Notion
Search a workspace and its connected sources, read pages and databases, and create, update, move and comment.
A Notion connection gives a playbook's functions Notion's MCP server. You sign in to Notion, choose a workspace and allow access, and the connection acts as you in that workspace, with the pages and databases you can see.
Available on Auto Cloud and on self-hosted runtimes.
What a playbook can do with Notion
- Search the workspace, and the sources connected to it through Notion.
- Read pages and databases, and a database's rows.
- Create pages and database rows, update them, move them, and comment on them.
What you cannot see in Notion, the playbook cannot see either; a workspace admin's pages stay the admin's.
Notion's MCP server lists its own tools when a function runs, and once you connect, your agent lists them with list_connection_tools.
An example workflow
Meeting notes that become decisions. A schedule trigger runs the workflow every evening. A lookup function reads today's pages in the "Meeting notes" database. A reasoning function reads each page with the team's conventions in its prompt and pulls out the decisions taken and the actions agreed, with their owners, in the shape the "Decisions" database takes. An interaction function creates a row in "Decisions" for each decision through the server's tools, with a link back to the notes, and comments on the notes page with what it recorded, so the people in the meeting see it. Where a decision names no owner, the workflow asks the meeting's organizer through a Slack connection and waits for the name before it writes the row. The run's history in Studio keeps every page read and every row written.
How to connect Notion
- Sign in to Notion, choose a workspace and allow access. The consent screen shows the permissions listed below.
Then:
- Ask your agent to connect Notion to Auto, or open Settings, Agents, Connections in Auto Studio and choose Notion.
- On the Studio page, check the service and its access, choose which playbooks may use the connection, and approve it.
- Have your agent check one small read through the connection before a function depends on it.
What it needs
- A Notion account in the workspace; the connection has your access there.
- Your agent connected to Auto and signed in as you, with permission to change your organization, if your agent adds the connection.
- On a self-hosted runtime, nothing to register: Notion's server takes a client Auto names by its metadata document or registers itself, or one you registered.
Permissions Auto asks for
- Search, read, create and change the pages and databases of the Notion workspace chosen.
Good to know
A tool that creates, updates or moves a page is marked as one that acts, so a lookup function cannot call it, and a reasoning function calls it only where its definition names the tool. What a function reads, a page's content for example, is kept in the run's history, where people with access to the playbook can read it.