Integrations
Connect the CRM to the other software you use — accounting, payments, help desk, email, SMS, and phone systems — so records flow both ways without copy-paste. Each connection is set up once, monitored continuously, and can be paused or removed at any time.
The connector catalog
Open Integrations to see the catalog of available providers. Each card shows the provider, what it syncs, and whether your space already has a connection.
Connecting a provider
- Click Connect on the provider's card.
- Give the connection a name (useful when you connect more than one account of the same provider).
- Sign in:
- OAuth providers — you are sent to the provider's own login page to approve access, then returned here. Your password for that system is never seen or stored by the CRM. - API-key providers — paste the key from the provider's dashboard. It is stored encrypted.
- The system installs the connection and immediately runs a health check. If anything is
wrong, the connection shows a clear error message instead of pretending to work.
changes made in the other system arrive here automatically — no polling, no manual refresh.
Connection states
| State | Meaning | What to do |
|---|---|---|
| Active | Healthy and syncing both ways. | Nothing — it just works. |
| Needs re-authorization | The provider's access token could not be refreshed (some providers expire them periodically). | Click Re-authorize and sign in again. |
| Disabled | Paused by an administrator; nothing flows, but nothing is lost. | Re-enable when ready — no need to reconnect. |
| Error | Setup or health checks are failing. | Read the error message on the connection, fix the cause, and run a health check. |
You can run a health check on demand from the connection page. If a connection becomes unhealthy or needs re-authorization, the responsible users are notified automatically — see Notifications.
Both directions, without loops
Syncing two systems both ways risks a change bouncing back and forth forever. The CRM guards against this automatically: every incoming change is checked against what was just sent out, and echoes are dropped before they touch your data. When the system detects a genuine conflict — the same record changed in both systems at once — it applies your space's conflict policy, and unclear cases land in a review queue for a human decision rather than being guessed at.
by workflows you can inspect, and administrators can adjust provider quirks without waiting for a
software update. See Automations.
Pausing or removing a connection
- Disable pauses the connection. Incoming updates are politely acknowledged but ignored, and
nothing is sent out. Re-enabling picks up where you left off.
- Uninstall disconnects for good: event subscriptions are cancelled, access tokens are revoked
at the provider, and the connection is removed. Historical link information is kept by default so past syncs remain traceable.
synced data without ever seeing these screens. See Who Can See What.