POST request with a JSON body after a call reaches the live-call block to which it is connected.
Use API Request in post-call when you need another HTTP method, custom headers or authentication, retries, or response variables.
Configure the endpoint
Enter a publicly reachable HTTPS endpoint in Webhook URL. The endpoint must acceptPOST requests with a JSON body.
Send Call Data does not provide custom headers or authentication. If the endpoint requires them, use API Request instead.
Choose the payload
Choose whether Phonely sends the full call payload or a custom JSON body:
The full payload can include phone numbers, transcripts and summaries, call timing and outcome, extracted insights, links, action history, and stored variables. Some fields may be empty when the corresponding data was not available for the call.
Full call data fields
Full call data fields
Configure a custom body
Turn off Send full call data, then choose how to build the JSON body:
Manual fields support strings, numbers, booleans, arrays, objects, and nested values. Both modes support fixed values and variables available at the block.
Select a Manual field or place the cursor in the Code editor, then choose a value from Available Variables. Use variables for call details or information collected during the conversation, and fixed values for constants required by the destination.
For example, a custom body might resolve to:
Test the request
Run the block test before relying on Send Call Data. The test sends a realPOST request to the configured endpoint.
- Enter safe sample values for each variable used in the custom body.
- Review Resolved Input to confirm the URL and JSON body.
- Run the test and inspect Test Result.
- Confirm in the receiving system that the request arrived with the expected data.
Verify the live behavior
Complete a controlled call that reaches the live-call block connected to Send Call Data, then let the call end.- Confirm that the endpoint receives one request after the call.
- Check that fixed values and variables resolve correctly.
- For full call data, confirm that the fields needed by the destination are present.
- For a custom body, confirm that its JSON structure matches the endpoint’s requirements.
200 after accepting the live payload. In Call Details, expand Send Call Data to review its execution status.
Troubleshooting
No request reaches the endpoint
No request reaches the endpoint
Confirm that the configured HTTPS URL is publicly reachable and accepts
POST requests. The post-call block runs only when the call reaches the live-call block to which it is connected, so also confirm that the tested call followed that path.The endpoint rejects the request
The endpoint rejects the request
Confirm that it accepts JSON with
Content-Type: application/json and returns HTTP 200. Send Call Data cannot add custom authorization headers; use a post-call API Request when the endpoint requires them.The custom payload contains a missing or incorrect value
The custom payload contains a missing or incorrect value
Check that the variable is available at the block and enter a representative value for it during the block test. Review Resolved Input, then confirm that each manual field uses the required data type or that the raw JSON is valid.
The full payload does not contain an expected value
The full payload does not contain an expected value
Some fields depend on what occurred or was captured during the call. Complete a representative call and confirm that the source information exists in Call Details. Use a custom body when the destination needs a smaller, stable contract.
The block test succeeds, but live data looks different
The block test succeeds, but live data looks different
Full-payload tests use sample call data. Complete a controlled call to inspect the values produced by a live call.