Skip to main content
CloudTalk doesn’t have a built-in connector for every CRM. If you’ve built your own system, or use a platform that isn’t on our native integrations list, you can still connect it to CloudTalk. This article explains the supported paths.
User level: Admin

​
Before you start

API access is available on the Essential plan and above. For where to find your keys and how to generate them, see How to access and generate your CloudTalk API keys. If you don’t see the API Keys tab in your dashboard, your account is likely on a lower plan. If you’re unsure, contact CloudTalk Support and we’ll check for you.

​
Option 1: Direct REST API integration (for developers)

CloudTalk provides a public REST API that lets you read and write data programmatically, including contacts, calls, and recordings.
  1. Generate your API credentials: go to Settings > API Keys and click + Add API Key. Copy both the Access Key ID and the Access Key Secret.
  2. Send requests to the API at api.cloudtalk.io, using Basic Authentication (your Key ID as the username and your Secret as the password). Note that this is a different address from developers.cloudtalk.io (the docs) and dashboard.cloudtalk.io (the dashboard), so make sure your requests go to api.cloudtalk.io.
  3. Browse the available endpoints and request formats at developers.cloudtalk.io.
  4. Build the logic in your CRM to call these endpoints on the events you care about, for example creating or updating a contact after a call ends.
Tip: Test your calls in a tool like Postman before wiring them into your CRM. Use the Authorization > Basic Auth option and paste your Key ID and Secret. Keep an eye on the rate-limit response headers and back off if you hit them; the current limits are documented at developers.cloudtalk.io.

​
Option 2: Receive real-time events with Webhooks (for developers)

Webhooks send CloudTalk events to an HTTPS endpoint you own the moment they happen, so your CRM stays in sync without polling the API. Events cover calls, contacts, users, messages, Conversation Intelligence, VoiceAgents and Dialer. Each event arrives as signed JSON.
  1. Go to Settings > Webhooks and click Add endpoint. You need an Admin role.
  2. Enter your HTTPS URL and choose the event types you want. Leave the selection empty to receive all events, including ones added later.
  3. Copy the endpoint’s signing secret and verify the signature on every delivery.
  4. Click Send test event and check that your endpoint responds with a 2xx. You’ll see the result in the delivery log.
Failed deliveries are retried automatically, and you can resend or recover them from the same page for up to 30 days. For payloads, signature verification and best practices, see the Webhooks developer guide.

​
Option 3: Push events to your CRM with Workflow Automation

If you want CloudTalk to send data to your CRM automatically when something happens (for example, when a call ends), you can set up a Workflow Automation that sends an HTTP request to an endpoint you control.
  1. In your CRM, or on a server you control, set up an endpoint that can receive HTTP POST requests.
  2. In CloudTalk, go to Settings > Workflow Automations and create an automation that triggers on the event you want and adds an action that sends an HTTP request to your endpoint URL. See the Workflow Automations guide for setup.
  3. CloudTalk sends the event data to your endpoint when the trigger fires.
  4. Parse the payload in your CRM to update records, log calls, or trigger follow-up actions.
Good to know: Workflow Automation HTTP requests are delivered on a best-effort basis. If your endpoint is temporarily unreachable, a delivery can be missed, and there’s no self-serve replay. If you need reliable event delivery with retries and replay, use Webhooks (Option 2) instead.

​
Option 4: No-code bridge via Zapier or Make

If you’d rather not write code, Zapier and Make can act as a bridge between CloudTalk and your CRM. Both support CloudTalk as a trigger and an action source. Zapier: Follow the Configure Zapier guide to connect your CloudTalk account, then create a Zap that triggers on a CloudTalk event and sends data to your CRM, either through a native CRM action or a webhook step. Make (formerly Integromat): Add the CloudTalk app in Make (see Make’s CloudTalk documentation at apps.make.com/cloudtalk), then build a scenario that triggers on a CloudTalk event, such as a new call, and maps the fields into your CRM. Make’s CloudTalk app includes a generic “Make an API Call” action, so if your CRM isn’t a native Make app, or you need a CloudTalk operation without a dedicated module, you can still reach any CloudTalk endpoint through that step. Both tools support custom webhook/HTTP steps, so even a CRM that isn’t a native app in either platform can still receive data.

​
Which option is right for me?

Need help or have a question? Just reach out through our Support portal — we’re here for you.