Connectors that write back into the systems you run
Every connector is called from inside the flow graph, so a tool call is a node with inputs, retries and an audit line — not an undocumented script on a cron.
Certified connectors
Odoo
Partners, leads, helpdesk tickets and sales orders. Contact resolution on inbound call, ticket creation on disposition, order status read back into the voice turn.
Salesforce
Contacts, cases and tasks through the REST API. Screen-pop on match, case notes written from the transcript, owner routing by skill.
HubSpot
Contacts, deals and engagement timeline. Calls and WhatsApp threads logged as engagements with recording links.
Zendesk
Ticket create and update, macro selection from disposition, side conversations for WhatsApp threads.
FreeSWITCH
Native media layer. ESL events drive call state, recording, forking for recognition and supervisor barge-in.
Custom REST webhooks
Any endpoint becomes a node: JSON schema in, mapped fields out, HMAC signature, timeout and retry policy per call.
What a connector guarantees
Connectors run under the resolved tenant, using credentials encrypted per tenant and rotated outside the image. A credential cannot be read by another tenant even when the same connector class is in use.
Failures are visible where they happen. A node that times out marks the conversation, keeps the caller in flow and surfaces the error on the record rather than silently dropping the write.
- Per-tenant credentials, rotated outside the deployment image
- Retry with exponential backoff and a hard per-node ceiling
- Field mapping defined in Studio, versioned with the flow
- Every outbound call appears on the conversation audit trail
Need a connector that is not on this list?
Most systems are one REST node away. Send us the API surface and we will scope the mapping.