Google Calendar Incremental Sync (OAuth) to n8n Data Tables

Keep your n8n data tables always in sync with Google Calendar—incrementally, reliably, and with OAuth

This n8n workflow incrementally syncs Google Calendar events into n8n Data Tables using Google Calendar OAuth. Run it manually or every 15 minutes to fetch only changes via sync tokens, normalize events, and upsert durable records with safe pagination, retries, and error handling.

What this workflow does

• Loads sync state from an n8n Data Table (including the saved nextSyncToken and cursor metadata).
• Chooses incremental vs full sync based on the stored token and a forceFullSync setting, then records run start metadata.
• Fetches event changes from Google Calendar using the Events API with OAuth, with showDeleted enabled.
• Handles pagination by iterating with pageToken and includes safety checks to prevent repeated tokens or excessive pages.
• Retries transient API failures using backoff to improve resiliency.
• Recovers from invalid tokens: if the API returns HTTP 410, the workflow clears the invalid sync token once and restarts as a full sync.
• Normalizes and upserts each returned event (including cancelled “tombstones”) into an n8n Data Table.
• Commits the new cursor only after success: updates the stored nextSyncToken only after all event writes succeed; on failure, it saves an error summary without advancing the cursor.

Use cases

• Maintain an always-current event mirror of Google Calendar in n8n for reporting, dashboards, or downstream automations.
• Ensure cancelled and updated events are reflected (tombstones included) for accurate calendar-derived data.
• Build SaaS or internal workflows that rely on consistent calendar state without re-importing everything.

Technical details

• Triggers: manual run or scheduled every 15 minutes
• Integrations: Google Calendar API via Google Calendar OAuth2 credential in n8n
• Workflow nodes / building blocks: if, code, wait, switch, Data Table, and a Sticky Note