Send calls to Zapier, Make or n8n

Point a webhook at a Zapier, Make or n8n flow so every finished call, message and booking reaches your other apps.

Last updated November 3, 2026

Zapier, Make and n8n all start a flow when a web address receives a message. Robofono sends that message for you each time a call ends, so a finished call can add a row to a spreadsheet, create a contact in your CRM or post to a chat tool without anyone copying anything by hand. The Integrations page in the app menu shows the steps and a sample message.

Suggested image Screenshot of the Integrations page scrolled to the Zapier, Make and n8n card: the three numbered steps, the four call event names as chips, the sample call.completed JSON, and the Open Developers button at the right of the card.

What you need: an account with one of the three tools, and access to Settings > Developers. You can add an endpoint if you own the account, are an administrator on it, or are a client with API access switched on for your location. If your provider has not switched it on, the Integrations page says so.

Set it up

  1. In your tool, start a new flow with a webhook trigger, and copy the web address it gives you.
    • Zapier: choose the Webhooks by Zapier app and the Catch Hook event.
    • Make: add the Webhooks module and choose Custom webhook.
    • n8n: add a Webhook node, set the method to POST, and copy its production URL. The test URL only works while the node is waiting for a test message.
  2. Open Settings > Developers and press Add endpoint on the Outbound webhooks card.
  3. Paste the address into the URL field. It has to be https://.
  4. Tick the call events you want: call.completed, call.failed, call.message_taken and call.booking_created. Call events are off until you tick them.
  5. Press Add endpoint. The signing secret is shown once. Copy it somewhere safe if you want to check signatures later.
Suggested image Screenshot of the Add endpoint dialog on Settings > Developers: a Zapier-style catch hook URL in the URL field and call.completed, call.failed, call.message_taken and call.booking_created ticked in the event list.

Then make a test call to one of your numbers. When it ends, the call arrives in your tool. Your tool can now use the fields to build the rest of the flow.

What a finished call looks like

Every message has the same outer shape: an id, a type, a created_at time, the workspace_id of the location and a data block. For call.completed the data block holds:

  • call_id: the id of the call.
  • location_id, agent_id and number_id: the location, the agent and the phone number that took the call.
  • direction: whether the call came in or went out.
  • from and to: the phone numbers on each end.
  • caller_name: the caller's name, when the agent got it.
  • started_at and ended_at: when the call began and ended.
  • duration_seconds and billed_seconds: how long the call lasted and how many seconds were billed.
  • outcome and summary: how the call ended (for example, booked) and a one-line summary.
  • language: the language of the call.
  • extracted: the details your agent collected, or null when it collected none.
  • flagged: whether the call was flagged.

call.failed carries the same fields. call.message_taken and call.booking_created carry the call_id, the workspace_id and a message or a booking with the caller's details, the times and the notes. Credits are never part of any call message.

The Integrations page shows a full sample of call.completed with a Copy sample button. Paste it into your tool if the tool asks for an example message before it lets you map fields.

Good to know

  • One message per event. A call can send call.completed or call.failed, plus one call.message_taken for each message and one call.booking_created for each booking. They arrive after the call ends, in no fixed order.
  • Retries. If your tool does not answer with a success code, Robofono tries again for up to 24 hours. Each message keeps its id on every retry, so a flow that stores the id can ignore duplicates.
  • Keep the address private. Zapier, Make and n8n addresses are secrets in practice: anyone who has one can post to your flow. Messages carry caller names, numbers and message text, so do not share the address or paste it into places others can read.
  • Check the log. If nothing arrives, press Show log on the endpoint in Settings > Developers to see each attempt and what your tool answered.
  • Client calls stay with the client. Endpoints set up by an agency do not receive a client location's call events. The client adds their own endpoint.

For signatures, test sends and the delivery log, see Outbound webhooks. If you would rather read calls on demand than receive them, see Create and manage API keys.

Was this helpful?

Still stuck? Send us the profile and the comment you are looking at and we will answer with the fix rather than a link back here.

Contact Robofono support