Integrations Overview
Omniflow plays well with the tools you already have. Most integrations are OAuth-based and can be turned on by an admin in a few minutes — no code, no engineering tickets.
Categories
How integrations work
| Capability | Examples |
|---|---|
| Channel | Receive and send messages — Gmail, Slack, WhatsApp. |
| Sync | Pull data from external systems — Salesforce contacts, HubSpot deals. |
| Action | Trigger something external — create a Linear issue, post to Slack. |
| Tool | Expose actions to agents — salesforce_lookup_account. |
Most connectors do several of these. Salesforce, for example, syncs contacts, exposes an agent tool, and writes back conversation outcomes.
Connect an integration
The flow is the same for almost every connector:
- Open Settings → Integrations.
- Pick the connector.
- Click Connect and complete the OAuth dance.
- Pick which scopes / accounts / objects to sync.
- Save. Initial sync runs in the background.
OAuth tokens are encrypted at rest using a workspace-scoped key. Only edge functions running with service_role can read them.
Disconnecting
Disconnecting removes the integration but keeps the data already synced into Omniflow. Conversations, contacts, and traces stay; live sync stops.
| Concern | What happens |
|---|---|
| Existing conversations | Stay in the inbox; replies stop flowing through the integration. |
| Existing contacts | Stay in Omniflow; no further updates from the source. |
| Custom fields populated by the integration | Stay; no further updates. |
To remove all synced data, use Settings → Data → Purge after disconnecting.
Custom integrations
If your tool isn’t on the catalog, you have two options:
- Custom webhook tool — expose any HTTP endpoint as an agent tool. See Tools & Actions.
- Generic webhook integration — listen for events from any system and trigger Omniflow workflows. See Custom API & Webhooks.
OAuth scopes
Each integration requests the minimum scopes it needs to function. Read scopes are always preferred over read/write; write scopes are only requested when the integration needs to make changes (e.g. updating a Salesforce case status).
Audit OAuth scopes when you upgrade. New integration features may require new scopes; Omniflow will prompt you, but you should re-confirm with your security team before granting.
Open in Omniflow
Related
| If you want to… | Go to |
|---|---|
| Use an integration as an agent tool | Tools & Actions |
| Trigger automations from an integration event | Routing Rules |
| Read the API docs | API Reference |