Files
- Files
- Category
- OAuth
- Connection
- Folders you connect
- Lands in memory
What agents do
The work that stays in Google Drive.
Read the doc that holds the decision
The spec, the deck, or the sheet is pulled into the project instead of passed as a link.
Draft a doc from the meeting
Notes become a proposed document in the folder you chose. It is created after approval.
Find the file the thread mentioned
When Slack or Teams names a doc, the agent looks in the folders in scope.
Cite the sheet
Finance and ops agents read the rows you connected, so the number in the brief matches the file.
Keep the deck with the launch
The file stays attached to the project, so the next agent does not ask for the link again.
Scope stays on the folder
Other Drive files are not read. Only what you connect joins the brain.
How you connect
Connect once. The brain starts from there.
- 01
Connect the account
One click into Google Drive, where the tool allows it. Morrow inherits that person's access — nothing wider.
- 02
Work writes itself in
The Google Drive records you scope to the project land in the company brain.
- 03
Agents act after you approve
Mor drafts the Google Drive update. Nothing is written back until you confirm.
In practice
What teams ask for
Spec the team can ask
A product question is answered from the doc in the connected folder, with the page cited.
Meeting notes filed where they belong
The agent drafts the write-up into the project folder. You approve before it is created.
The number from the sheet
Finance cites the connected sheet in the morning brief instead of a retyped total.
Before you connect
Questions about this connection
Does Morrow index all of Drive?
No. Only the folders and files you connect to the project.
Can it create documents?
It drafts them. Creation waits for approval.
What about Docs and Sheets?
Files in a connected folder are readable, including Docs and Sheets. Writes still wait for approval.
Often used with
