| name | notion-workspace |
| description | Search pages and databases, update content, and manage Notion workspace data from chat. Use this skill when users want to read, create, or modify Notion pages, query databases, manage sections, or automate Notion workflows via the Notion API. |
Notion Assistant
Access Notion via the Notion API with OAuth authentication. Search pages and databases, read and update content, manage sections, and coordinate workspace workflows.
This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure Notion API access yourself.
Setup in 3 Steps
| Step 1: Install | Step 2: Pair Account | Step 3: Connect Notion |
|---|
 |  | App-specific connection GIF coming soon |
| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Notion |
How It Works
┌─────────────────┐ ┌──────────────┐ ┌──────────────────┐
│ OpenClaw │────▶│ ClawLink │────▶│ Notion API │
│ (User Chat) │ │ (OAuth) │ │ │
└─────────────────┘ └──────────────┘ └──────────────────┘
│ │ │
│ 1. Install Plugin │ │
│ 2. Pair Device │ │
│ 3. Connect Notion │ │
│ │ 4. Secure Token │
│ │ 5. Proxy Requests │
│ │ │
▼ ▼ ▼
┌──────────┐ ┌──────────┐ ┌──────────┐
│ SKILL │ │ Dashboard│ │ Notion │
│ File │ │ Auth │ │ Workspace│
└──────────┘ └──────────┘ └──────────┘
Install
Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.
openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart
Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for Notion again."
Quick Start
clawlink_call_tool --tool "notion_list_databases" --params '{}'
clawlink_call_tool --tool "notion_search" --params '{"query": "project notes"}'
clawlink_call_tool --tool "notion_get_page" --params '{"page_id": "PAGE_ID"}'
Authentication
All Notion tool calls are authenticated automatically by ClawLink using the user's connected Notion account.
No API key is required in chat. ClawLink stores the OAuth token securely and injects it into every Notion API request on the user's behalf.
Getting Connected
- Install the ClawLink plugin (see Install above).
- Pair the plugin with
clawlink_begin_pairing if it is not configured yet.
- Open https://claw-link.dev/dashboard?add=notion and connect Notion.
- Call
clawlink_list_integrations to verify the connection is active.
Connection Management
List Connections
clawlink_list_integrations
Response: Returns all connected integrations. Look for notion in the list.
Verify Connection
clawlink_list_tools --integration notion
Response: Returns the live tool catalog for Notion.
Reconnect
If Notion tools are missing or the connection shows an error:
- Direct the user to https://claw-link.dev/dashboard?add=notion
- After they confirm, call
clawlink_list_integrations to verify
- Then call
clawlink_list_tools --integration notion
Security& Permissions
- Access is scoped to pages, databases, and content within the connected Notion workspace.
- All write operations require explicit user confirmation. Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.
- Destructive actions (delete page, remove database entry) must be confirmed.
Discovery Workflow
- Call
clawlink_list_integrations to confirm Notion is connected.
- Call
clawlink_list_tools --integration notion to see the live catalog.
- Treat the returned list as the source of truth. Do not guess or assume what tools exist.
- If the user describes a capability but the exact tool is unclear, call
clawlink_search_tools with a short query and integration notion.
- If no Notion tools appear, direct the user to https://claw-link.dev/dashboard?add=notion.
Execution Workflow
┌─────────────────────────────────────────────────────────────┐
│ READ OPERATIONS (Safe) │
│ list → get → search → describe → call │
│ │
│ Example: Search pages → Read content → Show results │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ WRITE OPERATIONS (Require Confirmation) │
│ list → get → describe → preview → confirm → call │
│ │
│ Example: Describe tool → Preview changes → User approves │
│ → Execute update │
└─────────────────────────────────────────────────────────────┘
- For unfamiliar tools, ambiguous requests, or any write action, call
clawlink_describe_tool first.
- Use the returned guidance, schema,
whenToUse, askBefore, safeDefaults, examples, and followups to shape the call.
- Prefer read, list, search, and get operations before writes when that reduces ambiguity.
- For writes or anything marked as requiring confirmation, call
clawlink_preview_tool first.
- Execute with
clawlink_call_tool. Pass confirmation only after the preview matches the user's intent.
- If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.
Code Examples
Search pages
clawlink_call_tool --tool "notion_search" \
--params '{
"query": "meeting notes",
"filter": {
"property": "object",
"value": "page"
}
}'
Query a database
clawlink_call_tool --tool "notion_query_database" \
--params '{
"database_id": "DATABASE_ID",
"filter": {
"property": "Status",
"select": {
"equals": "In Progress"
}
},
"sorts": [
{
"property": "Last edited time",
"direction": "descending"
}
]
}'
Create a page
clawlink_call_tool --tool "notion_create_page" \
--params '{
"parent": {
"database_id": "DATABASE_ID"
},
"properties": {
"Name": {
"title": [
{
"text": {
"content": "New Project Page"
}
}
]
}
},
"children": [
{
"object": "block",
"type": "heading_2",
"heading_2": {
"rich_text": [
{
"text": {
"content": "Overview"
}
}
]
}
}
]
}'
Notes
- Notion API has rate limits. Use exponential backoff when encountering 429 errors.
- Page and database IDs are UUIDs (e.g.,
abc123-def456-...). Use the full ID, not the human-readable page URL slug.
- Block content updates require the full block structure in the request body.
- Archived pages can be retrieved but may require specific filter conditions.
Error Handling
| Status / Error | Meaning |
|---|
| Tool not found | The tool name does not exist in the current catalog. Verify with clawlink_list_tools --integration notion. |
| Missing connection | Notion is not connected. Direct the user to https://claw-link.dev/dashboard?add=notion. |
object_not_found | Page or database does not exist. Check the ID or search for the resource first. |
validation_error | Invalid parameter or missing required field. Review the tool schema with clawlink_describe_tool. |
conflict_error | Resource was modified concurrently. Retry or re-fetch the latest state. |
| Write rejected | User did not confirm a write action. Always confirm before executing writes. |
Troubleshooting: Tools Not Visible
- Check that the ClawLink plugin is installed:
openclaw plugins list
- If the plugin is installed but tools are missing, tell the user to send
/new as a standalone message to reload the catalog.
- If a fresh chat does not help, run:
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart
- After restart, tell the user to send
/new again and retry.
Troubleshooting: Invalid Tool Call
- Ensure the integration slug is exactly
notion.
- Use
clawlink_describe_tool to verify parameter names and types before calling.
- For write operations, always call
clawlink_preview_tool first.
Resources
Related Skills
- Google Docs — For Google Workspace document operations
- Notion — For this skill's native documentation
Powered by ClawLink — an integration hub for OpenClaw
