- Not Connected State
- Connected State
This payload is sent when a call attempt is made but the contact is not reached (e.g., busy, no answer).
Key Fields for Not Connected State
- callStatus:
"busy"- Indicates the call was not connected - analysis.success:
false- No successful conversation - analysis.disposition:
"Attempted"- Call was attempted but not completed - connected:
truein input but call didn’t result in conversation - conversation: Not present in the payload
Common Fields
- action_type: Type of webhook action —
"create","update", or"reupdate"(a resend of an already-sent update; suppress these with the callback’s Don’t send reupdates setting) - activityId: Unique identifier for the activity
- leadId: Unique identifier for the lead
- referenceId: Your custom reference identifier
- phone: The lead’s phone number — omitted when
referenceIdis set (useleadData.phoneinstead in that case) - leadData:
{ phone, name }— always present regardless ofreferenceId - timestamp: Unix timestamp in milliseconds
- activity.type: Type of activity (e.g., “call”)
- activity.status: Overall status of the activity
- activity.fromState: Previous state in the process flow
- activity.toState: New state after the activity
- activity.result.isUserInitiated:
trueif this was an incoming (customer-placed) call; the key is absent entirely — notfalse— for outgoing calls. - activity.result.analysis.connectedStatus: whether the call actually connected —
"connected","not-connected", or"connected-deferred"(connected, but the conversation wasn’t fully settled yet when evaluated). - leadSummary: Human-readable summary of the lead’s activities
- leadDisposition: Current disposition of the lead
