What problem does it solve? Building a reliable data sync into Notion requires choosing the right architecture, pagination strategy, and deletion handling for each external API, and mistakes like missing consistency buffers or non-advancing cursors cause permanent data loss or infinite loops. ## Core Features & Use Cases - Architecture Decision Framework: Choose between a simple replace-mode sync and a backfill+delta pair based on API change-tracking capability and dataset size. - Pagination & Cursor Patterns: Covers opaque cursors, page numbers, keyset (timestamp + id) pagination, event feeds, and consistency buffers drawn from Salesforce, Stripe, HubSpot, GitHub, and ServiceNow. - Deletion Strategies: Explains replace-mode mark-and-sweep, delete markers, and the flip-flop pattern for audit-log-based deletion detection. - Use Case: Sync HubSpot contacts into a Notion database by pairing a manual replace-mode backfill sync with a 5-minute incremental delta sync that handles search-API deadlocks. ## Quick Start Ask the agent to scaffold a Notion Workers sync for your external API, specifying the data source, whether it supports change tracking, and the desired schedule.