Overview
The Notion integration connects your Claws directly to your team’s Notion workspace through OAuth. Once authorized, a Claw can read existing pages and databases, create new content with full rich text formatting, and query structured data, all from within its isolated ClawCage container. Your Notion workspace becomes a living, AI-maintained knowledge base that stays current without manual effort.
ClawStaff handles the OAuth 2.0 handshake with Notion’s API. You authorize access at the workspace level, choosing exactly which pages and databases each Claw can see. Permissions are scoped per-connection, so different Claws can have different levels of access to your workspace.
What Your Claw Can Do
- Query databases. Filter, sort, and aggregate data across Notion databases. Claws can pull structured information like project trackers, content calendars, and CRM tables to answer questions or generate reports.
- Create pages with rich content. Generate full Notion pages with headings, bullet lists, code blocks, callouts, tables, and toggle blocks. Claws produce native Notion formatting, not plain text dumps.
- Update existing pages. Append content to pages, modify properties on database entries, and update status fields. Claws can keep documentation current as your project evolves.
- Search across the workspace. Full-text search through authorized pages and databases to find relevant information, surface forgotten docs, or cross-reference knowledge.
- Auto-generate documentation. Claws can produce meeting notes, technical documentation, onboarding guides, and project summaries and publish them directly to the right location in your workspace.
Who Can Reach Your Claw
Notion access is scoped through the OAuth authorization flow. You choose exactly which pages and databases to share:
- By workspace page. Only pages explicitly shared with the integration during OAuth are accessible. The Claw cannot browse or discover pages that were not shared.
- By database. Whitelist specific databases. The Claw can query and modify only those databases.
This works alongside three Claw scoping levels:
Private Claw. Only the creator interacts. The Claw manages your personal Notion pages: drafting docs, organizing notes, and searching your workspace. Example: a personal documentation assistant that maintains your personal wiki and generates meeting notes from Slack conversations.
Team Claw. Whitelisted team members share the Claw. It manages a team’s Notion workspace: maintaining the engineering wiki, updating project trackers, and generating reports. Only team members can query or trigger it.
Organization-wide Claw. Any org member can interact. The Claw serves as a company knowledge search tool, so anyone can ask it to find policies, procedures, or project documentation in the shared workspace.
How It Works
- Connect your workspace. From the ClawStaff dashboard, click “Add Integration” on the Notion card. You will be redirected to Notion’s OAuth consent screen where you select which pages and databases to share.
- Assign to a Claw. Once connected, assign the Notion connection to one or more Claws. Each Claw receives scoped credentials that only grant access to the pages you authorized.
- Claw reads and writes. At runtime, your Claw operates inside a ClawCage (an isolated Docker container). When it needs Notion data, it uses the stored OAuth token to call Notion’s API. All requests are made from within the container, and tokens never leave the ClawCage boundary.
- Token refresh is automatic. ClawStaff handles OAuth token refresh transparently. You connect once, and the integration stays active until you revoke it.
Security
- OAuth 2.0 scoped access. You choose exactly which pages and databases each Claw can access during the authorization flow. Claws never have blanket access to your entire workspace.
- Tokens encrypted at rest. OAuth tokens are stored using AES-256 encryption in ClawStaff’s database. They are decrypted only at runtime, inside the ClawCage.
- ClawCage isolation. Each Claw runs in its own Docker container with no shared filesystem or network access to other Claws. Notion API calls are made from within this isolated environment.
- Revocable at any time. Disconnect the integration from the ClawStaff dashboard or revoke access directly in Notion’s settings. Tokens are immediately invalidated.
- No data persistence. Claws process Notion data in-memory during task execution. Page content is not cached or stored outside the ClawCage after the task completes.
Cross-Integration Workflows
The Notion integration becomes significantly more powerful when combined with other connected tools:
- GitHub PR merged to Notion changelog updated. When a Claw detects a merged pull request via the GitHub integration, it can automatically create or append to a changelog page in Notion with the PR title, description, and linked issues.
- Slack discussion to Notion meeting notes. A Claw monitoring a Slack channel can summarize a conversation thread and publish structured meeting notes to a designated Notion page, complete with action items and decisions.
- Jira sprint completed to Notion retrospective template. When a sprint closes in Jira, a Claw can generate a pre-filled retrospective page in Notion with sprint velocity, completed tickets, and carry-over items pulled from Atlassian.
- Notion database to Slack digest. A Claw can query a Notion project tracker on a schedule and post a daily or weekly summary to a Slack channel, highlighting blockers, upcoming deadlines, and status changes.