Guide
OpenClaw + Notion: Read and Write Your Workspace from Chat
Notion isn't a chat channel — it's an action target. You connect it as a tool, and then your OpenClaw agent can create pages, update databases, and search docs on command. There are two solid ways to wire it up: the Notion MCP server, or Composio.
First, Understand the Model
Unlike Telegram or Slack, Notion doesn't send the agent messages. Instead, you give the agent tools that call the Notion API. When you ask “add a row to my CRM database” in your normal chat channel, the agent reaches into Notion and does it. So the integration is about granting tool access, not adding a channel.
Path 1: Notion MCP Server (most control)
OpenClaw supports the Model Context Protocol natively. Notion publishes an official MCP server that exposes its API as agent tools — search, page create/update, database query, block append, and more.
- Create a Notion integration at notion.so/my-integrations and copy the internal integration token.
- In Notion, open the pages or databases you want the agent to touch and share them with your integration (the integration only sees what you explicitly share).
- Add the Notion MCP server to your OpenClaw config, passing the token:
{
"mcpServers": {
"notion": {
"command": "npx",
"args": ["-y", "@notionhq/notion-mcp-server"],
"env": { "NOTION_TOKEN": "secret_..." }
}
}
}Restart the gateway and the agent now has Notion tools. This path keeps everything on your own infrastructure — no third-party broker holds your token.
Path 2: Composio (fastest, OAuth)
If you'd rather not manage a Notion token, connect Notion through Composio. It handles OAuth and exposes Notion as a searchable toolkit your agent can call.
- Go to openclawlaunch.com/integrations and connect Notion with one click.
- Authorize the Notion workspace you want the agent to use.
- From chat, the agent can now
search notionfor the right tool and call it — create pages, update databases, fetch content — with no per-instance token setup.
What You Can Ask the Agent to Do
- “Create a meeting-notes page under my Projects database.”
- “Add this lead to the CRM table with status = new.”
- “Search my wiki for the deployment runbook and summarize it.”
- “Turn this Telegram thread into a Notion doc.”
Because Notion is a tool, you can combine it with any channel — ask in Telegram, the result lands in Notion.
Which Path Should You Pick?
| Notion MCP Server | Composio | |
|---|---|---|
| Setup | Token + config edit | One-click OAuth |
| Token custody | Stays on your host | Held by Composio |
| Other apps | Notion only | Many apps, one connection |
| Best for | Self-hosters, privacy-first | Fastest path, multi-app |
Security Notes
With the MCP path, the Notion integration only accesses pages and databases you explicitly share with it — nothing else in your workspace is visible. With Composio, you authorize a specific workspace and can revoke access from the integrations page at any time.
What's Next?
- OpenClaw Architecture — how MCP and tools fit in
- OpenClaw Tools & Integrations — browse the catalog
- Integrations — connect Notion via Composio
- OpenClaw + Slack — pair a channel with Notion actions