Appointments & Scheduling · How-to guide

Appointments calendar integrations overview

Understand how native Britixo appointments connect to Google Calendar, Google Meet, Outlook and downloadable ICS files without becoming the same record.

Audience: Staff who manage appointmentsFeature: Calendar integrationsModule v1.3.6
Feature pathAppointments > Settings > Calendar integrations
Before you beginThis guide follows the supplied Britixo Appointments & Scheduling module version 1.3.6. The relevant access is Appointments: View. A menu, button, provider, time slot or client action can remain hidden when the signed-in user lacks the required permission, the module setting is disabled, the related record is in an ineligible state, or availability validation rejects the request.

What this feature does

Understand how native Britixo appointments connect to Google Calendar, Google Meet, Outlook and downloadable ICS files without becoming the same record. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.

How the module flow works

The appointment remains the authoritative Britixo record; remote calendar events store their own identifiers and API state.

Google OAuth is connected per staff user, Outlook uses configured application credentials, and ICS is generated from appointment data without a persistent remote connection.

Create, update and delete actions are conditional on permission, connection state, appointment data and settings.

Step-by-step workflow

  1. Choose the calendar integration required by the organisation.
  2. Configure credentials and connect the relevant staff account.
  3. Create a test appointment and add or synchronise its calendar event.
  4. Update the appointment and verify the remote event.
  5. Cancel or delete the test and confirm the chosen remote handling.

Important fields and decisions

Britixo appointmentPrimary operational record.
Remote event IDReference used to update or remove an external event.
OAuth/application credentialsAuthorise access to the chosen provider.
ICS filePortable calendar download generated from the appointment.

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 treat remote calendar success as the appointment database save result.
  • Use least-privilege credentials and revoke departed staff connections.
  • Check timezone in both systems.
  • 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.
Scheduling and data safetyAppointment changes can notify customers, reserve provider time, update remote calendars, create meeting links or invoices and alter reports. Confirm the exact record, timezone, status and recipients before saving.