Add, update or delete an Outlook calendar event
Maintain a Microsoft Outlook event connected to the Britixo appointment through the module's calendar actions.
What this feature does
Maintain a Microsoft Outlook event connected to the Britixo appointment through the module's calendar actions. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The module sends appointment content and timing through the authorised Microsoft calendar connection.
The returned event reference is used for later update and delete actions.
Remote API failure is distinct from the Britixo appointment save or lifecycle action.
Step-by-step workflow
- Connect Outlook Calendar.
- Open the appointment and add its Outlook event.
- Verify title, timing, timezone and location.
- Update after an appointment change.
- Delete the remote event when authorised and appropriate.
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
- Avoid duplicate creation when an event ID already exists.
- Deleting the remote event does not delete the Britixo appointment.
- Reconnect if authorisation expires.
- 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.
