Notion

Bulk-add content blocks to Notion. CRITICAL: Notion API enforces 2000 char limit per text.content field. Features: - Accepts simplified format: {'content': 'text', 'block_property': 'type'} - OR full Notion block format with 'type' and properties - AUTO-SPLITS text >2000 chars into multiple blocks - AUTO-PARSES markdown: **bold**, *italic*, ~~strike~~, `inline code`, [links](url) - Maximum 100 blocks per API call REQUIRED 'content' for: paragraph, heading_1-3, callout, to_do, toggle, quote, list items. For code blocks use full format: {'type': 'code', 'code': {'rich_text': [...], 'language': 'python'}} Common errors: - "content.length should be ≤ 2000": Auto-split failed, manually split content - "Content is required": Missing content for text blocks - Each item MUST be wrapped in 'content_block' field

DEPRECATED: Use 'add_multiple_page_content' for better performance. Adds a single content block to a Notion page/block. CRITICAL: Notion API enforces a HARD LIMIT of 2000 characters per text.content field. Content exceeding 2000 chars is AUTOMATICALLY SPLIT into multiple sequential blocks. REQUIRED 'content' field for text blocks: paragraph, heading_1-3, callout, to_do, toggle, quote, list items. Parent blocks MUST be: Page, Toggle, To-do, Bulleted/Numbered List Item, Callout, or Quote. Common errors: - "content.length should be ≤ 2000": Text exceeds API limit (should be auto-handled) - "Content is required for paragraph blocks": Missing 'content' field for text blocks - "object_not_found": Invalid parent_block_id or no integration access For bulk operations, use 'add_multiple_page_content' instead.

Appends raw Notion API blocks to parent. CRITICAL: Text content limited to 2000 chars per text.content field. Use for: Advanced blocks (tables, databases), pre-built block objects, complex nested structures. REQUIRES exact Notion block schema - each block MUST have 'object':'block' and 'type'. Text blocks MUST use rich_text arrays: {'rich_text': [{'type': 'text', 'text': {'content': 'text'}}]} Common errors: - "content.length should be ≤ 2000": Text exceeds API limit, split into multiple blocks - "validation_error": Using 'text' instead of 'rich_text' for headings/paragraphs - "object_not_found": Invalid block_id or no integration access - Missing 'object': 'block' or 'type' fields For simple content, use 'add_multiple_page_content' instead - it handles formatting automatically.

Archives (moves to trash) or unarchives (restores from trash) a specified Notion page.

Adds a comment to a Notion page (via `parent_page_id`) OR to an existing discussion thread (via `discussion_id`); cannot create new discussion threads on specific blocks (inline comments).

Creates a new Notion database as a subpage under a specified parent page with a defined properties schema. IMPORTANT NOTES: - The parent page MUST be shared with your integration, otherwise you'll get a 404 error - If you encounter conflict errors (409), retry the request as Notion may experience temporary save conflicts - For relation properties, you MUST provide the database_id of the related database - Parent ID must be a valid UUID format (with or without hyphens), not a template variable Use this action exclusively for creating new databases.

Tool to create a Notion FileUpload object and retrieve an upload URL. Use when you need to automate attaching local or external files directly into Notion without external hosting.

Creates a new empty page in a Notion workspace under a specified parent page or database. PREREQUISITES: - Parent page/database must exist and be accessible in your Notion workspace - Use search_pages or list_databases first to obtain valid parent IDs LIMITATIONS: - Cannot create root-level pages (must have a parent) - May encounter conflicts if creating pages too quickly - Title-based parent search is less reliable than using UUIDs

Archives a Notion block, page, or database using its ID, which sets its 'archived' property to true (like moving to "Trash" in the UI) and allows it to be restored later.

Duplicates a Notion page, including all its content, properties, and nested blocks, under a specified parent page or workspace.

Retrieves a paginated list of direct, first-level child block objects along with contents for a given parent Notion block or page ID; use block IDs from the response for subsequent calls to access deeply nested content.

Fetches metadata for a Notion block (including pages, which are special blocks) using its UUID. Returns block type, properties, and basic info but not child content. Prerequisites: 1) Block/page must be shared with your integration, 2) Use valid block_id from API responses (not URLs). For child blocks, use fetch_block_contents instead. Common 404 errors mean the block isn't accessible to your integration.

Fetches unresolved comments for a specified Notion block or page ID.

Fetches Notion items (pages and/or databases) from the Notion workspace, use this to get minimal data about the items in the workspace with a query or list all items in the workspace with minimal data

Fetches a Notion database's structural metadata (properties, title, etc.) via its `database_id`, not the data entries; `database_id` must reference an existing database.

Retrieves a Notion database row's properties and metadata; use fetch_block_contents for page content blocks.

Retrieves the User object for the bot associated with the current Notion integration token, typically to obtain the bot's user ID for other API operations.

Retrieves detailed information about a specific Notion user, such as their name, avatar, and email, based on their unique user ID.

Call this to get a specific property from a Notion page when you have a valid `page_id` and `property_id`; handles pagination for properties returning multiple items.

Creates a new page (row) in a specified Notion database. Prerequisites: - The database must be explicitly shared with your Notion integration - Property names and types must match the database schema exactly - Select/multi-select options must already exist in the database Common Errors: - 404 "Could not find database": Database is not shared with your integration - 400 "Status is not a property": Using 'status' type incorrectly (use 'select' instead) - Validation error on properties: Properties must be provided as a list, not a dictionary

Retrieves a paginated list of users (excluding guests) from the Notion workspace; the number of users returned per page may be less than the requested `page_size`.

Queries a Notion database to retrieve pages (rows). In Notion, databases are collections where each row is a page and columns are properties. Returns paginated results with metadata. Important requirements: - The database must be shared with your integration - Property names in sorts must match existing database properties exactly (case-sensitive) - The start_cursor must be a valid UUID from a previous response's next_cursor field - Database IDs must be valid 32-character UUIDs (with or without hyphens) Use this action to: - Retrieve all or filtered database entries - Sort results by one or more properties - Paginate through large result sets - Get database content for processing or display

Tool to query a Notion database with server-side filtering, sorting, and pagination. Use when you need to retrieve a subset of rows by property, date, status, or other conditions.

Tool to retrieve a specific comment by its ID. Use when you have a comment ID and need to fetch its details.

Tool to retrieve a specific property object of a Notion database. Use when you need to get details about a single database column/property.

Searches Notion pages and databases by title; an empty query lists all accessible items, useful for discovering IDs or as a fallback when a specific query yields no results.

Updates existing Notion block's text content. ⚠️ CRITICAL: Content limited to 2000 chars. Cannot change block type or archive blocks. Content exceeding 2000 chars will fail with validation error. For longer content, split across multiple blocks using add_multiple_page_content.

Update page properties, icon, cover, or archive status. Requires at least one update parameter. Common errors: - "Invalid property identifier": Property name doesn't exist - use exact names from your database - "should be defined": Property value missing wrapper - always wrap: {'Field': {'type': value}} - "Input should be a valid dictionary": Properties must be dict, not list Property formats by type: - title/rich_text: {'text': {'content': 'value'}} - select/status: {'name': 'option'} - url: plain string needs {'url': 'string'} wrapper - number: plain number needs {'number': value} wrapper

Updates a Notion database row (page) by its UUID. Common issues: (1) Use UUID from page URL, not the full URL, (2) Ensure page is shared with integration, (3) Match property names exactly as in database, (4) Use 'status' type for Status properties, not 'select', (5) Retry on 409 Conflict errors (concurrent updates). Supports updating properties, icon, cover, or archiving the row.

Updates an existing Notion database's schema including title, description, and/or properties (columns). IMPORTANT NOTES: - At least one update (title, description, or properties) must be provided - The database must be shared with your integration - Property names are case-sensitive and must match exactly - When changing a property to 'relation' type, you MUST provide the database_id of the target database - Removing properties will permanently delete that column and its data - Use NOTION_FETCH_DATA first to get the exact property names and database structure Common errors: - 'database_id' missing: Ensure you're passing the database_id parameter (not page_id) - 'data_source_id' undefined: When changing to relation type, database_id is required in PropertySchemaUpdate - Property name mismatch: Names must match exactly including case and special characters