Connect Google Calendar
Authorise an individual staff Google account so Britixo can create, update, delete or display calendar events for that user.
What this feature does
Authorise an individual staff Google account so Britixo can create, update, delete or display calendar events for that user. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The Google connection uses OAuth and stores the resulting staff-specific authorisation data.
The account must complete the Google consent flow and return to the module callback.
Calendar actions later use that connection and can fail independently if the token is revoked.
Step-by-step workflow
- Configure the required Google API credentials and redirect URI.
- Sign in as the staff user who owns the calendar.
- Select Connect Google Calendar.
- Complete Google consent.
- Create a test event and verify connection status.
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
- Never share one staff OAuth connection as a generic password.
- Use the exact live callback URI.
- Reconnect after token revocation or security-policy change.
- 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.
