Documents
- Documents
- Category
- OAuth
- Connection
- Pages and databases
- Lands in memory
What agents do
The work that stays in Notion.
Read the page that decided it
Specs, decisions, and owners are pulled from the page instead of asking the thread again.
Query the database
A roadmap or a tracker becomes a list the morning report can cite, filtered to the project.
Draft a new page
Launch notes, meeting write-ups, and briefs are proposed as pages. They are created only after you approve.
Update properties
Status, owner, and date are drafted from the ticket or the call. The write waits.
Append what changed
A block or a comment is proposed on the page that already holds the decision — not a new doc nobody will find.
Search what you connected
When someone asks where pricing landed, the agent looks across the pages in scope.
How you connect
Connect once. The brain starts from there.
- 01
Connect the account
One click into Notion, where the tool allows it. Morrow inherits that person's access — nothing wider.
- 02
Work writes itself in
The Notion records you scope to the project land in the company brain.
- 03
Agents act after you approve
Mor drafts the Notion update. Nothing is written back until you confirm.
In practice
What teams ask for
Friday's call becomes a spec update
The product agent proposes an edit on the existing page, with the open questions called out.
Morning brief cites the page
The CEO note points at the Notion decision instead of paraphrasing Slack.
Runbook grows after the incident
Support drafts the resolution onto the page the team already uses. It lands after approval.
Before you connect
Questions about this connection
Does Mor read the whole Notion workspace?
Only the pages and databases you connect to the project.
Can it create pages by itself?
It drafts them. Creation waits for approval.
What if we disconnect Notion?
New reads stop. Memory already captured stays until you delete it.
Often used with
