
About
Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas.
name: notion-automation description: "Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas." risk: critical source: community date_added: "2026-02-27"
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 configurati
