
Team Drive
v0.1.0Your shared Drive folder, able to say what changed this week and where the current version is.
Team Drive
agents
Drive Librarian
.agents/drive-librarian/
Monthly Drive Map
0 6 1 * *
Week Watcher
.agents/week-watcher/
Monday Drive Brief
0 8 * * 1
2
Agents
2
Jobs
1
Depts
3
Pages
Keeps a map of the shared Drive folder so anyone can find the right file without opening ten of them.
Writes one short page every Monday saying what moved in the shared Drive folder last week.
Team Drive
Your shared Drive folder, able to say what changed this week and where the current version is.
What you get
Two pages and two people.
Where things are is a map of the folder. One line per folder saying what it holds, and for the things that come in versions, which file is the current one. It is the page you open when somebody asks "where do we keep the signed contracts".
This week is a short page written every Monday morning. What was added, what was changed, what was moved or renamed, and what that means. You read it in a minute and you know what your colleagues did without asking any of them.
Between the two, you can just ask. Type "where is the latest pricing deck" or "what changed in Finance last week" into the cabinet and the answer comes from the folder itself, not from a search box.
How to look at it
The Drive folder sits in the sidebar of this cabinet, exactly where you put it. Open it and you are looking at your real files, the same ones the Drive app keeps on this computer. Nothing is copied anywhere.
Where things are and This week are pages in this cabinet. They come pre-filled with a made-up example so you can see the shape straight away. Both say clearly that the files in them are invented. Your first real run replaces them.
Before it can read your real folder
Connect Google Drive when Cabinet asks, or later from Integrations, and pick the shared folder you want. You do it once. It uses the Google Drive app on this computer, so nothing new gets installed and nothing is uploaded anywhere.
Your team reads. It does not write to Drive, rename anything, or move a file. Until you connect a folder, both pages keep showing the example and the two routines wait.
If the pages still show the example
The routines only write when they can actually read a folder. If one has run and the example is still sitting there, no Drive folder is in this cabinet yet. Nothing was overwritten and nothing errored. Add the folder and run it again.
What is inside
- Drive Librarian and Week Watcher. One keeps the map, one writes Monday's page.
- Monthly Drive Map, on the first of the month. Monday Drive Brief, Mondays at 08:00.
- Where things are and This week, the two pages above.
$ git clone --filter=blob:none --sparse https://github.com/cabinetai/cabinets.git && cd cabinets && git sparse-checkout set google-drive-team-drive