What problem does it solve? Building reliable data syncs into Notion databases requires handling pagination, rate limits, eventual consistency, and deletion detection correctly — 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 simple replace-mode syncs and backfill+delta sync pairs based on API change-tracking capability and dataset size. - Pagination & Cursor Patterns: Reference implementations for opaque cursors, page numbers, keyset (timestamp + id) pagination, and event-feed cursors drawn from Salesforce, Stripe, HubSpot, GitHub, and ServiceNow. - Production Edge Cases: Covers consistency buffers, HubSpot deadlock detection, ServiceNow flip-flop delete streams, and event anchors for backfill-to-delta transitions. - Use Case: Sync Stripe customers into a Notion database by pairing a manual replace-mode backfill with a 5-minute incremental delta sync reading the events feed with a 10-second consistency buffer. ## 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.