Synchronise an appointment to Google Calendar
Create a Google Calendar event from a Britixo appointment and retain the remote reference for later updates.
What this feature does
Create a Google Calendar event from a Britixo appointment and retain the remote reference for later updates. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The action reads appointment subject, description, location, start/end and timezone.
Google returns a remote event identifier that the module stores against the appointment or related calendar record.
Later update or delete actions use that identifier rather than creating another event.
Step-by-step workflow
- Connect the responsible staff Google Calendar.
- Open the appointment.
- Select Add to Google Calendar.
- Confirm the event appears with correct time and content.
- Verify Britixo shows the remote calendar state.
Important fields and decisions
What happens after completion
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 click create repeatedly when the remote response is slow.
- Check event timezone and invited attendees.
- Update the existing event after appointment changes.
- 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.
