Share
Notion (Edge) Setup Guide

Notion is a connected workspace in which teams write documents, build wikis, and manage projects and tasks. Teams organize their content as pages and databases, and collaborate through comments.

Hevo uses the Notion API to replicate data from your Notion workspace to the Destination of your choice. To ingest data, you must provide Hevo with the API key of a Notion internal connection that has access to the pages and databases you want to replicate.


Supported Features

Feature Name Supported
Capture deletes Yes (for some objects)
History mode No
Custom data (user-configured tables & fields) No
Data blocking (skip objects and fields) Yes
Resync (objects and Pipelines) Yes
API configurable Yes

Handling of Deletes

For the Page Index, Block, Block Level 2 to Block Level 5, Block Comment, Block Level 2 Comment to Block Level 5 Comment, Page Comment, and Users objects, Hevo uses a full data refresh approach to capture deletes. During each Pipeline run, Hevo compares the data fetched from the Source object with the data present in the Destination table. If a record exists in the Destination but is no longer returned by the Source, the record is marked as deleted by setting the value of the metadata column __hevo__marked_deleted to True.

For the Data Source Title, Data Source Description, and Database Title objects, Hevo replaces the records of a data source or database each time it ingests the data source. As a result, the title and description in the Destination always match those in Notion.

For all the other objects, Hevo does not capture deletes. Records deleted in Notion remain in the Destination.


Source Considerations

  • Hevo replicates only the pages and databases that your internal connection can access. If you give the connection access to a page after creating the Pipeline, Hevo ingests its data in the next Pipeline run.

  • The Block Comment and Page Comment objects require the Read comments capability, and the Users object requires a user information capability. If your internal connection does not have the required capability, Notion does not return the data for these objects. To avoid ingestion errors, add the capability to the connection or deselect the objects in the Pipeline.

  • The email addresses of people are replicated in the Users object only if your internal connection has the Read user information including email addresses capability.

  • The Users object does not contain the guests of your workspace, as Notion does not return guests in the list of users.

  • For each block, Hevo requests the nested blocks and the comments from Notion. In workspaces with many blocks, this increases the ingestion time and the number of requests that count toward the Notion rate limit.

  • Notion returns only the unresolved comments on a page or block. Hence, when a comment is resolved in Notion, Hevo marks it as deleted in the Destination.

  • Adding or editing a row in a database does not update the last edited time of its data source. As Hevo ingests the child objects of a data source only when the data source is new or updated, the Data Source Query Results object does not include rows that are added or edited later. The rows of databases are also pages, so Hevo ingests their latest data in the Page and Page Property objects. To get the current rows of a database, use the Page records whose parent_type is data_source_id and whose parent_database_id is the ID of the database. To refresh the Data Source Query Results object, resync the Data Source object.


Limitations

  • Hevo ingests blocks up to the fifth level of nesting. Blocks nested more deeply, and the comments on them, are not ingested.

  • The plain_text field of the comment objects contains the text of the first 24 rich text elements of each comment. The complete text is in the rich_text field.

Last updated on Oct 29, 2026

Tell us what went wrong

Skip to the section