Workflows & Integrations
The Zoho and Salesforce connector, webhooks and the REST API.
Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.
A call is only useful if something happens after it. Xebit turns each outcome into an action in the systems you already run: a CRM record updated, a slot booked, a ticket opened or a person alerted. There are three ways in: the CRM connector for Zoho and Salesforce, webhooks for any endpoint you run, and the REST API for everything else.
How a call becomes an action
- The call happens. Inbound or outbound, the agent works through the conversation and its business rules.
- The outcome is captured. The disposition, the fields your workflow needs, a summary and the transcript.
- Your systems are updated. Webhooks fire, the API is called or the CRM connector writes the record.
- The next step starts. A booking is confirmed, a ticket opened, a follow up scheduled or a person alerted.
Actions can also happen while the call is live, such as looking up an account or checking a calendar. Those are workflow actions on the agent: see Workflows.
The CRM connector: Zoho and Salesforce
The integrations connector writes call outcomes to the right record in Zoho or Salesforce, so nobody copies notes out of a call.
- Sign in to the dashboard at
voice.xebit.aiand open the integrations settings. - Sign in to the Xebit VoiceKit admin console and open the integrations settings. The CRM must be reachable from your deployment.
- Choose Zoho or Salesforce and authorise the connection with a CRM user that can read and update the records the agent works on.
- Map what Xebit sends to your CRM fields: the outcome, each captured field, the summary and a link to or copy of the transcript.
- Choose which agents and campaigns write to the CRM.
- Make a test call and check the record updates as the call ends.
If records do not update, see CRM Sync Errors.
Webhooks
Webhooks fire on call lifecycle events, outcomes and transfers, to any endpoint you run. Use them to start anything downstream: open a ticket, write a promise to pay into your loan management system, or have your own messaging system send the customer a confirmation. Xebit does not send SMS, WhatsApp or email to your customers; your systems do, triggered by the webhook.
- Open the webhook settings in the dashboard or admin console.
- Add your endpoint URL. It must accept HTTPS POST requests.
- Choose the events to receive: call lifecycle events, outcomes, transfers.
- Save, make a test call and check your endpoint receives the events.
Respond with a success status as soon as the request arrives and do the work in the background. Use the event ID to ignore duplicates if a delivery is retried. The payloads are described in Outbound Webhooks.
The REST API
The REST API covers campaigns, calls, lists, outcomes, recordings and transcripts. Use it to start calls from your own systems, push contact lists into campaigns, and pull results into a data warehouse or BI tool.
- Base URL:
https://api.voice.xebit.ai/v1. Create keys in the Xebit VoiceCloud dashboard. - Base URL:
https://<your-xebit-voicekit-host>/v1. Create keys in the Xebit VoiceKit admin console. - Start with Auth Setup and API Keys, then Creating Calls.
- Request limits for your account are in Rate Limits.
- Request limits and concurrency are set by your own deployment and licence band. See Rate Limits.
Teams that build agents in code can use the Agent SDK alongside the API.
Other systems
Ticketing and service desks, loan management systems, ATS and HR systems, calendars and data warehouses do not have a prebuilt connector. They connect through the REST API, webhooks and workflow actions, and because the orchestration layer is Xebit's, Xebit builds the hook into your system as part of deployment. Tell us which system a call outcome should land in.
Telephony is yours
Xebit never provides telephony or numbers. You keep your carrier, trunks and rates, and Xebit connects over standard SIP and WebSocket, so switching carrier later is a configuration change rather than a rebuild.
Air gapped deployments
In an air gapped Xebit VoiceKit deployment, webhooks, workflow actions and the CRM connector can only reach systems inside your network. Use a CRM and endpoints hosted inside the network.
Air gapped deployments apply to Xebit VoiceKit only. On Xebit VoiceCloud, your endpoints and CRM must be reachable from the internet.
Next steps
- Workflows: actions before, during and after a call
- Export Reports
- More on the capability: Workflows and integrations