Once connected, the Notion integration enables syncing of content, task boards, and structured records into Fostr for smarter decision routing and workflow support. This page answers common questions about the type of data Fostr pulls from Notion, how it’s structured, and what’s supported or excluded.

Data Refresh, Frequency and Sync Timing

Notion data is refreshed at a standardized interval of every 30 minutes. This is performed through background polling syncs that automatically capture updates without requiring user intervention. If Notion introduces webhook functionality in the future (currently on their roadmap), real-time syncing may become available, reducing reliance on interval-based polling.

Sync timing is not configurable at the tenant level; it is standardized across all integrations. However, users may occasionally see updates appear more quickly if specific contextual actions are taken, such as document lookups, content routings, or decision-driven flows that query Notion on demand.

Because of Notion’s API throttling, there are cases where delays should be expected. The current rate limit is 3 requests per second per workspace, so updates may not appear until the next sync cycle (a maximum of 30 minutes). Newly added pages or edits are therefore only visible inside Fostr after the next scheduled pull.

Key points:

• Data refreshes automatically every 30 minutes.
• Additional lookups can be triggered contextually by user actions.
• Real-time support may be possible in the future when Notion enables webhooks.
• Delays are possible due to API rate limits and polling intervals.

Data Coverage and Historical Access

When the integration is first connected, Fostr performs a complete scan of accessible Notion content. Linked databases and pages available through the authorized Notion token are reviewed, and all existing rows, pages, and blocks are brought into scope. This ensures that Fostr starts with a full historical picture rather than only pulling forward-looking updates.

Backfill is supported by default. Any existing content that the integration can reach will be processed unless it is explicitly filtered out by permissions, sync logic, or structural mismatches between Notion’s content formats and Fostr’s mapping model.

Some content types are not currently supported. This includes certain embedded or private materials, unless they have been explicitly linked or shared to the scope of the integration.

Currently excluded from sync:

• Embedded media blocks such as equations, code snippets, and videos
• Private user notes unless deliberately shared
• Subpages not linked inside sync-enabled databases

Data Scope and Granularity

The integration captures both high-level page structures and detailed database records from Notion. Supported data types include:

• Page titles and standard block contents
• Database properties and record metadata such as status, tags, and owners
• Linked fields and selected relational properties

The level of detail preserved in sync ensures that both structured metadata and unstructured page content remain actionable inside Fostr. Examples of granularity include:

• Text content blocks, including lists, headings, and tables
• Column-level data within Notion database views
• Page URLs, metadata fields such as last edited by, and timestamps