Reports and integrations
Webhooks tell your systems when something happens on the phones: a call in a queue, an answer, an outcome, an operator on a break. The API lets your software load leads, manage contacts and start calls.
{ "id": "evt_7Hq2kLm9Xa", "type": "queue.call_answered", "createdAt": "2026-10-05T09:41:12.000Z", "data": { "call": { "from": "+14155550123", "waitSeconds": 42 }, "contact": { "name": "Mark Brown" }, "queue": { "id": 100000346, "name": "Customer care" }, "operator": { "extension": "202", "name": "Laura Green" } }}
A webhook is a request the phone system sends to an address of yours the moment something happens. With Robottino webhooks your CRM, back office or automation tool knows straight away that a call came in, an operator answered, a caller left a score or asked to be called back. Nobody has to check by hand.
You choose the events, from 27 in seven groups: calls, queues, operators, IVR answerer, feedback, callback and internal chat. You can narrow them to some queues, operators, numbers or IVR menus, and send either the full event or only the fields your system needs, named the way you want.
Every delivery is signed, so your system can check it really comes from the phone system. If your address does not answer, the delivery is retried several times; the Deliveries tab shows the request and response of every attempt, and one click resends an event.
The other way round there is the public API: with an API key your software reads and creates leads and lists, searches and updates phonebook contacts, starts or pauses campaigns, reads the call history and starts a click-to-call from an operator’s phone.
With the "call ringing to the operator" event your CRM gets the caller number, the queue and the operator extension, and can open the right record before the operator picks up. Operator custom fields can carry the operator’s CRM ID too.
When an operator saves or changes a call outcome, the event reaches your system with the outcome name, note and recall date. If you only care about sales, pick the conversion event: it fires only for outcomes marked as a conversion.
The "missed call" or "abandoned in queue" event can post to Slack, open a ticket or create a callback task in your automation tool, with the number, the queue and the wait time.
Your website form calls the API and adds the contact to a list, and the call campaign works it right away. The API also lets you read a lead’s status, update it or delete it.
Your software calls the API with the operator and the number: the operator’s phone rings first, then the call to the customer goes out on the operator’s outbound line. The call history then tells you how it went.
Login, logout, break and back-to-available events, with the break duration, feed your timesheet or payroll system without manual exports.
In Webhooks press New webhook, give it a name and enter your system’s https URL. Pick the method (POST, PUT, PATCH or GET) and add headers such as an authorization key if needed.
On the Events tab tick when to send, searching by name or group. With "Only for…" you limit events to some queues, operators, numbers or IVR menus.
On the Content tab choose Full event, with all the data ready, or Custom fields: write the field names and values using variables such as {{call.from}}. The preview shows the result with sample data.
Test sends a sample request right away, even before you save, and shows your system’s response, the headers and the equivalent cURL command.
The Deliveries tab lists every send of the last 30 days with result, time and attempts. Click a row to see request and response, and use Resend to queue an event again.
HTTPS requests the phone system sends to your system when an event happens, such as a call in a queue, an answer or an outcome. Your CRM gets them in real time instead of polling for data.
27 events in seven groups: calls (inbound, ended, missed, limit reached), queues (entry, answered, abandoned, timeout, full), operators (login, logout, break, ringing, answer, outbound calls, transfer, outcome, conversion), IVR, feedback, callback and internal chat.
Each request has a Robottino-Signature header with a timestamp and an HMAC-SHA256 signature of "timestamp.body", made with the webhook’s signing secret. Your system computes the signature again and compares.
The delivery is retried after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours. If nothing gets through for more than 3 days, the webhook is paused and you get an email. You can resend events from the delivery log.
Yes. With an API key you manage campaigns, lists, leads, the phonebook and operators, read the call history and start click-to-call calls. The OpenAPI documentation lets you try requests in the browser.
Yes, with a webhook pointing at the address your automation tool gives you (for example Zapier’s "Catch Hook" trigger). Pick the events and, if you like, custom fields.
Sign up free and try this feature with your numbers, or message us on WhatsApp and we’ll show it to you.
