Notion connector FAQ
This feature is in Beta. Workspace admins can control access to this feature from the Previews page by opting into the Notion connector preview. See Manage Databricks previews.
This page answers frequently asked questions about the managed Notion ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which tables does the connector support?
The connector supports seven source tables: pages, data_sources, databases, blocks, page_comments, block_comments, and users. For the full schemas, see Destination table schemas.
Which authentication methods does the connector support?
The connector supports OAuth user-to-machine (U2M) authentication only. You authorize the connection through a Notion public integration that you own. OAuth M2M and basic authentication with a username and password are not supported.
How does the connector decide which content to ingest?
Notion uses a page-picker permission model instead of OAuth scopes. When you create the connection, you select the pages and data sources to share with the integration, and the connector ingests only that content. To ingest more content later, edit the shared selection in Notion. See Create a Notion connection.
Which tables sync incrementally?
The pages and data_sources tables sync incrementally on last_edited_time. The databases, blocks, page_comments, block_comments, and users tables are full refresh only, because their Notion endpoints expose no change-time ordering. See Supported source tables.
Does the connector sync page permissions?
No. Notion page permissions (ACLs) are not synced. Who can view a page within Notion is not reflected in the ingested data. See Notion connector limitations.
How deeply nested can ingested blocks be?
The connector walks the block tree recursively up to 30 levels deep by default. Blocks nested deeper than this limit are not ingested. See Notion connector limitations.
Which clouds does the connector support?
The connector is available on Databricks on AWS, Azure, and GCP.