← ClaudeAtlas

sync-implement-pollinglisted

Implement Merge sync detection via a scheduled polling job. Use this as a development starting point (no public webhook endpoint required) and as a production fallback alongside `sync-implement-webhooks` to catch missed or delayed webhook deliveries. A single job covers both initial sync detection (first connection) and subsequent incremental syncs (`modified_after` bounded fetches). Use when a developer says "set up polling sync", "scheduled sync", "fallback sync", "sync without webhooks", "cron job for Merge", or wants a simple way to fetch data while developing locally.
merge-api/merge-unified-skills · ★ 0 · Code & Development · score 71
Install: claude install-skill merge-api/merge-unified-skills
# Implementing Merge Sync via Polling (Fallback / Development Starting Point) A single scheduled background job polls every active linked account, detecting both initial sync completion and ongoing incremental updates. Simpler than webhooks — no public endpoint, no HMAC verification — and useful in two production-relevant scenarios: 1. **Development starting point.** You're prototyping locally and don't yet have a publicly reachable webhook URL. Polling gets you to working sync in minutes. 2. **Production fallback safety net.** Run alongside `sync-implement-webhooks` so missed or delayed webhook deliveries don't leave data stale. > **Webhooks are the primary production approach.** This skill is intentionally framed as a fallback or development tool. For production reliability, also implement `sync-implement-webhooks` and let the two run in parallel — data fetches are idempotent because the bounded `modified_after` / `modified_before` window covers the same records safely. > **Field-name convention used in this doc.** Pseudo-code and JSON snippets show the raw HTTP response shape (snake_case: `is_initial_sync`, `last_sync_result`, `modified_at`). The Merge SDKs auto-convert to camelCase — in Node, `model.is_initial_sync` becomes `model.isInitialSync`, and request params like `modified_after` become `modifiedAfter`. Write your code in your SDK's convention. ## First activation: self-introduce > I'm the sync-implement-polling skill. I'll wire up a single scheduled job that