To learn how to specify webhook URLs for your cloud employees in the Signals app, please see the webhook URLs configuration step in the quickstart guide.Below you will find an example of the data structure for outbound voice calls.
Outbound Call Webhook
Event Types:
- call_start: Triggered when an outbound call begins
- call_ended: Triggered when an outbound call ends
- call_analyzed: Triggered after call analysis is complete
Webhook Response Structure
When an outbound call event occurs, Signals will send a webhook response with the following structure:If metadata or custom variables are empty they will be omitted from the webhook event payload
Key Fields
Field | Description |
---|---|
event | The type of call event (call-start , call-ended , or call-analyzed ) |
call.call_type | Type of call (always “phone” for voice calls) |
call.call_direction | Direction of the call (always “outbound”) |
call.from_number | The phone number that initiated the call |
call.to_number | The phone number that received the call |
call.call_duration | Duration of the call in seconds |
call.call_status | Status of the call (e.g., “completed”, “failed”, “busy”) |
call.extracted_variables | Information extracted during the call |
call.transcript | The full conversation transcript |
call.call_analysis | Analysis results including summary and sentiment |
Usage Notes
-
Call Status
completed
: Call ended normallyfailed
: Call failed to connectbusy
: Recipient was busyno_answer
: Call was not answeredvoicemail
: Call went to voicemail
-
Call Analysis
- Available only in
call-analyzed
events - Includes sentiment analysis and call summary
- May contain custom analysis data based on your configuration
- Available only in
-
Transcripts
transcript
: Plain text version of the conversationtranscript_object
: Structured version with speaker informationtranscript_with_tool_calls
: Includes tool usage during the call