Setting up the Notion integration in Fostr involves workspace authorization, field mapping, and a few simple configuration steps to ensure accuracy and continuity. This section provides answers to frequently asked questions around troubleshooting.

Sync Failures (Pages or Properties Not Appearing)

Notion data may fail to sync into Fostr if permissions are incomplete or if the schema setup does not match the requirements of the integration. These issues often occur during the initial configuration or after changes in Notion.

Common reasons pages do not sync:

• The Fostr OAuth integration has not been fully granted permission inside Notion
• Databases or pages were not shared with the app on the Notion side
• The API authentication token has expired or is missing required scopes
• The page structure includes unsupported block types

Sometimes records appear in Fostr, but certain properties are missing or incomplete. This typically reflects schema mismatches or unsupported fields within Notion.

Common causes for missing fields:

• The Notion API requires a flat schema and may drop nested or multi-select properties if not mapped correctly
• Property types like checkboxes or people-tags often require mapping logic during setup

To resolve page or property sync issues, review permission settings in Notion, verify OAuth scopes, confirm database sharing, and adjust field mappings after any schema changes.

Sync Timing and Platform Limitations

The Notion integration refreshes automatically every 30 minutes using a polling model. Updates such as new pages, property changes, or edits will not appear inside Fostr until the next scheduled sync cycle. Sync intervals cannot currently be customized at the tenant level.

Limitations to be aware of:

• No webhook support: Notion does not yet provide real-time sync APIs. Polling is required until webhooks are made available
• Polling delays: Updates may take up to 30 minutes to appear inside Fostr
• Rate limits: The Notion API enforces three requests per second per workspace, which can cause delays in larger environments
• Unsupported block types: Elements such as toggle headers, synced blocks, embedded media, or unshared private notes may not sync unless explicitly linked

Until webhooks are introduced, Fostr recommends planning workflows with the 30-minute sync cycle in mind and optimizing Notion databases to minimize delays from rate limits.