notion-automation
Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- notion-automation
- risk
- critical
- source
- community
- date_added
- 2026-02-27
- description
- Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas.
03 SKILL.md 正文
Notion Automation via Rube MCP
Automate Notion operations through Composio's Notion toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Notion connection via
RUBE_MANAGE_CONNECTIONSwith toolkitnotion - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitnotion - If connection is not ACTIVE, follow the returned auth link to complete Notion OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Create and Manage Pages
When to use: User wants to create, update, or archive Notion pages
Tool sequence:
NOTION_SEARCH_NOTION_PAGE- Find parent page or existing page [Prerequisite]NOTION_CREATE_NOTION_PAGE- Create a new page under a parent [Optional]NOTION_RETRIEVE_PAGE- Get page metadata/properties [Optional]NOTION_UPDATE_PAGE- Update page properties, title, icon, cover [Optional]NOTION_ARCHIVE_NOTION_PAGE- Soft-delete (archive) a page [Optional]
Key parameters:
query: Search text for SEARCH_NOTION_PAGEparent_id: Parent page or database IDpage_id: Page ID for retrieval/update/archiveproperties: Page property values matching parent schema
Pitfalls:
- RETRIEVE_PAGE returns only metadata/properties, NOT body content; use FETCH_BLOCK_CONTENTS for page body
- ARCHIVE_NOTION_PAGE is a soft-delete (sets archived=true), not permanent deletion
- Broad searches can look incomplete unless has_more/next_cursor is fully paginated
2. Query and Manage Databases
When to use: User wants to query database rows, insert entries, or update records
Tool sequence:
NOTION_SEARCH_NOTION_PAGE- Find the database by name [Prerequisite]NOTION_FETCH_DATABASE- Inspect schema and properties [Prerequisite]NOTION_QUERY_DATABASE/NOTION_QUERY_DATABASE_WITH_FILTER- Query rows [Required]NOTION_INSERT_ROW_DATABASE- Add new entries [Optional]NOTION_UPDATE_ROW_DATABASE- Update existing entries [Optional]
Key parameters:
database_id: Database ID (from search or URL)filter: Filter object matching Notion filter syntaxsorts: Array of sort objectsstart_cursor: Pagination cursor from previous responseproperties: Property values matching database schema for inserts/updates
Pitfalls:
- 404 object_not_found usually means wrong database_id or the database is not shared with the integration
- Results are paginated; ignoring has_more/next_cursor silently truncates reads
- Schema mismatches or missing required properties cause 400 validation_error
- Formula and read-only fields cannot be set via INSERT_ROW_DATABASE
- Property names in filters must match schema exactly (case-sensitive)
3. Manage Blocks and Page Content
When to use: User wants to read, append, or modify content blocks in a page
Tool sequence:
NOTION_FETCH_BLOCK_CONTENTS- Read child blocks of a page [Required]NOTION_ADD_MULTIPLE_PAGE_CONTENT- Append blocks to a page [Optional]NOTION_APPEND_TEXT_BLOCKS- Append text-only blocks [Optional]NOTION_REPLACE_PAGE_CONTENT- Replace all page content [Optional]NOTION_DELETE_BLOCK- Remove a specific block [Optional]
Key parameters:
block_id/page_id: Target page or block IDcontent_blocks: Array of block objects (NOT child_blocks)text: Plain text content for APPEND_TEXT_BLOCKS
Pitfalls:
- Use
content_blocksparameter, NOTchild_blocks-- the latter fails validation - ADD_MULTIPLE_PAGE_CONTENT fails on archived pages; unarchive via UPDATE_PAGE first
- Created blocks are in response.data.results; persist block IDs for later edits
- DELETE_BLOCK is archival (archived=true), not permanent deletion
4. Manage Database Schema
When to use: User wants to create databases or modify their structure
Tool sequence:
NOTION_FETCH_DATABASE- Inspect current schema [Prerequisite]NOTION_CREATE_DATABASE- Create a new database [Optional]NOTION_UPDATE_SCHEMA_DATABASE- Modify database properties [Optional]
Key parameters:
parent_id: Parent page ID for new databasestitle: Database titleproperties: Property definitions with types and optionsdatabase_id: Database ID for schema updates
Pitfalls:
- Cannot change property types via UPDATE_SCHEMA; must create new property and migrate data
- Formula, rollup, and relation properties have complex configuration requirements
5. Manage Users and Comments
When to use: User wants to list workspace users or manage comments on pages
Tool sequence:
NOTION_LIST_USERS- List all workspace users [Optional]NOTION_GET_ABOUT_ME- Get current authenticated user [Optional]NOTION_CREATE_COMMENT- Add a comment to a page [Optional]NOTION_FETCH_COMMENTS- List comments on a page [Optional]
Key parameters:
page_id: Page ID for comments (also calleddiscussion_id)rich_text: Comment content as rich text array
Pitfalls:
- Comments are linked to pages, not individual blocks
- User IDs from LIST_USERS are needed for people-type property filters
Common Patterns
ID Resolution
Page/Database name -> ID:
1. Call NOTION_SEARCH_NOTION_PAGE with query=name
2. Paginate with has_more/next_cursor until found
3. Extract id from matching result
Database schema inspection:
1. Call NOTION_FETCH_DATABASE with database_id
2. Extract properties object for field names and types
3. Use exact property names in queries and inserts
Pagination
- Set
page_sizefor results per page (max 100) - Check response for
has_moreboolean - Pass
start_cursorornext_cursorin next request - Continue until
has_moreis false
Notion Filter Syntax
Single filter:
{"property": "Status", "select": {"equals": "Done"}}
Compound filter:
{"and": [
{"property": "Status", "select": {"equals": "In Progress"}},
{"property": "Assignee", "people": {"contains": "user-id"}}
]}
Known Pitfalls
Integration Sharing:
- Pages and databases must be shared with the Notion integration to be accessible
- Title queries can return 0 when the item is not shared with the integration
Property Types:
- Property names are case-sensitive and must match schema exactly
- Formula, rollup, and created_time fields are read-only
- Select/multi-select values must match existing options unless creating new ones
Response Parsing:
- Response data may be nested under
data_previewordata.results - Parse defensively with fallbacks for different nesting levels
Quick Reference
| Task | Tool Slug | Key Params |
|---|---|---|
| Search pages/databases | NOTION_SEARCH_NOTION_PAGE | query |
| Create page | NOTION_CREATE_NOTION_PAGE | parent_id, properties |
| Get page metadata | NOTION_RETRIEVE_PAGE | page_id |
| Update page | NOTION_UPDATE_PAGE | page_id, properties |
| Archive page | NOTION_ARCHIVE_NOTION_PAGE | page_id |
| Duplicate page | NOTION_DUPLICATE_PAGE | page_id |
| Get page blocks | NOTION_FETCH_BLOCK_CONTENTS | block_id |
| Append blocks | NOTION_ADD_MULTIPLE_PAGE_CONTENT | page_id, content_blocks |
| Append text | NOTION_APPEND_TEXT_BLOCKS | page_id, text |
| Replace content | NOTION_REPLACE_PAGE_CONTENT | page_id, content_blocks |
| Delete block | NOTION_DELETE_BLOCK | block_id |
| Query database | NOTION_QUERY_DATABASE | database_id, filter, sorts |
| Query with filter | NOTION_QUERY_DATABASE_WITH_FILTER | database_id, filter |
| Insert row | NOTION_INSERT_ROW_DATABASE | database_id, properties |
| Update row | NOTION_UPDATE_ROW_DATABASE | page_id, properties |
| Get database schema | NOTION_FETCH_DATABASE | database_id |
| Create database | NOTION_CREATE_DATABASE | parent_id, title, properties |
| Update schema | NOTION_UPDATE_SCHEMA_DATABASE | database_id, properties |
| List users | NOTION_LIST_USERS | (none) |
| Create comment | NOTION_CREATE_COMMENT | page_id, rich_text |
| List comments | NOTION_FETCH_COMMENTS | page_id |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.