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.
Automation platformsZapierMaken8nAlbato
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.
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.
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.
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.
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.
| Twilio | Direction | Krokul | When |
|---|---|---|---|
Incoming SMS (From, Body) | Twilio → Krokul | Contact, thread and, for a new customer, a deal | Messaging webhook on each text |
| Message (Messages API) | Krokul → Twilio | Reply or automation text in the thread | When the manager sends it or a rule fires |
Call (CallSid, CallStatus, CallDuration) | Twilio → Krokul | Call record with direction and length | Status callback when the call ends |
Recording (RecordingUrl) | Twilio → Krokul | Player on the call record | Recording callback |
| Outbound Call (Calls API) | Krokul → Twilio | Call button on the contact card | When the manager presses Call |
Call status no-answer or busy | Twilio → Krokul | Call-back task for the manager | Status callback |
From phone to a person with contact/api-find, or add one with contact/api-create.CallStatus is no-answer or busy.x-crm-signature, and send the SMS through the Twilio Messages API.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.
Recordings stay in Twilio storage. Krokul keeps the RecordingUrl on the call record and plays the file from there.
Your Twilio account. Krokul uses your numbers and your credentials, so Twilio bills usage to you as before.
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.
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.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
Twilio is a trademark of Twilio Inc. Krokul is not affiliated with Twilio.
