Integrations · Notion
A Guild agent can read, write, and query your Notion workspace on your team’s behalf. Guild stores the OAuth credential server-side and injects it into every request, so agent code never handles a token. Credential policies let you restrict exactly which operations each agent may perform, and every call appears in the audit record.
Book a demo
See how teams govern agents that use Notion.
Start free
Connect Notion and scope your first agent.
What the Notion integration exposes
The integration provides tools that cover pages, blocks, databases, data sources, comments, users, and file uploads. Agents can search by title, render pages as Markdown, query and update database rows, create and move pages, manage blocks, and upload files. Search matches titles only, not page body content. Thenotion_oauth_retrieve_page_markdown tool may truncate long pages; check its truncated field.
How it works
1
Connect your Notion account
In Guild, go to Access & setup > Credentials, click Connect, and select notion-oauth. See Credentials for workspace, member, and agent-scoped options.
2
Choose which pages to share
Sign in to Notion, pick the workspace, and select the pages Guild can access. The agent can reach only those pages and anything under them.
3
Import tools into your agent
Import
NotionOauthTools from the guildai~notion-oauth package and spread it into your agent’s tools object. Use pick() from the Agent SDK to include only the tools your agent needs.Why Notion access needs governing
Guild’s credential proxy enforces credential policies before any request leaves the platform. You can write ALLOW and DENY rules scoped to specific operations, agents, or workspaces, so a read-only wiki agent cannot edit or delete pages even if the underlying credential permits it. Credentials are stored and injected server-side, so agent code, prompts, and containers never see the OAuth token. You can scope a credential to a single agent, a single workspace, or a single member using the options on the Credentials page. A team that shares one Notion connection can still give each agent a separate policy.About the Notion integration
The Notion integration connects agents to a Notion workspace with OAuth. Agents can search, read pages as Markdown, query and update databases, create and edit pages and blocks, comment, and upload files. The integration isguildai~notion-oauth.
The older
guildai~notion package is retired, and agents that import notionTools from it get errors. Use guildai~notion-oauth instead.Authentication
- Type: OAuth 2.0
Setup
1
Connect Notion
In Guild, go to Access & setup > Credentials, click Connect, and select notion-oauth.
2
Choose pages
Sign in to Notion, pick the workspace, and select the pages Guild can access.
Usage
Selecting specific tools
Tools are named with thenotion_oauth_ prefix. Use pick() to include only what your agent needs.
notion_oauth_search matches page and data source titles only, not page content. Search results include data source IDs you can pass to notion_oauth_query_data_source. If you have a database ID instead, get its data sources with notion_oauth_retrieve_database first.
Tools
Tools in the latest published version ofguildai~notion-oauth:
All 33 tools
All 33 tools
Limitations
notion_oauth_retrieve_page_markdowncuts off long pages. Check itstruncatedfield.
Frequently asked questions
Can an agent reach pages I did not select during setup?
Can an agent reach pages I did not select during setup?
No. When you connect, Notion limits the agent to the pages you chose and the pages under them. To grant access to more pages, share additional pages with the connection in Notion.
Can the agent search inside the body of a page?
Can the agent search inside the body of a page?
Not yet. The
notion_oauth_search tool matches against titles only, not page body content.How do I stop one agent from editing pages while another can?
How do I stop one agent from editing pages while another can?
Write a credential policy that denies mutating operations for the read-only agent. DENY rules are enforced by Guild’s credential proxy before the request reaches Notion, and a DENY always wins over an ALLOW.
Does the integration support webhook events from Notion?
Does the integration support webhook events from Notion?
No. The catalog entry for
guildai~notion-oauth lists no webhook events, so agents cannot trigger on Notion activity through this integration.Put a governed agent on Notion this week
Book a demo
See how teams govern agents that use Notion.
Start free
Connect Notion and scope your first agent.