There’s already a deep guide on building the OpenClaw-Notion integration from scratch — raw API calls, rich-text JSON quirks, database schema handling. This guide is different. It’s about installing and configuring the Notion skill from the OpenClaw marketplace and getting a working “meeting notes → searchable wiki” workflow running as quickly as possible.
If you want to understand the API internals, read the integration guide. If you want it working today, read this one.
Installing the Notion Skill
@openclaw install skill notion
Or search the marketplace:
@openclaw skills search notion
> Found: notion-core v1.8.2 — Pages, databases, wiki workflows
> Install? [y/n]
After installation:
@openclaw setup notion skill
This launches the credential setup flow.
Getting Your Internal Integration Token
The skill uses a Notion internal integration token — simpler and more appropriate for personal use than OAuth.
- Go to notion.so/my-integrations
- Click New integration
- Name: “OpenClaw”
- Associated workspace: select your workspace
- Capabilities:
- Read content ✓
- Update content ✓
- Insert content ✓
- Click Submit
- Copy the Internal Integration Secret
@openclaw configure notion skill
> Paste your integration token: [paste here]
> ✅ Token saved
Verify:
@openclaw check notion skill
> ✅ Connected to workspace: Your Workspace Name
> Pages accessible: 0 (share pages with integration to grant access)
That last line is important. Zero accessible pages is normal at this stage.
Sharing Pages with the Integration
Notion’s integration model requires you to explicitly share each page or database with your integration. The integration doesn’t get blanket workspace access — you choose what it can see.
Share a page:
- Open any Notion page
- Click
...(top-right) → Connections - Find “OpenClaw” → click Confirm
Share a database:
Same process. Open the database → ... → Connections → OpenClaw → Confirm.
Tip: Share a top-level page and all child pages inherit access automatically. Share your workspace root page (if you have one) and the integration can see everything beneath it. Share selectively if you want to limit what OpenClaw can access.
After sharing, verify:
@openclaw check notion skill
> ✅ Connected to workspace: Your Workspace Name
> Pages accessible: 47
> Databases accessible: 8
Understanding Page vs. Database Operations
The Notion skill handles two fundamentally different types of content. Understanding the difference prevents confusion.
Pages are documents — they have a title and a body of content blocks (paragraphs, headings, bullet lists, code blocks, etc.). Think of a page as a Google Doc living inside Notion.
Databases are collections of pages with a shared schema — each page in the database has properties (text fields, selects, dates, checkboxes, etc.). Think of a database as a spreadsheet where each row is also a full page.
Most real Notion workspaces use a mix: databases for structured tracking (tasks, projects, meeting notes) and standalone pages for documents and reference material.
Reading a page:
@openclaw read my "Product Strategy 2026" Notion page
Reading a database:
@openclaw show open tasks in my "Tasks" Notion database
Writing to a page:
@openclaw add a section to my "Team Handbook" page about our new meeting norms
Adding a row to a database:
@openclaw add a task to my Notion Tasks database: "Review Q3 metrics", due Friday, priority High
The skill detects which operation is needed based on context, but being explicit (“page” vs. “database”) removes ambiguity.
Skill Configuration
notion:
token: "${NOTION_TOKEN}"
# Default databases (set these to avoid specifying every time)
defaults:
tasks_database: "your-tasks-db-id"
notes_database: "your-notes-db-id"
wiki_database: "your-wiki-db-id"
# Folder structure for new pages
folders:
meeting_notes: "Meeting Notes" # Parent page name
daily_notes: "Daily Notes"
reference: "Reference Library"
# Property names in your databases (customize to match your schema)
property_names:
status: "Status"
priority: "Priority"
due_date: "Due Date"
tags: "Tags"
created_by: "Created"
Getting database IDs: Open the database in Notion → click ... → Copy link. The ID is the 32-character string in the URL before the ?.
The “Meeting Notes → Searchable Wiki” Recipe
This is the flagship workflow for the Notion skill. Raw meeting notes become structured, searchable wiki entries automatically.
The Problem It Solves
After a meeting, most people either:
- Don’t write notes at all (information lost)
- Write quick notes in a scratchpad that nobody including themselves will ever find again
- Spend 15 minutes reformatting notes into a proper document (tedious)
The skill collapses this to: dump your raw notes, OpenClaw structures them and files them correctly.
Step 1: Set Up Your Meeting Notes Database
Create a Notion database called “Meeting Notes” with these properties:
| Property | Type |
|---|---|
| Title | Title |
| Date | Date |
| Attendees | Multi-select |
| Project | Relation (links to Projects database, optional) |
| Action Items | Checkbox or Relation |
| Tags | Multi-select |
Share this database with your OpenClaw integration.
Tell the skill about it:
@openclaw my meeting notes database is called "Meeting Notes"
Step 2: Dump Raw Notes After a Meeting
@openclaw save meeting notes:
Spoke with Sarah and Marcus about Q3 roadmap
- Mobile redesign is being pushed, everyone agrees
- API performance work takes priority
- Marcus needs sign-off from legal before we start the data migration
- Sarah will have the revised timeline by end of week
- We agreed to weekly check-ins every Tuesday 3pm
- I need to send Marcus the performance benchmarks from last quarter
OpenClaw processes the raw notes and creates a structured entry:
Creates in “Meeting Notes” database:
Title: Q3 Roadmap Review
Date: May 19, 2026
Attendees: Sarah, Marcus, [You]
Tags: Roadmap, Q3, API
---
## Summary
Reviewed Q3 priorities. Agreed to deprioritize mobile redesign in favor of
API performance work. Legal sign-off required before data migration begins.
## Decisions
- Mobile redesign → Q4
- API performance → Q3 priority 1
- Weekly check-ins every Tuesday 3pm
## Action Items
- [ ] @Marcus: Get legal sign-off for data migration
- [ ] @Sarah: Send revised timeline by end of week
- [ ] @You: Send Marcus performance benchmarks from last quarter
## Notes
Marcus is blocked on legal. Sarah owns the timeline update.
Step 3: Action Items Sync
@openclaw extract action items from my meeting notes and add them to my Tasks database
OpenClaw reads the meeting notes just created, finds all action items assigned to you, and creates corresponding tasks in your Tasks database with a link back to the meeting notes page.
Step 4: Making Notes Searchable
@openclaw find meeting notes where we discussed the data migration
OpenClaw searches the Meeting Notes database across titles, tags, and body content to surface relevant pages. This works because meeting notes were filed consistently — title, date, tags, structured body — rather than as freeform text.
Found 3 meeting notes mentioning "data migration":
1. Q3 Roadmap Review — May 19, 2026
"Marcus needs sign-off from legal before we start the data migration"
2. Infrastructure Planning — May 5, 2026
"Data migration estimated 3 weeks, requires staging environment setup"
3. Q2 Retrospective — April 30, 2026
"Delayed data migration to Q3 due to resource constraints"
Expanding to a Full Wiki
The same pattern works for any content you want to build into a searchable knowledge base:
# Research notes
@openclaw save research note: [paste article summary or notes]
# Decision logs
@openclaw log a decision: we chose PostgreSQL over MongoDB for the new service because [reasons]
# Reference material
@openclaw save to reference library: [technical documentation, how-tos, etc.]
Each gets filed in the appropriate database, tagged, and becomes searchable via OpenClaw.
Common Operations
# Reading
@openclaw find my notes about [topic]
@openclaw show my open tasks in Notion
@openclaw read the [page name] page
# Creating
@openclaw create a page in [parent page]: [title and content]
@openclaw add to my [database name]: [properties and content]
# Updating
@openclaw mark [task] as complete in my Tasks database
@openclaw update the status of [page] to [value]
@openclaw add a note to [page]: [content]
# Searching
@openclaw search Notion for [topic]
@openclaw find notes tagged [tag] from last month
Troubleshooting Setup Issues
“No pages found” after connecting: You need to share pages with the integration. See the “Sharing Pages” section above.
“Property not found” when creating database entries:
Your database’s property names might differ from the skill’s defaults. Check your database’s actual column names and update property_names in the skill config.
“Integration not found” when sharing a page: The integration must be created in the same Notion workspace where the page lives. If you have multiple workspaces, create separate integrations for each.
Rich text not formatting correctly: When reading content back from Notion, formatting (bold, italic, code) is rendered as markdown. When writing, plain text and basic markdown is supported. Complex nested formatting (colored text, columns) isn’t fully round-trippable via the API.
PaioClaw vs. Self-Hosted
The Notion skill works well self-hosted. PaioClaw’s additions:
Schema change detection: If you rename a Notion database property, the skill’s config breaks. PaioClaw detects schema changes at runtime and prompts you to update the mapping — self-hosted fails silently until you debug it.
Mobile capture: Quick capture from mobile (“remember this for later”) routes to Notion correctly via PaioClaw’s mobile interface. Self-hosted requires being at your computer.
Multi-workspace routing: If you have separate personal and work Notion workspaces, PaioClaw routes queries to the right one based on context. Self-hosted requires manually specifying the workspace for each command.
Plans start free, Smart at $15/mo, Genius at $25/mo.
Summary
Install the skill, create an internal integration token, share your key pages and databases with the integration, and configure the default database IDs. That’s the entire setup.
The meeting notes recipe is the fastest way to see the skill’s value: drop raw notes after any meeting and get a structured, tagged, linked wiki entry in return. Once that workflow is running reliably, expand to action item sync, decision logs, and reference material capture. The value compounds — the more you put in, the more useful the search becomes.