The same connection issue covered by our broader calendar and scheduling integration fix, focused specifically on syncing with Google or Outlook — we fix the connection on your site’s side, though we don’t control either calendar service itself.
Confirm which direction of sync is actually broken
Test whether a booking made on your site appears in Google or Outlook, and separately whether a change made directly in the calendar reflects back on your site. Confirming which direction fails narrows this down quickly.
Calendar sync (Google/Outlook) repair
Google or Outlook calendar sync repaired — the same fix as our general calendar integration, focused on this one path.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| Syncing specifically with Google or Outlook has stopped working correctly | This fix covers it |
| You want the broader calendar and scheduling integration diagnosed, not specifically Google/Outlook | Calendar / scheduling integration errors, in the Forms & Integrations category, the general version of this same fix |
| The calendar service itself is reporting an outage | Outside what we can fix — that’s the service’s own issue, on their timeline |
| Availability is wrong generally, not specifically a Google/Outlook sync issue | Booking calendar availability errors |
What you are seeing
- Bookings not appearing in the connected Google or Outlook calendar
- Availability not reflecting changes made directly in the calendar
- An authentication or connection error referenced during sync
- The issue possibly affecting only one sync direction
Common causes
- An expired authentication token between your site and Google or Outlook
- A timezone mismatch between your site and the calendar service
- The calendar service’s own API requirements changing
- Two connections both writing to the same calendar, creating conflicts
- A permission revoked on the Google or Microsoft account side, without an obvious notification reaching you
What we do
- Test both sync directions to isolate the failure
- Check authentication and reconnect where needed
- Verify timezone alignment between systems
- Test with a real booking and calendar change to confirm both directions work
- Flag plainly if the cause is on Google’s or Microsoft’s own side
What is included
- The sync issue identified and corrected, where within our control
- Verified two-way sync with real test cases
- A clear flag if the cause is on the calendar provider’s side
Not included
- Resolving an outage on Google’s or Microsoft’s own platform
- Setting this integration up for the first time, if not already in place
- Broader webhook connections unrelated to calendar sync specifically
- Ongoing monitoring for future provider-side changes
Questions about this fix
Is this different from the general calendar integration fix in a different category?
Not meaningfully in method — this is the same underlying diagnostic approach, framed here specifically for Google/Outlook sync in a booking context, rather than calendar integrations more broadly.
Do you need access to my Google or Outlook account?
Where the service supports it, a delegated or limited-access connection is preferable to your full account password.
Is there anything that would make this sync break again later?
Yes, since it depends on two independently maintained services staying compatible — a future change on Google's or Microsoft's side could require reconnecting again, through no fault of the original fix.
What if I use a different calendar service, not Google or Outlook?
This fix is scoped to those two specifically — a different calendar service's sync would need its own assessment, since the connection method and likely failure points differ.
Will this also fix availability that's wrong for reasons other than sync?
No — if availability itself is inaccurate for reasons unrelated to the Google or Outlook connection, that's the broader booking calendar availability fix rather than this one.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.