Show Google Calendar events in the appointment table
Include imported Google Calendar events beside Britixo appointments for a wider workload view without converting those events into native appointment records.
What this feature does
Include imported Google Calendar events beside Britixo appointments for a wider workload view without converting those events into native appointment records. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
When a staff member has connected Google Calendar and event display is enabled, the table can retrieve remote calendar events for the configured date range.
Imported Google events remain remote calendar records; they are displayed for context and do not gain Britixo appointment statuses, invoices or feedback.
The integration stores OAuth credentials per staff member and applies the configured retrieval window.
Step-by-step workflow
- Connect the relevant staff Google Calendar.
- Enable Google event display in the Appointments settings.
- Set a practical past and future date range.
- Reload the appointment table and identify remote Google events.
- Open Britixo appointments separately when status or invoice actions are required.
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
- Keep the retrieval range narrow enough for responsive loading.
- Do not expect status actions on a remote-only Google event.
- Reconnect the account if the OAuth token is revoked or expired.
- 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.