Tone Webhook

Starts the workflow when a Tone call, SMS, or campaign event occurs

Tone Webhook

AI-generated

Summary

Starts a workflow when Tone sends a call, SMS, or campaign event to an auto-registered webhook, emitting the event payload as the trigger output.

Inputs

  • events — Multi-select of Tone events to listen for (call.initiated/completed, call.transfer.initiated/connected/failed/completed, campaign.started/completed, campaign.contact.answered/no_answer/failed, sms.received/delivered, or * for all). Defaults to call.completed. Sent to Tone when the webhook is registered and also used to filter incoming requests.
  • toneApi credential (required) — Tone API credential supplying baseUrl and apiKey (sent as a Bearer token) used to register and remove the webhook.

Output shape

One workflow item per accepted POST request, containing the full JSON body Tone sent (e.g. the event field plus its event data).

The webhook responds immediately (responseMode onReceived). Requests whose body.event isn't in the selected events are dropped with no workflow run, unless * is selected. Bodies with no event field are always passed through. Event filtering is done locally; the selected events are also sent to Tone at registration. Changing events requires re-activating the workflow to re-register.

Examples

Example 1: Log finished calls to a CRM

events = [call.completed]; connect Tone API credential; activate workflow.

Example 2: Handle inbound SMS and delivery receipts

events = [sms.received, sms.delivered]; branch on the event field downstream.

Example 3: Monitor everything

events = [* (all events)] to receive all call, transfer, campaign and SMS events.

Links

Discussion