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_CONNECTIONS with toolkit notion
- Always call
RUBE_SEARCH_TOOLS first 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_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit notion
- 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_PAGE
parent_id: Parent page or database ID
page_id: Page ID for retrieval/update/archive
properties: 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 syntax
sorts: Array of sort objects
start_cursor: Pagination cursor from previous response
properties: 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 ID
content_blocks: Array of block objects (NOT child_blocks)
text: Plain text content for APPEND_TEXT_BLOCKS
Pitfalls:
- Use
content_blocks parameter, NOT child_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 databases
title: Database title
properties: Property definitions with types and options
database_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 called discussion_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_size for results per page (max 100)
- Check response for
has_more boolean
- Pass
start_cursor or next_cursor in next request
- Continue until
has_more is 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_preview or data.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.
1---
2name: notion-automation
3description: 'Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas.'
4metadata:
5 source: https://skillmd.com/skills/sickn33/notion-automation
6 aas-risk: critical
7 aas-source: community
8 aas-date-added: '2026-02-27'
9---
10
11# Notion Automation via Rube MCP
12
13Automate Notion operations through Composio's Notion toolkit via Rube MCP.
14
15## Prerequisites
16
17- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
18- Active Notion connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `notion`
19- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
20
21## Setup
22
23**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.
24
25
261. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
272. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `notion`
283. If connection is not ACTIVE, follow the returned auth link to complete Notion OAuth
294. Confirm connection status shows ACTIVE before running any workflows
30
31## Core Workflows
32
33### 1. Create and Manage Pages
34
35**When to use**: User wants to create, update, or archive Notion pages
36
37**Tool sequence**:
381. `NOTION_SEARCH_NOTION_PAGE` - Find parent page or existing page [Prerequisite]
392. `NOTION_CREATE_NOTION_PAGE` - Create a new page under a parent [Optional]
403. `NOTION_RETRIEVE_PAGE` - Get page metadata/properties [Optional]
414. `NOTION_UPDATE_PAGE` - Update page properties, title, icon, cover [Optional]
425. `NOTION_ARCHIVE_NOTION_PAGE` - Soft-delete (archive) a page [Optional]
43
44**Key parameters**:
45- `query`: Search text for SEARCH_NOTION_PAGE
46- `parent_id`: Parent page or database ID
47- `page_id`: Page ID for retrieval/update/archive
48- `properties`: Page property values matching parent schema
49
50**Pitfalls**:
51- RETRIEVE_PAGE returns only metadata/properties, NOT body content; use FETCH_BLOCK_CONTENTS for page body
52- ARCHIVE_NOTION_PAGE is a soft-delete (sets archived=true), not permanent deletion
53- Broad searches can look incomplete unless has_more/next_cursor is fully paginated
54
55### 2. Query and Manage Databases
56
57**When to use**: User wants to query database rows, insert entries, or update records
58
59**Tool sequence**:
601. `NOTION_SEARCH_NOTION_PAGE` - Find the database by name [Prerequisite]
612. `NOTION_FETCH_DATABASE` - Inspect schema and properties [Prerequisite]
623. `NOTION_QUERY_DATABASE` / `NOTION_QUERY_DATABASE_WITH_FILTER` - Query rows [Required]
634. `NOTION_INSERT_ROW_DATABASE` - Add new entries [Optional]
645. `NOTION_UPDATE_ROW_DATABASE` - Update existing entries [Optional]
65
66**Key parameters**:
67- `database_id`: Database ID (from search or URL)
68- `filter`: Filter object matching Notion filter syntax
69- `sorts`: Array of sort objects
70- `start_cursor`: Pagination cursor from previous response
71- `properties`: Property values matching database schema for inserts/updates
72
73**Pitfalls**:
74- 404 object_not_found usually means wrong database_id or the database is not shared with the integration
75- Results are paginated; ignoring has_more/next_cursor silently truncates reads
76- Schema mismatches or missing required properties cause 400 validation_error
77- Formula and read-only fields cannot be set via INSERT_ROW_DATABASE
78- Property names in filters must match schema exactly (case-sensitive)
79
80### 3. Manage Blocks and Page Content
81
82**When to use**: User wants to read, append, or modify content blocks in a page
83
84**Tool sequence**:
851. `NOTION_FETCH_BLOCK_CONTENTS` - Read child blocks of a page [Required]
862. `NOTION_ADD_MULTIPLE_PAGE_CONTENT` - Append blocks to a page [Optional]
873. `NOTION_APPEND_TEXT_BLOCKS` - Append text-only blocks [Optional]
884. `NOTION_REPLACE_PAGE_CONTENT` - Replace all page content [Optional]
895. `NOTION_DELETE_BLOCK` - Remove a specific block [Optional]
90
91**Key parameters**:
92- `block_id` / `page_id`: Target page or block ID
93- `content_blocks`: Array of block objects (NOT child_blocks)
94- `text`: Plain text content for APPEND_TEXT_BLOCKS
95
96**Pitfalls**:
97- Use `content_blocks` parameter, NOT `child_blocks` -- the latter fails validation
98- ADD_MULTIPLE_PAGE_CONTENT fails on archived pages; unarchive via UPDATE_PAGE first
99- Created blocks are in response.data.results; persist block IDs for later edits
100- DELETE_BLOCK is archival (archived=true), not permanent deletion
101
102### 4. Manage Database Schema
103
104**When to use**: User wants to create databases or modify their structure
105
106**Tool sequence**:
1071. `NOTION_FETCH_DATABASE` - Inspect current schema [Prerequisite]
1082. `NOTION_CREATE_DATABASE` - Create a new database [Optional]
1093. `NOTION_UPDATE_SCHEMA_DATABASE` - Modify database properties [Optional]
110
111**Key parameters**:
112- `parent_id`: Parent page ID for new databases
113- `title`: Database title
114- `properties`: Property definitions with types and options
115- `database_id`: Database ID for schema updates
116
117**Pitfalls**:
118- Cannot change property types via UPDATE_SCHEMA; must create new property and migrate data
119- Formula, rollup, and relation properties have complex configuration requirements
120
121### 5. Manage Users and Comments
122
123**When to use**: User wants to list workspace users or manage comments on pages
124
125**Tool sequence**:
1261. `NOTION_LIST_USERS` - List all workspace users [Optional]
1272. `NOTION_GET_ABOUT_ME` - Get current authenticated user [Optional]
1283. `NOTION_CREATE_COMMENT` - Add a comment to a page [Optional]
1294. `NOTION_FETCH_COMMENTS` - List comments on a page [Optional]
130
131**Key parameters**:
132- `page_id`: Page ID for comments (also called `discussion_id`)
133- `rich_text`: Comment content as rich text array
134
135**Pitfalls**:
136- Comments are linked to pages, not individual blocks
137- User IDs from LIST_USERS are needed for people-type property filters
138
139## Common Patterns
140
141### ID Resolution
142
143**Page/Database name -> ID**:
144```
1451. Call NOTION_SEARCH_NOTION_PAGE with query=name
1462. Paginate with has_more/next_cursor until found
1473. Extract id from matching result
148```
149
150**Database schema inspection**:
151```
1521. Call NOTION_FETCH_DATABASE with database_id
1532. Extract properties object for field names and types
1543. Use exact property names in queries and inserts
155```
156
157### Pagination
158
159- Set `page_size` for results per page (max 100)
160- Check response for `has_more` boolean
161- Pass `start_cursor` or `next_cursor` in next request
162- Continue until `has_more` is false
163
164### Notion Filter Syntax
165
166**Single filter**:
167```json
168{"property": "Status", "select": {"equals": "Done"}}
169```
170
171**Compound filter**:
172```json
173{"and": [
174 {"property": "Status", "select": {"equals": "In Progress"}},
175 {"property": "Assignee", "people": {"contains": "user-id"}}
176]}
177```
178
179## Known Pitfalls
180
181**Integration Sharing**:
182- Pages and databases must be shared with the Notion integration to be accessible
183- Title queries can return 0 when the item is not shared with the integration
184
185**Property Types**:
186- Property names are case-sensitive and must match schema exactly
187- Formula, rollup, and created_time fields are read-only
188- Select/multi-select values must match existing options unless creating new ones
189
190**Response Parsing**:
191- Response data may be nested under `data_preview` or `data.results`
192- Parse defensively with fallbacks for different nesting levels
193
194## Quick Reference
195
196| Task | Tool Slug | Key Params |
197|------|-----------|------------|
198| Search pages/databases | NOTION_SEARCH_NOTION_PAGE | query |
199| Create page | NOTION_CREATE_NOTION_PAGE | parent_id, properties |
200| Get page metadata | NOTION_RETRIEVE_PAGE | page_id |
201| Update page | NOTION_UPDATE_PAGE | page_id, properties |
202| Archive page | NOTION_ARCHIVE_NOTION_PAGE | page_id |
203| Duplicate page | NOTION_DUPLICATE_PAGE | page_id |
204| Get page blocks | NOTION_FETCH_BLOCK_CONTENTS | block_id |
205| Append blocks | NOTION_ADD_MULTIPLE_PAGE_CONTENT | page_id, content_blocks |
206| Append text | NOTION_APPEND_TEXT_BLOCKS | page_id, text |
207| Replace content | NOTION_REPLACE_PAGE_CONTENT | page_id, content_blocks |
208| Delete block | NOTION_DELETE_BLOCK | block_id |
209| Query database | NOTION_QUERY_DATABASE | database_id, filter, sorts |
210| Query with filter | NOTION_QUERY_DATABASE_WITH_FILTER | database_id, filter |
211| Insert row | NOTION_INSERT_ROW_DATABASE | database_id, properties |
212| Update row | NOTION_UPDATE_ROW_DATABASE | page_id, properties |
213| Get database schema | NOTION_FETCH_DATABASE | database_id |
214| Create database | NOTION_CREATE_DATABASE | parent_id, title, properties |
215| Update schema | NOTION_UPDATE_SCHEMA_DATABASE | database_id, properties |
216| List users | NOTION_LIST_USERS | (none) |
217| Create comment | NOTION_CREATE_COMMENT | page_id, rich_text |
218| List comments | NOTION_FETCH_COMMENTS | page_id |
219
220## When to Use
221This skill is applicable to execute the workflow or actions described in the overview.
222
223## Limitations
224- Use this skill only when the task clearly matches the scope described above.
225- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
226- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.