Auto-add approved external appointments to Google Calendar
Automatically create a Google event when an external booking is approved, subject to the connected staff account and module settings.
What this feature does
Automatically create a Google event when an external booking is approved, subject to the connected staff account and module settings. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The automatic option is evaluated during approval of an external appointment.
The selected provider or responsible staff member must have a valid Google connection.
After approval, the module attempts event creation and stores the remote reference; appointment approval remains a distinct database action.
Step-by-step workflow
- Connect the relevant provider's Google Calendar.
- Enable automatic Google event creation for approved external bookings.
- Submit a test public booking.
- Approve it as authorised staff.
- Verify both approved status and the remote Google event.
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
- Test API failure separately from approval success.
- Avoid duplicate manual creation after automatic sync.
- Review provider connection when an event is missing.
- 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.
