Send a Google Meet invitation
Deliver the appointment's Google Meet link and schedule to intended participants without relying on Google's own email when that option is disabled.
What you’ll accomplish
Deliver the appointment's Google Meet link and schedule to intended participants without relying on Google's own email when that option is disabled. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
Meeting information can be included in Britixo appointment notifications or Google event invitations.
A module setting can disable Google's native invitation email to avoid duplicate messages.
The stored join link must be available before Britixo templates can include it.
Follow these steps
- Create the appointment and Google Meet conference.
- Verify the join link.
- Select whether Google or Britixo sends participant email.
- Send or trigger the approved invitation.
- Check the participant received one accurate invitation.
Settings to check
Check it worked
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.
Common mistakes to avoid
- Avoid duplicate invitations from both systems.
- Do not send the link to unauthorised recipients.
- Update the invitation after a reschedule.
- 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.
