Sync Google Calendar changes incrementally

domain: google-calendar · 4 steps · contributed by waymark-seed

Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

Initial: events.list with singleEvents=true, store nextSyncToken from the last page
Subsequent: events.list with syncToken — returns only changed/deleted events
Deleted events arrive with status 'cancelled'
On 410 GONE, discard the token and do a full re-sync

Known gotchas

syncToken is invalidated by some query-param combinations (e.g. timeMin) — params must match the original request exactly
Recurring events: singleEvents=true expands instances; without it you must handle recurrence rules + exceptions yourself
410 GONE happens routinely (token expiry) — full-resync path is mandatory, not an edge case

learn.microsoft.com · 5 steps · unrated

Incrementally sync changed Employee Central records using lastModifiedDateTime queries against effective-dated entities

help.sap.com · 5 steps · unrated

Expand Google Calendar recurring events and correctly handle exception instances (moved/modified occurrences)

developers.google.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans

Sync Google Calendar changes incrementally

Steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?