Skip to main content
POST
/
to_your_webhook_url
cURL
curl --request POST \
  --url https://app.phonely.ai/api/to_your_webhook_url
{
  "agentName": "<string>",
  "mentionedEmail": "<string>",
  "unansweredQuestions": [
    "<string>"
  ],
  "actionItems": [
    "<string>"
  ],
  "followUpReason": "<string>",
  "followUp": "<string>",
  "recordingUrl": "<string>",
  "dashboardUrl": "<string>",
  "purpose": "<string>",
  "sentiment": "<string>",
  "transcriptText": "<string>",
  "transcript": [
    {
      "content": "<string>",
      "role": "<string>"
    }
  ],
  "mentionedDate": "<string>",
  "businessPhoneNumber": "<string>",
  "keyPoints": [
    "<string>"
  ],
  "topic": "<string>",
  "longSummary": "<string>",
  "callId": "<string>",
  "ai_success": "<string>",
  "customerPhoneNumber": "<string>",
  "callStarted": "2023-11-07T05:31:56Z",
  "callEnded": "2023-11-07T05:31:56Z",
  "duration": 123,
  "callerName": "<string>",
  "callDirection": "<string>",
  "mentionedTime": "<string>",
  "summary": "<string>",
  "endedReason": "<string>"
}

Documentation Index

Fetch the complete documentation index at: https://docs.phonely.ai/llms.txt

Use this file to discover all available pages before exploring further.

Phonely can send a POST request to your webhook endpoint after a call completes. Use this when you want to forward summaries, transcripts, outcomes, or call links into another system.

​
Where To Configure It In Phonely

  1. Open /agent/{agentId}?tab=workflows.
  2. Add the Send Call Data post-call action to the workflow.
  3. In the Configure tab, enter your webhook URL.
  4. Choose whether to send the full call payload or a custom body.
  5. Open the Test tab and send a sample request.
  6. Confirm your receiver returns a success response.

​
Receiver Requirements

  • The receiver must accept HTTPS requests.
  • The receiver must be ready to parse JSON request bodies.
  • The receiver should return a 2xx response after successful processing.
  • The receiver should log failures for later debugging.

​
Payload Contents

The schema below documents the standard post-call payload. It includes fields such as:
  • call and agent identifiers
  • transcript text and structured transcript
  • summary, long summary, topic, and sentiment
  • recording and dashboard URLs
  • caller and business phone numbers
  • call start time, end time, duration, and end reason

​
Testing Tips

  • Return 200 OK after storing or accepting the payload.
  • Re-run the Test tab any time you change the expected body or the receiver.
  • If the receiver returns a non-success status, inspect the receiver logs before publishing the workflow.

Response

Successful response

​
agentName
string

Name of the agent handling the call

​
mentionedEmail
string | null

Email address mentioned during the call

​
unansweredQuestions
string[]

List of questions that were not answered during the call

​
actionItems
string[]

List of action items identified during the call

​
followUpReason
string

Reason for any required follow-up

​
followUp
string

Indicator if follow-up is required

​
recordingUrl
string

URL to access the call recording

​
dashboardUrl
string

URL to access the call dashboard

​
purpose
string

Main purpose or topic of the call

​
sentiment
string

Overall sentiment of the call

​
transcriptText
string

Full text transcript of the call

​
transcript
object[]

Structured transcript of the call

​
mentionedDate
string | null

Any specific date mentioned during the call

​
businessPhoneNumber
string

Phone number of the agent

​
keyPoints
string[]

Key points or highlights from the call

​
topic
string

Main topic or category of the call

​
longSummary
string | null

Detailed summary of the call

​
callId
string

Unique identifier for the call

​
ai_success
string

Indicator of AI's success in handling the call

​
customerPhoneNumber
string

Phone number of the customer

​
callStarted
string<date-time>

Date string when the call started

​
callEnded
string<date-time>

Date string when the call ended

​
duration
number

Duration of the call in seconds

​
callerName
string

Name of the caller

​
callDirection
string

Direction of the call (inbound/outbound)

​
mentionedTime
string | null

Any specific time mentioned during the call

​
summary
string

Brief summary of the call

​
endedReason
string

Reason for the call ending