How to Connect Notion to OpenClaw

Go to notion.so/my-integrations and click '+ New integration'. Give it a name (e.g., 'OpenClaw Integration') and select the workspace it should have access to. Under capabilities, select: - Read content - Update content - Insert content Click 'Submit'. Notion creates the integration and shows your Internal Integration Token — this is your NOTION_API_KEY. It looks like `secret_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx`. Copy it immediately. The token is the only credential you need for API access. Unlike OAuth integrations, Internal Integration Tokens do not expire and do not require periodic re-authorization. They are scoped to the workspace you selected and can only access pages and databases that you explicitly share with the integration. Do not confuse this with a Notion OAuth integration (used for third-party apps that need to access multiple users' workspaces). For OpenClaw connecting to your own workspace, the Internal Integration Token is the correct approach — simpler, no OAuth flow required.

1# Your Notion API key format:
2# NOTION_API_KEY=secret_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
3
4# Verify API key works:
5curl -H "Authorization: Bearer YOUR_NOTION_API_KEY" \
6     -H "Notion-Version: 2022-06-28" \
7     https://api.notion.com/v1/users/me
8
9# Expected response:
10# {"object": "user", "id": "...", "type": "bot", "bot": {"owner": {"type": "workspace"}}}

This is the most frequently missed step for Notion API beginners. Creating the integration and getting an API key is not enough — Notion requires you to explicitly grant the integration access to each database or page you want it to reach. For each database or page you want OpenClaw to access: 1. Open the database or page in Notion 2. Click the three-dot menu (⋯) in the top-right corner 3. Click 'Connect to' 4. Search for your integration name (e.g., 'OpenClaw Integration') 5. Click 'Confirm' You only need to share the top-level database or page — child pages inherit access automatically. If you have a workspace organized with a top-level 'Home' or 'Dashboard' page that contains all databases, sharing that one page with the integration gives access to everything under it. To find a database's ID (needed for API calls): open the database in Notion and look at the URL. The 32-character string after the last `/` (before `?v=`) is the database ID. Format: `xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx` or `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx` with hyphens.

1# Notion database URL format:
2# https://www.notion.so/workspace/DATABASE_ID?v=VIEW_ID
3# Example:
4# https://www.notion.so/myteam/a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6?v=...
5# Database ID: a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6
6
7# Verify access to a database after sharing:
8curl -H "Authorization: Bearer YOUR_NOTION_API_KEY" \
9     -H "Notion-Version: 2022-06-28" \
10     https://api.notion.com/v1/databases/YOUR_DATABASE_ID
11
12# If access is not granted, you get:
13# {"object": "error", "status": 404, "code": "object_not_found"}

Open `~/.openclaw/config.yaml` and add the Notion integration block under `integrations`. The configuration requires your API key and optionally a default database ID for quick reference in workflows. The `version` field should always be set to `2022-06-28` — this is Notion's stable API version and must be included as a header on every API request. If omitted, requests may fail or return unexpected response formats. The optional `databases` section lets you give friendly names to specific database IDs, so you can reference them by name (e.g., `notion:task_log`) in OpenClaw workflows rather than using the raw 32-character ID. This makes workflows more readable and easier to maintain when database IDs need to change. After saving, run `clawhub reload`. OpenClaw will verify the API key and optionally pre-fetch the schema for each configured database to validate access.

1# ~/.openclaw/config.yaml
2integrations:
3  notion:
4    api_key: "secret_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
5    version: "2022-06-28"          # Always use this Notion API version
6    databases:
7      task_log: "a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6"      # Activity log DB
8      crm: "b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7"           # CRM contacts DB
9      knowledge_base: "c3d4e5f6g7h8i9j0k1l2m3n4o5p6r8s9"  # Docs database
10    default_database: task_log     # Used when no database is specified in workflow
11    search_enabled: true           # Enable full workspace search
12    page_size: 100                 # Results per API call (max 100)

With credentials configured, test querying an existing database and creating a new entry. Notion's API represents database entries as Pages — even rows in a database are internally Notion pages with properties. To query a database, POST to `/v1/databases/{database_id}/query` with optional filter and sort parameters. Notion's filter syntax uses a property-based structure — you specify which property to filter on and the condition. This is equivalent to adding a filter in Notion's database view. To create a new database entry (row), POST to `/v1/pages` with the parent database ID and a properties object matching the database schema. Property values must match the property type exactly — a Title property expects `{"title": [{"text": {"content": "value"}}]}` format, while a Select property expects `{"select": {"name": "option_name"}}`. Mismatched property types are the most common cause of failed page creation.

1# Query database entries (get last 5 tasks):
2curl -X POST "https://api.notion.com/v1/databases/YOUR_DATABASE_ID/query" \
3  -H "Authorization: Bearer YOUR_NOTION_API_KEY" \
4  -H "Notion-Version: 2022-06-28" \
5  -H "Content-Type: application/json" \
6  -d '{
7    "sorts": [{"property": "Created", "direction": "descending"}],
8    "page_size": 5
9  }'
10
11# Create a new database entry:
12curl -X POST "https://api.notion.com/v1/pages" \
13  -H "Authorization: Bearer YOUR_NOTION_API_KEY" \
14  -H "Notion-Version: 2022-06-28" \
15  -H "Content-Type: application/json" \
16  -d '{
17    "parent": {"database_id": "YOUR_DATABASE_ID"},
18    "properties": {
19      "Name": {
20        "title": [{"text": {"content": "OpenClaw workflow completed"}}]
21      },
22      "Status": {
23        "select": {"name": "Success"}
24      },
25      "Date": {
26        "date": {"start": "2026-03-30"}
27      },
28      "Notes": {
29        "rich_text": [{"text": {"content": "Automated entry from OpenClaw"}}]
30      }
31    }
32  }'

With CRUD operations working, integrate Notion into OpenClaw workflows as a persistent data store. The most powerful pattern is using Notion as a structured log and knowledge base — OpenClaw writes records as it operates, and you can query and analyze them in Notion's familiar interface. Configure OpenClaw workflows with Notion as the output target for activity logging. Every workflow completion, error, or notable event writes a structured entry to a Notion database. This gives you a searchable history of everything OpenClaw has done, viewable in Notion with custom views, filters, and groupings. For read workflows, search your Notion workspace before generating responses — this grounds AI outputs in your actual documentation rather than general knowledge. The Notion search API covers all accessible pages and databases. RapidDev's team recommends structuring your Notion activity log database with a consistent schema from the start: Name (title), Status (select), Integration (select), Timestamp (date), Summary (text), Error (text) — this schema accommodates virtually all OpenClaw activity types and supports rich Notion views.

1# ~/.openclaw/config.yaml — Notion activity logging workflow
2workflows:
3  log-to-notion:
4    trigger:
5      type: workflow_complete     # Fires after any other workflow completes
6    actions:
7      - type: integration-call
8        integration: notion
9        endpoint: /pages
10        method: POST
11        body:
12          parent:
13            database_id: "{{config.integrations.notion.databases.task_log}}"
14          properties:
15            Name:
16              title:
17                - text:
18                    content: "{{trigger.workflow_name}} — {{trigger.status}}"
19            Status:
20              select:
21                name: "{{trigger.status}}"
22            Integration:
23              select:
24                name: "{{trigger.integration}}"
25            Timestamp:
26              date:
27                start: "{{trigger.completed_at}}"
28            Summary:
29              rich_text:
30                - text:
31                    content: "{{trigger.summary}}"
32
33# Search Notion workspace:
34curl -X POST "https://api.notion.com/v1/search" \
35  -H "Authorization: Bearer YOUR_NOTION_API_KEY" \
36  -H "Notion-Version: 2022-06-28" \
37  -H "Content-Type: application/json" \
38  -d '{"query": "deployment checklist", "filter": {"value": "page", "property": "object"}}'