Import Notion pages and embedded call transcripts into the warehouse.
Page text, properties, links, and available call transcripts are imported together. You don’t need an API key. Imported content uses the destination warehouse's access controls; Notion's individual page permissions are not copied.
Each row contains the page ID, title, original URL, creation and edit times, properties, parent, and Markdown content. Meeting transcripts embedded in pages are included when Notion makes them available to the connection. Plain-text transcripts pasted into pages are imported too. This source does not record calls or transcribe audio.
Embrasure uses Notion's Markdown API with transcript retrieval enabled. It rereads pages so transcripts that finish processing later can be picked up. Keep the generated id key and sync_cursor selections.
Create an Embrasure public connection in Notion’s developer portal, enable Read content only, and register https://api.embrasure.ai/v1/source-oauth/notion/callback as the redirect URI. The page picker is provided by Notion.
Set server-side NOTION_SOURCE_OAUTH_CLIENT_ID and NOTION_SOURCE_OAUTH_CLIENT_SECRET. In AWS, populate the matching Secrets Manager entries before enabling enable_notion_source_oauth_secrets for API and worker tasks. Set the deployment repository variable ENABLE_NOTION_SOURCE_OAUTH_SECRETS=true to preserve this setting on subsequent releases. The source remains unavailable while these credentials are missing. Never ask customers to create their own OAuth app or paste a token.
OAuth state is single-use and browser-bound. Tokens are encrypted, reconnects stay bound to the original Notion workspace, and rotating refresh credentials are stored atomically when Notion supplies expiring grants.