Fixing recurring events that do not appear in Google Calendar after being created in Zoho CRM requires checking sync settings, reauthenticating accounts, and confirming which calendar is the event target. This overview explains what the sync does, when to apply common fixes, where to find the controls in the UI, and which sibling features to check next.
What is it
The "Zoho CRM ↔ Google Calendar" sync pushes meetings and calls created in Zoho CRM into the linked Google Calendar and pulls Google events back into Zoho where applicable. It supports two-way updates for standard events, but recurring events can fail to appear in Google when the target calendar is wrong, authorization expires, or the sync experiences delays. Zoho Calendar and Zoho CRM share separate sync controls: CRM events appear in Zoho Calendar when the CRM calendar sync is active, and Google sync must be enabled and authorized from Zoho Calendar to mirror those events to Google. Changes can take time to propagate and sometimes require reauthorization. [3][7][2]
When to use it
- Recurring meetings created in Zoho CRM never show on the expected Google calendar — check the event’s target calendar and sync status. [3]
- Events appear in Google but show the wrong time or only after a long delay — investigate recent service issues and known delays reported by the support team. [2]
- Recurring series syncs once but later occurrences stop updating — reauthorize the Google connection and verify there has been no permission revocation. [4]
- Users report some CRM events showing in Zoho Calendar but not in Google — confirm that the CRM calendar is set to sync with Zoho Calendar and then that Google sync is enabled. [7]
- An account change (password, Google account downgrade, or multiple linked Google identities) happened recently — verify account links and reauthenticate the affected Zoho–Google connection. [1][6]
How to access it
Open Zoho Calendar to control Google sync: go to Settings > Calendar > Synchronize, then click Google Calendar to enable, reauthorize, or stop synchronization. If you manage the CRM-to-Zoho calendar link, go to Settings > Calendar > Zoho Apps inside Zoho Calendar and select Zoho CRM calendar to turn CRM sync on or off. If sync stops or behaves inconsistently, use the Unsynchronize/Turn off sync and then re-add the connection or choose Reauthorize to refresh tokens. These same pages show which calendar is the target when you create an event in Zoho; ensure you select the correct Google calendar in the Create Event window. [3][7][4]
Related features
- Reauthorize calendar connections — forces refresh of OAuth tokens when sync stalls or access is revoked. [4]
- Unsynchronize (disconnect) and re-add Google Calendar — clears stale connections and re-imports events cleanly. [3]
- Associate an event with Zoho CRM from Zoho Calendar — use when you want a Google-created event to appear in CRM Activities and be linked to a contact or lead. [7]
- Account linking and single-sign-on settings — check when users report double-linked Google identities, auth token errors, or federated sign-in problems. [1][6]
Notes on common causes and quick checks
- Verify the event was created on the calendar that syncs to Google. If you choose "My Calendar" in Zoho but that calendar is not the Google-linked calendar, Google will not receive the event. [3]
- Reauthorize when there has been no sync activity for a long time, the Google account password changed, or Google revoked access. Reauthorization often restores recurring-series behavior. [4]
- Expect some delays. Support has acknowledged occasional lag and time-drift issues between Zoho CRM and Google; if a sync looks delayed, check status and reauthorize before filing a ticket. [2]
- If users have multiple Google identities linked or recent changes in Google Apps plans, confirm the correct Google account is connected to Zoho and reauthenticate the intended account. [1][6]
If these checks do not restore recurring series sync, collect one example event (date/time, series ID, target calendar) and reauthorize the Google connection; escalate to support if the reauthorize/unsync cycle does not resolve the missing occurrences.