Update or delete a Google Calendar event
Keep the remote event aligned after an appointment changes or remove it when calendar presence is no longer required. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
What you’ll accomplish
Keep the remote event aligned after an appointment changes or remove it when calendar presence is no longer required. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The module uses the stored Google event identifier to update timing/content or delete the remote event.
An appointment update does not guarantee remote success if the staff token is invalid or the event was removed directly in Google.
The module option can control whether remote events are deleted when appointments are removed or cancelled.
Follow these steps
- Go to the appointment and confirm it has a Google event reference.
- After a date/content change, choose the update action or verify automatic update.
- After cancellation/deletion, choose the configured remote delete action.
- Check the Google calendar.
- Check Britixo history and remote-reference state.
Fields and decisions to review
How to confirm it worked
After this workflow completes, Britixo keeps the appointment and its supported relationships connected. Reopen the appointment and verify the saved status, date, timezone, customer or lead, service, provider, attendees, reminder state, calendar or meeting reference, invoice reference and history that apply to this feature. External email, SMS, Google, Microsoft or payment outcomes must be checked separately from the Britixo database save.
- Open the saved appointment and confirm the final status and source.
- Check the participant, provider, timing and timezone from the full detail page.
- Review the relevant table filter, calendar, history, report or linked invoice instead of relying only on a success message.
Controls, checks and common mistakes
- Do not create a replacement event before checking the existing remote ID.
- Deleting a Google event does not by itself cancel the Britixo appointment.
- Handle revoked tokens before retrying.
- Use the least destructive correction and retain the appointment history when the booking existed operationally.
- Never bypass a permission, availability, approval, client-access or verification control by changing an unrelated route or setting.
