NAiOS IconNAiOS Logo
Volver al catálogo

Notion

notion

Notion centralizes notes, docs, wikis, and tasks in a unified workspace, letting teams build custom workflows for collaboration and knowledge management

Acciones
28
Triggers
13
Autenticación
OAuth gestionado
Información técnica: el detalle de parámetros, schemas y triggers de esta página está pensado para equipos de integración. Si solo necesitas saber si tu herramienta favorita está disponible, basta con ver la lista de acciones.

Acciones disponibles (28)

Cada acción es una operación que el agente puede ejecutar contra este conector. Haz clic en una acción para ver sus parámetros.

Add multiple content blocks (bulk, user-friendly)NOTION_ADD_MULTIPLE_PAGE_CONTENTAcción

Efficiently adds multiple standard content blocks to a notion page in a single api call with automatic markdown parsing. the 'content' field in notionrichtext blocks now automatically detects and parses markdown formatting including headers (# ## ###), bold (**text**), italic (*text*), strikethrough (~~text~~), inline code (`code`), links ([text](url)), and more. ideal for bulk content creation, ai agents, and replacing multiple individual add page content calls. supports automatic text formatting, content splitting, and up to 100 blocks per request.

Parámetros de entrada

  • afterstring

    Identifier of an existing block. The new content blocks will be appended immediately after this block. If omitted or null, the new blocks are appended to the end of the parent's children list.

  • content_blocksobject[]Obligatorio

    A list of content blocks to be added to the page. Each block can use either the flattened NotionRichText schema or full Notion block structure. ENHANCED: The 'content' field in NotionRichText now automatically detects and parses markdown formatting - supports headers (# ## ###), bold (**text**), italic (*text*), strikethrough (~~text~~), inline code (`code`), links ([text](url)), and more. Maximum of 100 blocks per request.

  • parent_block_idstringObligatorio

    Identifier of the parent page or block to which the new content blocks will be added. This parent must be capable of having child blocks. Obtain valid IDs using other Notion actions or API calls.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Add content to Notion pageNOTION_ADD_PAGE_CONTENTAcción

Deprecated: appends a single content block to a notion page or a parent block (must be page, toggle, to-do, bulleted/numbered list, callout, or quote); invoke repeatedly to add multiple blocks.

Parámetros de entrada

  • afterstring

    Identifier of an existing block. The new content block will be appended immediately after this block. If omitted or null, the new block is appended to the end of the parent's children list.

  • content_blockobjectObligatorio

    Include these fields in the json: {'content': 'Some words', 'link': 'https://random-link.com'. For content styling, refer to https://developers.notion.com/reference/rich-text. ENHANCED: The 'content' field now automatically detects and parses markdown formatting - supports bold (**text**), italic (*text*), strikethrough (~~text~~), inline code (`code`), and links ([text](url)). Headers (# ## ###) are handled via block_property.

  • parent_block_idstringObligatorio

    Identifier of the parent page or block to which the new content block will be added. This parent must be capable of having child blocks. Obtain valid IDs using other Notion actions or API calls.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Append complex blocks (advanced, full control)NOTION_APPEND_BLOCK_CHILDRENAcción

Appends complex blocks with full notion block structure to a parent block or page. use for advanced scenarios requiring precise control: code blocks, tables, embeds, nested children within blocks, or when working with pre-built notion block objects. requires full notion api block schema - use add multiple page content for simpler content creation.

Parámetros de entrada

  • afterstring

    An optional ID of an existing child block. If provided, the new blocks will be inserted directly after this specified block. If omitted, new blocks are appended to the end of the parent's children list.

  • block_idstringObligatorio

    Identifier of the parent block or page to which new child blocks will be appended. To find available page IDs and their titles, the `NOTION_FETCH_DATA` action can be utilized.

  • childrenobject[]Obligatorio

    A list of block objects to be added as children to the parent block. Each block object must conform to Notion's block structure. A maximum of 100 blocks can be appended in a single request.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Archive Notion PageNOTION_ARCHIVE_NOTION_PAGEAcción

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

Parámetros de entrada

  • archiveboolean

    Set to `true` to move the page to trash (archive), or `false` to restore it from trash (unarchive). Defaults to `true`.

  • page_idstringObligatorio

    The unique identifier (UUID) of the Notion page to be archived or unarchived. This page must already exist in the Notion workspace. Page IDs can be obtained using other Notion actions that retrieve or search for pages.

Parámetros de salida

  • dataobjectObligatorio

    Represents the updated Notion page object, reflecting its new archive status with the `in_trash` property updated.

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Create commentNOTION_CREATE_COMMENTAcción

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).

Parámetros de entrada

  • commentobjectObligatorio

    Content of the comment as a NotionRichText object. Simplest form: {'content': 'Looks good!'} (optional styling fields: bold, italic, link, etc.). Do NOT wrap this in a list or use Notion API block JSON.

  • discussion_idstring

    The ID of an existing discussion thread to which the comment will be added. This is required if `parent_page_id` is not provided.

  • parent_page_idstring

    The ID of the Notion page where the comment will be added. This is required if `discussion_id` is not provided. Page IDs can be obtained using other Notion actions that fetch page details or list pages.

Parámetros de salida

  • dataobjectObligatorio

    A dictionary containing the full JSON response from the Notion API, which includes the details of the newly created comment object.

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Create Notion DatabaseNOTION_CREATE_DATABASEAcción

Creates a new notion database as a subpage under a specified parent page with a defined properties schema; use this action exclusively for creating new databases.

Parámetros de entrada

  • titlestringObligatorio

    The desired title for the new database. This text will be automatically converted into Notion's rich text format when the database is created.

  • parent_idstringObligatorio

    Identifier of the existing Notion page that will contain the new database. This ID must be a valid UUID corresponding to a page within the Notion workspace. It can often be obtained using search functionalities or the `NOTION_FETCH_DATA` action.

  • propertiesobject[]Obligatorio

    A list defining the schema (columns) for the new database. Each item in the list is an object representing a property and must specify at least its 'name' (how it will appear in Notion) and 'type' (the kind of data it will hold). Refer to the `PropertySchema` model for full structure details. At least one property of type 'title' is generally required. Common supported property types include: 'title', 'rich_text', 'number', 'select', 'multi_select', 'status', 'date', 'people', 'files', 'checkbox', 'url', 'email', 'phone_number'. Other types like 'formula', 'relation', 'rollup', 'created_time', 'created_by', 'last_edited_time', 'last_edited_by' might also be supported.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Create Notion pageNOTION_CREATE_NOTION_PAGEAcción

Creates a new empty page in a notion workspace.

Parámetros de entrada

  • iconstring

    An emoji to be used as the icon for the new page. Must be a single emoji character.

  • coverstring

    The URL of an image to be used as the cover for the new page. The URL must be publicly accessible.

  • titlestringObligatorio

    The title of the new page to be created.

  • parent_idstringObligatorio

    The UUID of the parent page or database under which the new page will be created. This ID must correspond to an existing page or database in the Notion workspace. Use other Notion actions (e.g., for searching or fetching data) to obtain valid parent IDs.

Parámetros de salida

  • dataobjectObligatorio

    A dictionary representing the newly created page object, including its ID, parent information, creation time, last edited time, and properties, as returned by the Notion API.

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Delete a blockNOTION_DELETE_BLOCKAcción

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.

Parámetros de entrada

  • block_idstringObligatorio

    Identifier of the block, page, or database to be deleted (archived). To find page IDs and their titles, consider using an action like `NOTION_FETCH_DATA`.

Parámetros de salida

  • dataobjectObligatorio

    A dictionary representing the block object that was successfully archived. This object includes an 'archived': true key-value pair, confirming the deletion.

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Duplicate pageNOTION_DUPLICATE_PAGEAcción

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

Parámetros de entrada

  • titlestring

    An optional new title for the duplicated page. If not provided, the title of the original page will be used, prefixed with 'Copy of'.

  • page_idstringObligatorio

    The unique identifier (UUID v4) of the Notion page to be duplicated. Ensure this page exists and is accessible.

  • parent_idstringObligatorio

    The unique identifier (UUID v4) of the Notion page or workspace that will serve as the parent for the duplicated page. Ensure this parent exists and is accessible. This ID cannot be the same as `page_id`.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Fetch Notion Block ChildrenNOTION_FETCH_BLOCK_CONTENTSAcción

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.

Parámetros de entrada

  • block_idstringObligatoriouuid

    Identifier (UUID) of the parent Notion block or page whose children are to be fetched. This ID can be for a block or a page (as pages are blocks). To obtain relevant IDs and their titles, consider using actions like 'NOTION_FETCH_DATA' or other actions that list pages or database content.

  • page_sizeinteger

    The maximum number of child blocks to return in a single response. The actual number of results may be lower if there are fewer child blocks available or if the end of the list is reached. Maximum allowed value is 100. If unspecified, Notion's default page size will be used.

  • start_cursorstring

    An opaque string. If provided, the response will list blocks starting from the position indicated by this cursor. If omitted, the first page of results is returned. Essential for paginating through a large number of child blocks.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Fetch Notion block metadataNOTION_FETCH_BLOCK_METADATAAcción

Fetches metadata for a notion block (or page, as pages are blocks) using its valid uuid; if the block has children, use fetch block contents to fetch their contents.

Parámetros de entrada

  • block_idstringObligatoriouuid

    The unique UUID identifier for the Notion block to be retrieved. This can be the ID of a standard block or a page. To find block or page IDs, you might use actions that list page content or search for blocks/pages.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Fetch commentsNOTION_FETCH_COMMENTSAcción

Fetches unresolved comments for a specified notion block or page id.

Parámetros de entrada

  • block_idstringObligatorio

    Identifier for a Notion block or page from which to fetch comments. To find page IDs, use the `NOTION_FETCH_DATA` action to list available pages and their corresponding IDs.

  • page_sizeinteger

    The number of comments to return in a single response page. Must be between 1 and 100, inclusive. Default is 100.

  • start_cursorstring

    A pagination cursor. If provided, the response will contain the page of results starting after this cursor. If omitted, the first page of results is returned.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Fetch Notion DataNOTION_FETCH_DATAAcción

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

Parámetros de entrada

  • querystring

    An optional search query to filter pages and/or databases by their title or content. If not provided (None or empty string), all accessible items matching the selected type (pages, databases, or both) are returned.

  • get_allboolean

    If true, fetches both pages and databases accessible to the Notion integration. Only one of `get_pages`, `get_databases`, or `get_all` can be true.

  • get_pagesboolean

    If true, fetches all pages accessible to the Notion integration. Only one of `get_pages`, `get_databases`, or `get_all` can be true.

  • page_sizeinteger

    The maximum number of items to retrieve. Must be between 1 and 100, inclusive. Defaults to 100. Note: this action currently only fetches the first page of results, so `page_size` effectively sets the maximum number of items returned.

  • get_databasesboolean

    If true, fetches all databases accessible to the Notion integration. Only one of `get_pages`, `get_databases`, or `get_all` can be true.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Fetch DatabaseNOTION_FETCH_DATABASEAcción

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.

Parámetros de entrada

  • database_idstringObligatorio

    The unique identifier of the Notion database whose metadata (structure, properties) is to be retrieved. To obtain a list of `database_id` values and corresponding database titles, use the 'NOTION_FETCH_DATA' action (or a similar action designed for listing/discovering databases). Note: Linked databases are not supported; the ID must reference an actual database, not a linked database.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Fetch database rowNOTION_FETCH_ROWAcción

Retrieves a notion database row's properties and metadata; use fetch block contents for page content blocks.

Parámetros de entrada

  • page_idstringObligatorio

    The UUID of the Notion page (which represents a row in a database) to retrieve. Each row in a Notion database is a page. You can obtain `page_id` values by using an action that lists database pages (e.g., `NOTION_FETCH_DATA`) to get available page IDs and their titles.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Get About MeNOTION_GET_ABOUT_MEAcción

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.

Parámetros de entrada

Sin parámetros.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Get about userNOTION_GET_ABOUT_USERAcción

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

Parámetros de entrada

  • user_idstringObligatorio

    The unique identifier of the Notion user whose details are to be retrieved. This ID is used to fetch specific user information.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Get page propertyNOTION_GET_PAGE_PROPERTY_ACTIONAcción

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.

Parámetros de entrada

  • page_idstringObligatorio

    Identifier of the Notion page (e.g., '067dd719-a912-471e-a9a3-ac10710e78b4') from which to retrieve the property. Use the 'NOTION_FETCH_DATA' action or similar to discover available page IDs and their titles.

  • page_sizeinteger

    For paginated property types (e.g., 'relation', 'rollup', 'rich_text' if content is extensive), this specifies the number of items to return per request. If omitted, Notion's default page size for the property is used.

  • property_idstringObligatorio

    Identifier or name of the property to retrieve. For 'title' properties, the ID is always 'title'. For other properties, this can be the property's name as displayed in Notion (e.g., 'Status', 'Assignee') or its unique programmatic ID (e.g., 'N%3A%5B%7C', 'prop_id_example'). Property IDs/names can be found by inspecting the page object or database schema.

  • start_cursorstring

    For paginated properties, if a previous request's response indicated `has_more: true`, provide the `next_cursor` value here to fetch the subsequent set of items. Omit if fetching the first page.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Insert row databaseNOTION_INSERT_ROW_DATABASEAcción

Creates a new page (row) in a specified notion database.

Parámetros de entrada

  • iconstring

    Emoji to be used as the page icon. Must be a single emoji character.

  • coverstring

    URL of an external image to set as the page cover. The URL must point to a publicly accessible image.

  • propertiesobject[]

    Property values for the new page. IMPORTANT: This field requires a LIST of objects, not a dictionary. Each object in the list defines a property and must include: `name` (the exact name of the property as it appears in Notion), `type` (the property's data type), and `value` (the property's value, formatted as a string according to its type). CORRECT FORMAT EXAMPLE (a list of property objects): [ {"name": "Title", "type": "title", "value": "My new task"}, {"name": "Status", "type": "select", "value": "In Progress"}, {"name": "Tags", "type": "multi_select", "value": "Work,Personal"}, {"name": "Due Date", "type": "date", "value": "2024-06-01T12:00:00.000-04:00"}, {"name": "Completed", "type": "checkbox", "value": "False"} ] INCORRECT FORMAT (e.g., a dictionary instead of a list): { "Title": "My new task", "Status": "In Progress" } Value formatting rules by property type: - `title` or `rich_text`: Plain text string (maximum 2000 characters). - `number`: String representation of a number (e.g., "23.4"). - `select`: The name of an existing option for the select property (e.g., "In Progress"). - `multi_select`: Comma-separated string of existing option names (e.g., "Work,Personal"). - `date`: ISO 8601 formatted date string (e.g., "2024-06-01T12:00:00.000-04:00"). - `people`: Comma-separated string of Notion user IDs. - `checkbox`: String "True" or "False". - `url`: A valid URL string. - `files`: Comma-separated string of URLs. Properties defined in the database schema but omitted from this list will be initialized with default or empty values. Ensure that property names and types correctly match the target database schema.

  • database_idstringObligatorio

    Identifier (UUID) of the Notion database where the new page (row) will be inserted. This ID must correspond to an existing database accessible to the integration. Use the `NOTION_FETCH_DATA` action to find available database IDs.

  • child_blocksobject[]

    A list of `NotionRichText` objects defining content blocks (e.g., paragraphs, headings) to append to the new page's body. If omitted, the page body will be empty.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

List usersNOTION_LIST_USERSAcción

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`.

Parámetros de entrada

  • page_sizeinteger

    The desired number of users to retrieve per page. The maximum value is 100.

  • start_cursorstring

    If omitted, retrieves the first page of users. Use the 'next_cursor' value from a previous response to get the next page.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Query databaseNOTION_QUERY_DATABASEAcción

Queries a notion database for pages (rows), where rows are pages and columns are properties; ensure sort property names correspond to existing database properties.

Parámetros de entrada

  • sortsobject[]

    List of sort rules. Each item must use the keys 'property_name' and 'ascending'. Example: [{'property_name': 'Due', 'ascending': False}]

  • page_sizeinteger

    The maximum number of items (pages or rows) to return in a single response. Defaults to 2. The actual number of items returned may be less than this value.

  • database_idstringObligatorio

    Identifier of the Notion database to query. To discover available database IDs and their corresponding titles, you can use an action like `NOTION_FETCH_DATA` or inspect the database in Notion.

  • start_cursorstring

    An opaque cursor for pagination, used to retrieve the next set of results. This value is obtained from the `next_cursor` field in a previous response. If omitted, retrieves results from the beginning.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Retrieve CommentNOTION_RETRIEVE_COMMENTAcción

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

Parámetros de entrada

  • comment_idstringObligatorio

    Identifier for the comment to retrieve.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Retrieve Database PropertyNOTION_RETRIEVE_DATABASE_PROPERTYAcción

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

Parámetros de entrada

  • database_idstringObligatorio

    Identifier for the database.

  • property_idstringObligatorio

    Identifier for the property. This can be the property ID or the property name.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Search Notion pageNOTION_SEARCH_NOTION_PAGEAcción

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.

Parámetros de entrada

  • querystring

    The text to search for in page and database titles. If an empty string is provided, all pages and databases accessible to the integration will be returned.

  • directionstring

    Specifies the sort direction for the results. Required if `timestamp` is provided. Valid values are `ascending` or `descending`.

  • page_sizeinteger

    The number of items to include in the response. Must be an integer between 1 and 100, inclusive. Defaults to 2.

  • timestampstring

    The timestamp field to sort the results by. Currently, the only supported value is `last_edited_time`. If provided, `direction` must also be specified.

  • filter_valuestring

    Filters the search results by object type. Valid values are `page` or `database`. Defaults to `page`.

  • start_cursorstring

    An opaque cursor value returned in a previous response. If provided, the API will return results starting after this cursor, enabling pagination. If `None` or an empty string, results start from the beginning.

  • filter_propertystring

    The property to filter the search results by. Currently, the only supported value is `object`, which filters by the type specified in `filter_value`. Defaults to `object`.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Update blockNOTION_UPDATE_BLOCKAcción

Updates an existing notion block's textual content or type-specific properties (e.g., 'checked' status, 'color'), using its `block id` and the specified `block type`.

Parámetros de entrada

  • contentstringObligatorio

    The new text content for the block. This is primarily used for text-based blocks like paragraphs, headings, and list items.

  • block_idstringObligatorio

    Identifier of the Notion block to be updated. To find a block's ID, other Notion actions that list or retrieve blocks can be used. For updating content within a page (which is also a block), its ID can be obtained using actions like `NOTION_FETCH_DATA` to get page IDs and titles.

  • block_typestringObligatorio

    The type of the block to update. Must be one of the supported types: 'paragraph', 'heading_1', 'heading_2', 'heading_3', 'bulleted_list_item', 'numbered_list_item', 'to_do', 'toggle'. The content structure and available `additional_properties` depend on this type.

  • additional_propertiesobject

    A dictionary of additional properties to apply to the block, specific to its type. These are merged into the block type's data object (e.g., into the 'paragraph' or 'to_do' object). Examples include `is_toggleable` (boolean) for heading blocks, `checked` (boolean) for 'to_do' blocks, or `color` (string, e.g., 'blue_background') for blocks supporting it. Consult Notion API documentation for supported properties within each block type object.

Parámetros de salida

  • dataobjectObligatorio

    A dictionary representing the updated Notion block object, conforming to the Notion API's block object structure.

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Update PageNOTION_UPDATE_PAGEAcción

Tool to update the properties, icon, cover, or archive status of a page. use when you need to modify existing page attributes.

Parámetros de entrada

  • iconobject

    A page icon object (either an emoji object or an external file object).

  • coverobject

    A file object for the page cover. Only external file objects are supported for covers.

  • page_idstringObligatorio

    Identifier for the Notion page to be updated.

  • archivedboolean

    Set to true to archive the page (i.e., send to trash). Set to false to restore a page from trash. Defaults to false.

  • propertiesobject

    An object containing the property values to update for the page. The keys are the names or IDs of the property and the values are property value objects. If a page property ID is not included, then it is not changed.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Update row databaseNOTION_UPDATE_ROW_DATABASEAcción

Updates or archives an existing notion database row (page) using its `row id`, allowing modification of its icon, cover, and/or properties; ensure the target page is accessible and property details (names/ids and values) align with the database schema and specified formats.

Parámetros de entrada

  • iconstring

    The emoji to be used as the icon for the page. Must be a single emoji character (e.g., '😻', '🤔').

  • coverstring

    URL of an external image to be used as the cover for the page (e.g., 'https://google.com/image.png').

  • row_idstringObligatorio

    Identifier (UUID) of the database row (page) to be updated. This ID must be a valid UUID string (e.g., '59833787-2cf9-4fdf-8782-e53db20768a5') corresponding to an existing Notion page. In Notion, database rows are treated as pages.

  • delete_rowboolean

    If true, the row (page) will be archived, effectively deleting it from the active view. If false, the row will be updated with other provided data.

  • propertiesobject[]

    A list of property values to update for the page. Each item in this list defines a specific property (by its name or ID) and the new value it should take. The format of the `value` depends on the property's type; refer to the main action documentation for detailed formatting guidelines. Properties not included in this list will retain their current values.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Update database schemaNOTION_UPDATE_SCHEMA_DATABASEAcción

Updates an existing notion database's title, description, and/or properties; at least one of these attributes must be provided to effect a change.

Parámetros de entrada

  • titlestring

    New title for the database. If this field is not provided or is set to `None` (the default value), the database's existing title will remain unchanged.

  • propertiesobject[]

    List of property updates. Each item must include at least the 'name' of the column to change plus one of: 'new_type', 'rename', or 'remove'. Example: [ {'name': 'Status', 'new_type': 'select'}, {'name': 'Priority', 'remove': true} ]

  • database_idstringObligatorio

    Identifier of the Notion database to update. Use the `NOTION_FETCH_DATA` action or similar tools to get available database IDs and their titles.

  • descriptionstring

    New description for the database. If this field is not provided or is set to `None` (the default value), the database's existing description will remain unchanged.

Parámetros de salida

  • dataobjectObligatorio

    Data from the action execution

  • errorstring

    Error if any occurred during the execution of the action

  • successfulbooleanObligatorio

    Whether or not the action execution was successful or not

Triggers (13)

Los triggers son eventos externos que pueden iniciar un flujo en tus agentes (ej: nuevo email, mensaje recibido, registro creado).

All Page EventsNOTION_ALL_PAGE_EVENTS_TRIGGERTrigger

Triggers when any Notion page is created or updated across the workspace.

Configuración

  • intervalnumber

    Periodic Interval to Check for Updates & Send a Trigger in Minutes

Payload del evento

  • event_typestringObligatorio

    Type of page event: page_added or page_updated

  • pageobjectObligatorio

    The Notion page object

Instrucciones

**Instructions for Setting Up the Trigger:** This trigger will monitor all pages in your Notion workspace for creations and updates. No additional configuration is required.

Comment CreatedNOTION_COMMENT_CREATEDTrigger

Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.

Configuración

  • page_idstring

    Optional page ID to scope comment events. When omitted, the trigger fires for any new comment in the workspace. Requires the 'Read comments' capability on the Notion integration.

Payload del evento

  • authorsobject[]

    Actors who performed the action.

  • comment_idstringObligatorio

    ID of the newly created comment.

  • dataobjectObligatorio

    Page reference for the comment.

  • event_idstringObligatorio

    Unique ID of the webhook event.

  • event_typestringObligatorio

    Notion webhook event type.

  • timestampstringObligatorio

    ISO 8601 event timestamp.

  • workspace_idstringObligatorio

    Workspace where the event occurred.

  • workspace_namestring

    Workspace name from the event.

Instrucciones

**Setting Up the Trigger** 1. Create a webhook subscription on your Notion public integration. 2. Use `https://backend.composio.dev/api/v3/trigger_instances/notion/pr_2t3DxsZg4uP0/handle` as the webhook URL. 3. Notion sends a one-time verification request containing a `verification_token`. Composio captures it automatically. 4. Retrieve the captured verification token from Composio and paste it into Notion's "Verify Subscription" UI to activate the subscription. 5. Subscribe the integration to the event categories the trigger needs (Page, Data source, View, Comment, etc.).

New CommentNOTION_COMMENTS_ADDED_TRIGGERTrigger

Triggers when a new comment is added to a specified Notion block or page.

Configuración

  • block_idstringObligatorio

    Identifier for a Notion block or page to monitor for new comments.

  • intervalnumber

    Periodic Interval to Check for Updates & Send a Trigger in Minutes

Payload del evento

  • commentobjectObligatorio

    The Notion comment object that was added

  • event_typestring

    Type of Notion comment event

Instrucciones

**Instructions for Setting Up the Trigger:** - Provide the block or page ID from your Notion workspace where comments are posted. - You can also use the `NOTION_SEARCH_NOTION_PAGE` action to discover block/page IDs.

Database CreatedNOTION_DATABASE_CREATEDTrigger

Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.

Configuración

Sin parámetros.

Payload del evento

  • authorsobject[]

    Actors who performed the action.

  • dataobjectObligatorio

    Where the new database was created.

  • database_idstringObligatorio

    ID of the newly created database.

  • event_idstringObligatorio

    Unique ID of the webhook event.

  • event_typestringObligatorio

    Notion webhook event type.

  • timestampstringObligatorio

    ISO 8601 event timestamp.

  • workspace_idstringObligatorio

    Workspace where the event occurred.

  • workspace_namestring

    Workspace name from the event.

Instrucciones

**Setting Up the Trigger** 1. Create a webhook subscription on your Notion public integration. 2. Use `https://backend.composio.dev/api/v3/trigger_instances/notion/pr_2t3DxsZg4uP0/handle` as the webhook URL. 3. Notion sends a one-time verification request containing a `verification_token`. Composio captures it automatically. 4. Retrieve the captured verification token from Composio and paste it into Notion's "Verify Subscription" UI to activate the subscription. 5. Subscribe the integration to the event categories the trigger needs (Page, Data source, View, Comment, etc.).

Data Source CreatedNOTION_DATASOURCE_CREATEDTrigger

Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.

Configuración

Sin parámetros.

Payload del evento

  • authorsobject[]

    Actors who performed the action.

  • dataobjectObligatorio

    Where the new data source was created.

  • data_source_idstringObligatorio

    ID of the newly created data source.

  • event_idstringObligatorio

    Unique ID of the webhook event.

  • event_typestringObligatorio

    Notion webhook event type.

  • timestampstringObligatorio

    ISO 8601 event timestamp.

  • workspace_idstringObligatorio

    Workspace where the event occurred.

  • workspace_namestring

    Workspace name from the event.

Instrucciones

**Setting Up the Trigger** 1. Create a webhook subscription on your Notion public integration. 2. Use `https://backend.composio.dev/api/v3/trigger_instances/notion/pr_2t3DxsZg4uP0/handle` as the webhook URL. 3. Notion sends a one-time verification request containing a `verification_token`. Composio captures it automatically. 4. Retrieve the captured verification token from Composio and paste it into Notion's "Verify Subscription" UI to activate the subscription. 5. Subscribe the integration to the event categories the trigger needs (Page, Data source, View, Comment, etc.).

Data Source Schema UpdatedNOTION_DATASOURCE_SCHEMA_UPDATEDTrigger

Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.

Configuración

  • data_source_idstring

    Optional data source ID to scope schema-change events. When omitted, the trigger fires for any data source schema change in the workspace the integration has access to.

Payload del evento

  • authorsobject[]

    Actors who performed the action.

  • dataobjectObligatorio

    Parent reference plus the schema-change details.

  • data_source_idstringObligatorio

    ID of the data source whose schema changed.

  • event_idstringObligatorio

    Unique ID of the webhook event.

  • event_typestringObligatorio

    Notion webhook event type.

  • timestampstringObligatorio

    ISO 8601 event timestamp.

  • workspace_idstringObligatorio

    Workspace where the event occurred.

  • workspace_namestring

    Workspace name from the event.

Instrucciones

**Setting Up the Trigger** 1. Create a webhook subscription on your Notion public integration. 2. Use `https://backend.composio.dev/api/v3/trigger_instances/notion/pr_2t3DxsZg4uP0/handle` as the webhook URL. 3. Notion sends a one-time verification request containing a `verification_token`. Composio captures it automatically. 4. Retrieve the captured verification token from Composio and paste it into Notion's "Verify Subscription" UI to activate the subscription. 5. Subscribe the integration to the event categories the trigger needs (Page, Data source, View, Comment, etc.).

New PageNOTION_PAGE_ADDED_TO_DATABASETrigger

Triggers when a new page is added to a Notion database.

Configuración

  • database_idstringObligatorio

    The ID of the database

  • intervalnumber

    Periodic Interval to Check for Updates & Send a Trigger in Minutes

Payload del evento

  • event_typestring

    Type of Notion page event

  • pageobjectObligatorio

    The Notion page that was added

Instrucciones

**Instructions for Setting Up the Trigger:** - You can get the database id by going to your Notion table/database and - copying it from there. - You can also use the NOTION_FETCH_DATA action to get the database ID and title of all databases accessible to the integration

Page Added to PageNOTION_PAGE_ADDED_TRIGGERTrigger

Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.

Configuración

  • intervalnumber

    Periodic Interval to Check for Updates & Send a Trigger in Minutes

  • parent_page_idstringObligatorio

    The ID of the parent Notion page to monitor for new subpages

Payload del evento

  • blockobjectObligatorio

    The Notion block that was added

  • event_typestring

    Type of Notion block event

Instrucciones

**Instructions for Setting Up the Trigger:** - Provide the parent page ID from your Notion workspace. - This trigger will monitor that parent page for newly created subpages (child_page blocks). - You can also use the NOTION_FETCH_DATA action to get the page ID and title of all pages accessible to the integration

Page Content UpdatedNOTION_PAGE_CONTENT_UPDATEDTrigger

Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).

Configuración

  • data_source_idstring

    Optional data source ID to scope to body-content edits on any row in this Notion data source. Mutually exclusive with page_id and parent_page_id.

  • page_idstring

    Optional page ID to scope to body-content edits on this specific Notion page. Mutually exclusive with data_source_id and parent_page_id.

  • parent_page_idstring

    Optional parent page ID to scope to body-content edits on any page whose immediate parent is this Notion page (does not match grandchildren). Mutually exclusive with data_source_id and page_id.

Payload del evento

  • authorsobject[]

    Actors who performed the action.

  • dataobjectObligatorio

    Parent reference plus the list of updated blocks.

  • event_idstringObligatorio

    Unique ID of the webhook event.

  • event_typestringObligatorio

    Notion webhook event type.

  • page_idstringObligatorio

    ID of the page whose content changed. For child-block additions (e.g. a new sub-page), this is the parent's ID.

  • timestampstringObligatorio

    ISO 8601 event timestamp.

  • workspace_idstringObligatorio

    Workspace where the event occurred.

  • workspace_namestring

    Workspace name from the event.

Instrucciones

**Setting Up the Trigger** 1. Create a webhook subscription on your Notion public integration. 2. Use `https://backend.composio.dev/api/v3/trigger_instances/notion/pr_2t3DxsZg4uP0/handle` as the webhook URL. 3. Notion sends a one-time verification request containing a `verification_token`. Composio captures it automatically. 4. Retrieve the captured verification token from Composio and paste it into Notion's "Verify Subscription" UI to activate the subscription. 5. Subscribe the integration to the event categories the trigger needs (Page, Data source, View, Comment, etc.).

Page CreatedNOTION_PAGE_CREATEDTrigger

Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.

Configuración

  • data_source_idstring

    Optional data source ID to scope to new rows in this Notion data source. Mutually exclusive with parent_page_id. Find the data source ID via Notion's API (GET /v1/databases/{id}.data_sources[].id) or the data source URL.

  • parent_page_idstring

    Optional parent page ID to scope to new sub-pages whose immediate parent is this Notion page (does not match grandchildren). Mutually exclusive with data_source_id.

Payload del evento

  • authorsobject[]

    Actors who performed the action.

  • dataobjectObligatorio

    Where the new page was created.

  • event_idstringObligatorio

    Unique ID of the webhook event.

  • event_typestringObligatorio

    Notion webhook event type.

  • page_idstringObligatorio

    ID of the newly created page.

  • timestampstringObligatorio

    ISO 8601 event timestamp.

  • workspace_idstringObligatorio

    Workspace where the event occurred.

  • workspace_namestring

    Workspace name from the event.

Instrucciones

**Setting Up the Trigger** 1. Create a webhook subscription on your Notion public integration. 2. Use `https://backend.composio.dev/api/v3/trigger_instances/notion/pr_2t3DxsZg4uP0/handle` as the webhook URL. 3. Notion sends a one-time verification request containing a `verification_token`. Composio captures it automatically. 4. Retrieve the captured verification token from Composio and paste it into Notion's "Verify Subscription" UI to activate the subscription. 5. Subscribe the integration to the event categories the trigger needs (Page, Data source, View, Comment, etc.).

Page Properties UpdatedNOTION_PAGE_PROPERTIES_UPDATEDTrigger

Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.

Configuración

  • data_source_idstring

    Optional data source ID to scope to property changes on any row in this Notion data source. Mutually exclusive with page_id and parent_page_id.

  • page_idstring

    Optional page ID to scope to property changes on this specific Notion page. Mutually exclusive with data_source_id and parent_page_id.

  • parent_page_idstring

    Optional parent page ID to scope to property changes on any page whose immediate parent is this Notion page (does not match grandchildren). Mutually exclusive with data_source_id and page_id.

Payload del evento

  • authorsobject[]

    Actors who performed the action.

  • dataobjectObligatorio

    Parent reference plus the list of property IDs that changed.

  • event_idstringObligatorio

    Unique ID of the webhook event.

  • event_typestringObligatorio

    Notion webhook event type.

  • page_idstringObligatorio

    ID of the page whose properties changed.

  • timestampstringObligatorio

    ISO 8601 event timestamp.

  • workspace_idstringObligatorio

    Workspace where the event occurred.

  • workspace_namestring

    Workspace name from the event.

Instrucciones

**Setting Up the Trigger** 1. Create a webhook subscription on your Notion public integration. 2. Use `https://backend.composio.dev/api/v3/trigger_instances/notion/pr_2t3DxsZg4uP0/handle` as the webhook URL. 3. Notion sends a one-time verification request containing a `verification_token`. Composio captures it automatically. 4. Retrieve the captured verification token from Composio and paste it into Notion's "Verify Subscription" UI to activate the subscription. 5. Subscribe the integration to the event categories the trigger needs (Page, Data source, View, Comment, etc.).

Page UpdatedNOTION_PAGE_UPDATED_TRIGGERTrigger

Triggers when any block within a specified Notion page is updated.

Configuración

  • intervalnumber

    Periodic Interval to Check for Updates & Send a Trigger in Minutes

  • page_idstringObligatorio

    The ID of the Notion page to monitor

Payload del evento

  • blockobjectObligatorio

    The Notion block that was updated

  • event_typestring

    Type of Notion block event

View CreatedNOTION_VIEW_CREATEDTrigger

Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.

Configuración

Sin parámetros.

Payload del evento

  • authorsobject[]

    Actors who performed the action.

  • dataobjectObligatorio

    Parent reference plus the view's layout type.

  • event_idstringObligatorio

    Unique ID of the webhook event.

  • event_typestringObligatorio

    Notion webhook event type.

  • timestampstringObligatorio

    ISO 8601 event timestamp.

  • view_idstringObligatorio

    ID of the newly created view.

  • workspace_idstringObligatorio

    Workspace where the event occurred.

  • workspace_namestring

    Workspace name from the event.

Instrucciones

**Setting Up the Trigger** 1. Create a webhook subscription on your Notion public integration. 2. Use `https://backend.composio.dev/api/v3/trigger_instances/notion/pr_2t3DxsZg4uP0/handle` as the webhook URL. 3. Notion sends a one-time verification request containing a `verification_token`. Composio captures it automatically. 4. Retrieve the captured verification token from Composio and paste it into Notion's "Verify Subscription" UI to activate the subscription. 5. Subscribe the integration to the event categories the trigger needs (Page, Data source, View, Comment, etc.).