Get notified

Campaign webhook events

The seven events an outbound campaign sends to your webhooks, from launch to each recipient's final result, with their payloads.

An outbound campaign sends seven events to your webhooks: six for the campaign itself and one for each recipient when they are finished with.

EventWhenFields beyond campaign
campaign.launchedThe campaign starts dialling: launched now, or its scheduled start passedtrigger
campaign.scheduledA draft is given a start time, or a scheduled campaign's start movesNone. The start is in campaign.scheduledStartAt
campaign.pausedSomeone paused it, or the platform paused itreason, detail
campaign.resumedA paused campaign starts dialling againNone
campaign.completedThe last recipient was settledcounts
campaign.cancelledSomeone cancelled itNone
campaign.recipient.finishedA recipient reached a final stateSee Recipient finished

Each event is sent once for the change it reports, from the app, the assistant, the campaigns API or the platform itself.

Campaign events

The six campaign events carry the same campaign object and the time of the change.

{
  "id": "6c1f0b6e-2d4a-5c7e-9a1b-3e5f7a9c0d2e",
  "event": "campaign.paused",
  "data": {
    "campaign": {
      "id": "9d4b2e70-…",
      "name": "November outreach",
      "agentId": "0c9e1d2f-…",
      "status": "paused",
      "fromNumber": "+61861497310",
      "scheduledStartAt": null,
      "scheduledStartTimezone": null,
      "startedAt": "2026-11-10T22:00:04.112Z",
      "completedAt": null
    },
    "reason": "spend_cap",
    "detail": null,
    "occurredAt": "2026-11-11T01:42:10.031Z"
  }
}
FieldMeaning
campaign.statusThe status after the change
campaign.scheduledStartAtThe scheduled start, UTC, or null
campaign.startedAt, campaign.completedAtWhen dialling began, and when the campaign completed or was cancelled, UTC
triggerOn campaign.launched: launch when someone launched it, schedule when its start time passed
countsOn campaign.completed: recipients by status, total, pending, calling, analysing, completed, noAnswer, failed and cancelled
occurredAtWhen the event was sent, UTC

Why a campaign paused

reasonMeaning
manualSomeone paused it in the app, the assistant or the API
spend_capSpend reached the campaign's spend cap
billingThe workspace can't be billed. detail says why: card_required, account_past_due, spend_cap_reached, subscription_canceled or trial_used
entitlementCampaigns were switched off for the workspace
agent_unresolvedThe campaign's agent can no longer be found
dialer_disabledOutbound calling is switched off on our side
otherA reason not on this list. detail holds it

detail is null for every reason but billing and other.

Recipient finished

campaign.recipient.finished is sent once per recipient, when they reach a final state and will not be called again.

{
  "id": "0f8e2c41-7b3a-5d9e-8c2f-1a4b6d8e0c3a",
  "event": "campaign.recipient.finished",
  "data": {
    "campaign": { "id": "9d4b2e70-…", "name": "November outreach" },
    "recipient": { "id": "41c7a8e3-…", "phoneNumber": "+61412345678", "name": "Sam Lee" },
    "result": "completed",
    "outcome": "booked",
    "converted": true,
    "attempts": 2,
    "stepId": "call-1",
    "lastSessionId": "3f2a9c1e-…",
    "summary": "Booked a quote visit for Thursday.",
    "finishedAt": "2026-11-11T01:40:55.318204+00:00"
  }
}
resultMeaning
completedA call connected, or the sequence ended on a text or a reply to one
no_answerEvery attempt went unanswered, busy or to voicemail
failedThe number was invalid, or the calls failed
stoppedSomeone stopped calling them, or, with outcome left_audience, they stopped matching the audience of a campaign that keeps adding contacts who match
suppressedThe number was on the do-not-call list when its turn came
cancelledThe campaign was cancelled while they were waiting for a call
FieldMeaning
outcomeThe id of the outcome the sequence ended on, such as booked, or the last call's result when nobody was reached, such as voicemail or invalid_number. A sequence a text reply ended is replied (do_not_call for a STOP), and one that ended on a text is sent
convertedtrue when the call connected and outcome counts as converted
attemptsAttempts used across every step. A double dial redial is part of its attempt, and a callback uses none
stepIdThe step the sequence ended on
lastSessionIdThe last call's session, matching its conversation events, or null if they were never called
summaryThe connected call's summary, or null
finishedAtWhen the recipient reached the final state, UTC

The event is sent on the dialler's next run, within about a minute in production. For a connected call it waits for the call's analysis, up to 15 minutes, so outcome and converted are final when it arrives.

Recipients who finished before these events existed, in November 2026, send nothing.

Ids and order

Each event's id is fixed by the change it reports. A retry carries the same id, and so does the same change if it is ever reported twice. Store the ids you have handled and skip a repeat.

Events can arrive out of order. Read campaign.status, not the order of arrival, for the campaign's current state.

Subscribe

The events are in the Campaigns group of a webhook's toggles. A new webhook is subscribed to all of them. A webhook created before they existed has them switched off until you turn them on.

On this page