← Back to Skills Marketplace
11838
Downloads
8
Stars
0
Active Installs
19
Versions
Install in OpenClaw
/install notion-api-skill
Description
Notion API integration with managed OAuth. Query databases, search pages, and read workspace content. Write operations require explicit user confirmation of the target resource and connection. Use this skill when users want to interact with Notion workspaces, databases, or pages. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Notion connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Notion action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Notion examples; they add no Notion capability - Notion is itself an event source, so its own events are in `references/notion/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Before installing, understand that this skill can read and modify Notion content through your connected account. Use the read/list workflow first, confirm exact page/database/block IDs before writes, avoid unscoped triggers, and do not create persistent destinations or hosted functions unless you explicitly want ongoing automation.
Capability Assessment
Credentials
Network access, a Maton account, OAuth login, and Notion connection access are proportionate for the integration, and the skill warns against exposing credentials or using raw API keys except where the CLI cannot be installed.
Install Mechanism
Installation uses pinned Maton CLI and SDK versions via npm, Homebrew, or package managers; no embedded executable package scripts were present in the skill artifacts inspected.
Instruction Scope
The skill documents high-impact features such as hosted functions, triggers, destinations, raw API calls, and local event watch execution, but repeatedly scopes them to user-requested tasks with explicit approval, least-privilege summaries, and narrow targets.
Persistence & Privilege
OAuth tokens, functions, triggers, destinations, and watch checkpoints can persist beyond one command, but those behaviors are disclosed and accompanied by confirmation, scoping, deletion, and credential-handling guidance.
Purpose & Capability
The stated purpose is Notion workspace access for search, reading, querying, and approved writes; the documented Notion API operations, OAuth connection flow, and Maton gateway usage match that purpose.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install notion-api-skill - After installation, invoke the skill by name or use
/notion-api-skill - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.5
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.4
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.3
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.2
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.1
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.11
- Removed the file `skill-card.md` from the repository.
- No changes made to code or functionality; documentation file only was deleted.
- The skill continues to provide Notion API integration with managed OAuth as before.
v1.0.10
- Clarified that all write operations (create, update, delete) require explicit user confirmation of the target resource and connection before execution.
- Updated the description and introductory text to emphasize stricter confirmation requirements for write actions.
- Adjusted documentation and usage notes to specify no writing is permitted without prior user approval.
- Reinforced security best practices and scope boundaries regarding resource operations and connection selection.
v1.0.9
Version 1.0.9
- Expanded Security & Permissions section with detailed user safety steps for write operations.
- Added requirements for confirming targets (IDs), verifying connections, and stating if an action is reversible or destructive before any write.
- Listed specific irreversible/high-risk operations that require extra caution.
- Clarified strict scope boundaries and the need for explicit user approval before bulk or batch changes.
- No changes to the skill's functionality or API surface.
v1.0.8
Version 1.0.8
- Added comprehensive CLI usage examples for interacting with Notion via the Maton CLI.
- Expanded installation and authentication instructions, including Homebrew and npm options.
- Provided side-by-side CLI and Python code samples for all major workflows (connections, search, data sources, pages).
- Clarified how to specify and manage multiple Notion connections in both CLI and API workflows.
- Improved documentation structure, making setup and usage clearer for both CLI and API users.
v1.0.7
- Changed all base URLs from gateway.maton.ai and ctrl.maton.ai to api.maton.ai.
- Updated sample code and instructions to use the new api.maton.ai endpoints.
- Added a security & permissions section, clarifying write operation requirements.
- Minor wording and formatting improvements in documentation.
- Removed the LICENSE.txt file.
v1.0.6
- Added homepage field to metadata for better discoverability and navigation to Maton platform.
- Minor metadata improvements; no changes to functionality or API usage.
v1.0.5
- Added a metadata section for clawdbot, specifying an emoji and required environment variable (MATON_API_KEY).
- No functional or API changes; documentation and compatibility remain the same.
v1.0.4
Version 1.0.4
- No file changes detected in this release.
- No updates or modifications to documentation or source code.
v1.0.3
- Added a note recommending the api-gateway skill for third party apps other than Notion.
- Replaced all shell/bash and JavaScript code examples with Python equivalents using `urllib.request` and standard libraries.
- Updated code snippets and quick start instructions to reflect the new Python-based examples for API usage and connection management.
- No changes to the API endpoints or core functionality; documentation updates only.
v1.0.2
- Clarified the gateway base URL pattern: use `/notion/{native-api-path}` instead of `/notion/v1/{endpoint}`.
- Added instructions for specifying the Notion connection via the new `Maton-Connection` header when multiple OAuth connections exist.
- Improved the "Getting Your API Key" section to mention account creation.
- Updated example connection response to include `creation_time`, `last_updated_time`, and `metadata`.
- Improved documentation formatting and consistency, with adjustments to connection management and quick start sections.
v1.0.1
- Clarified the relationship between databases and data sources: `GET /databases/{id}` now returns a `data_sources` array.
- Added an example output for the `GET /databases/{id}` data sources structure for clarity.
- Expanded connection management documentation with both "list connections" and "get single connection" response examples.
- Added example for the "Update Page Icon" endpoint.
- Improved explanations of endpoints and usage throughout for accuracy and consistency.
v1.0.0
- Initial release of Notion API integration with managed OAuth.
- Supports querying databases, creating/updating pages, and managing blocks in Notion workspaces.
- API gateway proxies requests to Notion API and handles OAuth token injection.
- Includes detailed setup instructions, API reference, connection management, and code examples (bash, JavaScript, Python).
- Databases and data sources are clearly separated for querying and schema updates.
- Comprehensive error handling and resource links provided.
Metadata
Frequently Asked Questions
What is Notion?
Notion API integration with managed OAuth. Query databases, search pages, and read workspace content. Write operations require explicit user confirmation of the target resource and connection. Use this skill when users want to interact with Notion workspaces, databases, or pages. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Notion connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Notion action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Notion examples; they add no Notion capability - Notion is itself an event source, so its own events are in `references/notion/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 11838 downloads so far.
How do I install Notion?
Run "/install notion-api-skill" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Notion free?
Yes, Notion is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Notion support?
Notion is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Notion?
It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.5.
More Skills