How do integrations work?
What connects, where tokens live, and how to disconnect.
01Where they live
Integrations in your organisation settings lists every provider alongside the state of your connection to it. There is nothing to install or enable first. The catalogue is simply there, and what you may do with it follows your permissions.
- Xero
- Pushes invoices and syncs contacts.
- Google Calendar
- Keeps a two way sync with your bookings.
- Webhook
- Sends signed events to an endpoint you control, for anything with no dedicated provider.
02Connect
Xero and Google Calendar are OAuth connectors, so connecting hands you to the provider’s own sign-in page to approve the access. We never see your provider password, and the Scopes row shows exactly what was asked for.
03Where access lives
The access tokens a provider issues are encrypted and held only on our servers. They never reach your browser and staff cannot read them, which is also why reconnecting is the fix for a broken connection rather than re-entering a key.
04Sync and health
Run a sync check at any time to confirm a connection is still healthy; recent results list under each connection, so a provider that quietly revoked access shows up as a failed check rather than as silence.
05Webhooks
Register an https endpoint you control and the events you want, and signed payloads are sent to it.
06Who can do what
Integrations is one permission: checking connection health, running a sync check, connecting and disconnecting, editing how local fields map onto the provider’s, and managing webhook endpoints all come with it. Without it the tab is absent.
07Disconnect
Disconnecting revokes access at the provider and deletes the stored tokens immediately. Nothing is kept just in case. Reconnect whenever you want and a fresh approval is asked for.