# Twilio + Krokul CRM

Yes. Krokul CRM integrates with Twilio and works with your own Twilio account. Text messages to your Twilio numbers become threads in the Communications section, every call is logged on the deal with its duration and recording, and managers send SMS or start a call from the contact card in Krokul. The connection runs through the Krokul app in Zapier, Make, n8n or Albato, or through the Krokul API and webhooks.

**Status:** Via API and webhooks. **Automation platforms:** Zapier, Make, n8n, Albato.

## What your team gets

### An inbound SMS starts a conversation

Twilio posts `From`, `To` and `Body` to Krokul when a text reaches one of your numbers. Krokul finds the contact by the `From` phone or creates one, opens a thread and, for a new customer, a deal. The manager answers in the thread, and Krokul sends the reply from the same Twilio number with the Messages API.

### Every call is logged with its length and recording

The Twilio status callback reports `CallStatus` and `CallDuration`, and the recording callback brings `RecordingUrl`. Krokul writes a call record on the contact and the open deal with the direction, length and a player for the recording, so a colleague can listen before the next conversation.

### Click to call from the contact card

The manager presses Call next to a phone number in Krokul. Krokul asks Twilio to create a Call that first rings the manager phone and then connects the customer, with your Twilio number as the caller ID. The finished call lands in the deal feed like any other.

### Missed calls turn into call-back tasks

When a call ends with the status `no-answer` or `busy`, Krokul creates a task for the manager of that contact with the number and the time in the title. An unknown number goes to the person you chose for new contacts.

### A stage change texts the customer

An automation rule sends an SMS through Twilio when a deal reaches a stage, for example "Ready for pickup". The text appears in the customer thread next to the manual messages.

## What moves between Twilio and Krokul

| Twilio | Krokul | Direction | When |
|---|---|---|---|
| Incoming SMS (`From`, `Body`) | Contact, thread and, for a new customer, a deal | Twilio → Krokul | Messaging webhook on each text |
| Message (Messages API) | Reply or automation text in the thread | Krokul → Twilio | When the manager sends it or a rule fires |
| Call (`CallSid`, `CallStatus`, `CallDuration`) | Call record with direction and length | Twilio → Krokul | Status callback when the call ends |
| Recording (`RecordingUrl`) | Player on the call record | Twilio → Krokul | Recording callback |
| Outbound Call (Calls API) | Call button on the contact card | Krokul → Twilio | When the manager presses Call |
| Call status `no-answer` or `busy` | Call-back task for the manager | Twilio → Krokul | Status callback |

## How to connect today

### Krokul app in Zapier, Make, n8n or Albato

1. Connect the Krokul app with an API key.
2. Use Twilio triggers such as New SMS or New Recording with Krokul actions such as Add Activity or Create Task.
3. Pair a Krokul trigger such as Invoice Paid with the Twilio action Send SMS for a payment receipt.

### Custom flow through the Krokul API and webhooks

1. Generate a Krokul API key with scopes for contacts, deals, tasks and activities.
2. Point the messaging and voice webhooks of your Twilio numbers at your receiver, and match the `From` phone to a person with contact/api-find, or add one with contact/api-create.
3. Write each text or finished call to the deal feed with activity/api-create, and create a call-back task with task/api-create when `CallStatus` is `no-answer` or `busy`.
4. For outbound texts, subscribe a Krokul webhook to card.statusChanged or invoice.paid, verify `x-crm-signature`, and send the SMS through the Twilio Messages API.

**Triggers:** New SMS; New Call; New Recording; New Transcription; New WhatsApp Message.

**Actions:** Send SMS; Call Phone; Send WhatsApp Message.

### For integrators

Twilio signs every webhook with the `X-Twilio-Signature` header, so a custom receiver checks it before it trusts the data. Through the public REST API a receiver writes call records as activities of type `call` with `durationSec` and `recordingUrl`, and texts as type `message`, the same types the app uses. Krokul webhooks carry an HMAC-SHA256 signature and a delivery log with redelivery.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Does Krokul integrate with Twilio?

Yes. Krokul integrates with Twilio through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks. SMS become threads, calls are logged with recordings, and managers text or call from Krokul.

### Where do call recordings live?

Recordings stay in Twilio storage. Krokul keeps the `RecordingUrl` on the call record and plays the file from there.

### Who pays for messages and minutes?

Your Twilio account. Krokul uses your numbers and your credentials, so Twilio bills usage to you as before.

### Do Twilio WhatsApp messages work too?

Zapier lists the Twilio trigger New WhatsApp Message and the action Send WhatsApp Message. For a WhatsApp number of its own, Krokul also integrates with WhatsApp Business.

## Limits

Twilio stays the carrier, and numbers, call routing, IVR and billing for messages and minutes live in your account there. Recordings are stored by Twilio, and Krokul keeps a playable link to each one on the call record.

## Related services

- [Aircall](https://krokul.com/en/integrations/aircall/index.md)
- [RingCentral](https://krokul.com/en/integrations/ringcentral/index.md)
- [WhatsApp Business](https://krokul.com/en/integrations/whatsapp-business/index.md)
- [Telegram](https://krokul.com/en/integrations/telegram/index.md)
- [Zoom](https://krokul.com/en/integrations/zoom/index.md)

[Customer messaging](https://krokul.com/en/integrations/category/messaging/index.md)

Twilio is a trademark of Twilio Inc. Krokul is not affiliated with Twilio.

Updated: 2026-10-12

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs