Drive is the team filesystem; connected, missions use it like one - deliverables filed into the right folders, existing files read as context, nothing orphaned in chat.
Work products need a home, and chat is not one. Connected to Drive, every mission artifact - sheets, docs, decks, exports - files into the folder structure your team already navigates, named like a person named it. Six months later, when someone asks for that competitor analysis, it is where analyses live rather than in a thread nobody can find.
The read side turns Drive into mission memory: existing files become context on request - last quarter’s plan, the brand deck, the export from the old tool - so agents work from what the team already knows.
Deliverables land in designated folders with sensible names - the archive builds itself.
Existing documents and exports read into missions when the objective points at them.
Multiple sources in a folder read together into one brief - the synthesis nobody had time to write.
Team-drive conventions respected: missions write where you scope them, and only there.
Real missions from the playbook library - run them as-is from the console, or read the full article behind each.
Build me a list of C-level contacts at US software companies between 50 and 500 employees showing active buying intent on marketing automation, format it as a LinkedIn Ad…
Build a matched audience of companies showing buying intent on my category plus their marketing leaders, format it exactly for LinkedIn Ads company and contact targeting,…
Segment my HubSpot contacts by lifecycle stage, build platform-ready retargeting CSVs for Meta and Google formats, and save them to Drive with a one-page targeting note.
Build a matched audience of companies showing intent on my category, format the LinkedIn Ads CSVs into Drive, then generate three landscape creatives aimed at that exact …
Connections are scoped to one workspace, every card has a disconnect button, and outbound actions honor your approval policy.
What the connected account can reach, used only as objectives direct - and you can keep a dedicated folder as the working scope. Every read and write is logged in the audit trail.
Yes - PDFs, docs and sheets pointed at by the objective become context. The deliverable cites which files informed it, the same evidence discipline as web research.
Those create and edit their document types; Drive is the filesystem around them - organization, retrieval and cross-file reading. Together they behave like a colleague with proper file manners.
One connection, eight specialist agents, one budget ledger - and your approval policy on everything outbound.