1 min lukuaika
Google Drive (folder structure)
Reads an existing folder tree and reorganises it — but only after a person approves each change.
Reorganising a Drive that grew by accident. The assistant reads the whole tree, proposes a structure, and then moves nothing until a person says yes.
What it is
Section titled “What it is”A connection to Google Drive focused on structure rather than content: it reads the folder tree, and can create folders and move items into them.
It is the one integration in this catalogue whose write tools stop and ask. Creating a folder and moving an item are both gated on explicit human approval — the assistant cannot perform either silently, by design.
Use it for
Section titled “Use it for”- “Read this folder tree and propose a better structure.”
- “Create the folders we agreed and move the files into them.”
- “Where does this file sit in the hierarchy?”
- “Which folders are near-duplicates of each other?”
| Function | Answers |
|---|---|
| Usage guide | How to propose before acting — the assistant reads this first |
| List folder tree | The existing structure, read in full |
| Create folder | Makes a new folder — requires approval |
| Move item | Moves a file or folder — requires approval |
Data and permissions
Section titled “Data and permissions”- Two of the four tools require explicit consent. Each write pauses for a person to approve it. This is enforced in the connection, not requested in a prompt.
- Structure, not content. The integration reads how the Drive is organised. It is not a document-search connection.
- Scoped to what the authorised account can see.
Getting started
Section titled “Getting started”Authorise the integration against the Google account whose Drive is to be reorganised. Start with a subtree rather than an entire Drive.
Limitations
Section titled “Limitations”- Moving is not copying, and it is not free. A move changes where a file is for everyone who has it, and shared links or references that assumed the old location may break. Approval is asked per action precisely because this is hard to reverse at scale.
- Nothing is deleted. There is no delete tool, and an unwanted move has to be moved back.
- It does not read documents. For searching inside files, this is the wrong connection.
- Large trees take time, and a very large Drive may be better handled a subtree at a time.