Put an AI agent to work inside Google Drive
Connect Google Drive in one click and delegate the busywork: an autonomous agent that files incoming attachments, summarizes new documents, keeps a tracker current, and reviews who can see what. You set the autonomy, it does the work.
4-day trial · Cancel anytime
Fleece AI connects to Google Drive through managed OAuth and lets autonomous agents create, move, rename, and search files, read Docs, Sheets, and Slides, and review sharing permissions in real time. Agents combine Drive with 3,000+ other apps — Gmail, Google Sheets, Notion, Slack — so a new file can become a summary, a tracker entry, a notification, or a filed attachment, under the approval rules you set.
At a glance
| Category | Storage |
|---|---|
| Availability | Starter plan and up — included in the 4-day trial |
| Connects to | 3,000+ apps via managed OAuth |
| Setup | Connect your tools — no code required |
| Autonomy | Suggest-only to fully autonomous, with approval gates |
| Pricing | 4-day trial (card required, no charge today), then paid plans |
By Loïc Jané · Updated June 22, 2026
What a Fleece agent does with Google Drive
Google Drive is where your documents actually accumulate — files land from email, exports, and uploads; folders and shared drives sprawl; Docs, Sheets, and Slides pick up comments; and finding the right version means remembering who named it what. A Fleece agent works inside that library. It watches the folders and shared drives you point it at, reads and searches file contents, understands where things belong, and acts: it files, renames, summarizes, shares, or flags, according to the instructions you give it in plain language.
Under the hood the connection runs through managed OAuth — you authorize Google Drive once, and Fleece stores, scopes, and refreshes tokens securely. The agent can create files and folders, move and rename them, search across My Drive and shared drives, read the contents of Docs, Sheets, and Slides, add comments, and review sharing permissions. Real-time event triggers let it react the moment a file is added to a watched folder or a document is shared — no polling, no delay.
What separates this from Drive's own rules or an Apps Script is judgment and reach. A script runs a fixed procedure inside Google's walls; an agent reads the actual document, decides where it belongs and what it means, writes a summary a human can act on, and coordinates other tools to finish the job. And because Fleece agents run as a hierarchy — a lead agent delegating to specialized child agents — one Drive-facing agent can hand analysis to a data agent or a notification to a messaging agent and report back.
What the agent can do in Google Drive
Attachment filing
Routes incoming files to the right folder or shared drive and renames them with a consistent convention, so nothing lands in the wrong place.
Document summaries
Reads new Docs, Sheets, and Slides and writes a plain-language summary you can act on, without opening every file.
Search and retrieval
Searches across My Drive and shared drives by content, not just filename, and surfaces the right version when you ask.
Permission review
Audits sharing on sensitive folders, flags files shared too widely, and proposes changes that wait for your one-click approval.
Real-time triggers
Reacts the instant a file is added to a watched folder or a document is shared, through event-based triggers rather than polling.
Intake pipelines
Turns each new file into a chain of actions — summarize, notify, log — across your other connected tools.
Automations teams run on Google Drive
These are concrete setups you can describe to a Fleece agent in plain language. Each one combines Google Drive with other connected apps.
Ops: attachments that file themselves
When an email with an attachment arrives, the agent reads it, decides which Google Drive folder or shared drive it belongs in, and files it with a consistent name — client, document type, date. Invoices go to finance, signed contracts to legal, design exports to the project folder. It leaves a note in Slack when something is ambiguous, so a human only steps in on the edge cases, not the routine.
Teams: a new-document pipeline
The moment a file lands in a watched folder, the agent reads it, writes a short summary, posts it to the relevant Slack channel, and adds a row to a Notion or Google Sheets tracker with the file link, owner, and status. The team learns a document exists and what it says without opening Drive, and the tracker stays current on its own.
Security: a standing check on who can see what
Every week the agent reviews sharing permissions across your sensitive folders and shared drives, flags anything shared with the whole domain or an external address that shouldn't be, and compiles a report to Slack. For each risky file it proposes a fix — restrict, remove a viewer, move to a locked folder — that waits for your one-click approval before it touches anything, and it logs every change it makes.
Meetings: the right docs, pulled and packaged
Before a recurring meeting, the agent searches Drive for the relevant Docs and Sheets, checks they are shared with the attendees, and assembles a short brief — links, a one-paragraph summary of each, and open comments that still need answers. It posts the pack to Slack and files the brief in Notion, so people walk in prepared instead of scrambling for the latest version.
How to connect Google Drive to Fleece AI
Create your Fleece account
Sign up and start the 4-day trial. Your Google Drive agent, its flows, and every other integration live together in one workspace.
Connect Google Drive via managed OAuth
Pick Google Drive from the integrations catalog and authorize it in one click. Fleece manages tokens and scopes for you; you can revoke access at any time from Google or from Fleece.
Describe the job in plain language
Create an agent and tell it what to watch and what to do — "watch the Incoming folder, summarize each new file to our #docs channel, and log it in our tracker". No flowchart building required.
Set autonomy and approval gates
Choose what the agent may do on its own and what waits for your sign-off. Sensitive actions — sharing changes, moves, deletions — pause for one-click approval.
Run it on triggers or a schedule
Let the agent react to Drive events in real time, or schedule recurring flows — a weekly permission review, a nightly filing pass — that run without you.
Google Drive works better with the rest of your stack
Drive automations get powerful when they cross app boundaries. Pair Google Drive with Gmail to file attachments the moment they arrive, with Google Sheets or Notion to keep a live document tracker, with Slack to tell the team when something lands, or with any of 3,000+ other apps to turn a file into a downstream action — all through the same agent, all under the same approval rules. The stack you already store work in is almost certainly covered.
Frequently asked questions
Only if you allow it. You set approval gates per agent: routine actions like filing an attachment or writing a summary can run on their own, while sensitive ones — changing sharing permissions, moving, or deleting files — pause for your one-click sign-off. You choose the autonomy level, from suggest-only to fully autonomous, and can tighten it whenever you want.
The connection uses managed OAuth: you authorize Google Drive once through Google's official consent screen, and tokens are stored and refreshed securely — you never paste API keys. Access is scoped to the permissions you grant, you can revoke it from either side at any time, and security-relevant actions like sharing changes are recorded in an audit log.
Yes. Event triggers fire the moment a file is added to a watched folder or a document is shared, so filing, summaries, and notifications happen in seconds. You can combine real-time triggers with scheduled flows — for example instant intake of new documents plus a weekly permission-review report posted to Slack.
Drive's rules and Apps Script run fixed procedures inside Google's walls. A Fleece agent reads the actual contents of a file, exercises judgment about where it belongs and what it means, writes summaries a human can act on, and acts across 3,000+ other apps — posting to Slack, updating Notion, replying in Gmail — from a single conversation. Scripts automate procedures; agents handle the judgment around them.
Google Drive is part of the Starter tier, so it is available on every plan — including during the 4-day trial. Higher plans widen the catalog around it: about 20 essential apps on Starter, 1,000+ on Pro, and the full 3,000+ catalog on Business. The Drive capabilities themselves are the same across every plan.
Yes — that's the core design. One agent can watch a Drive folder, summarize each new file, post it to Slack, and log it in Google Sheets or Notion in a single run. For bigger jobs, a lead agent can delegate to specialized child agents — a data agent, an email agent, a messaging agent — and report the outcome back.
Runs are recorded step by step, so you can see exactly what the agent did and why. Failed flows retry sensibly and pause themselves after repeated failures instead of looping, and you are notified so nothing fails silently. If Drive rate-limits a burst of file operations, the agent backs off and resumes rather than dropping the work.
Yes. Within the permissions you grant, the agent can open and read Docs, Sheets, and Slides to summarize them, search across My Drive and shared drives by content rather than filename, and read comments. It only sees files the connected account can access, and for tools without an API Fleece can also drive the browser directly when needed.
Go deeper on the blog
Put Google Drive on autopilot
Connect Google Drive in one click, describe the job in plain language, and let an autonomous agent keep your files organized. 4-day trial, cancel anytime.
Powered by Fleece AI · autonomous agents for 3,000+ apps