Custom Request Body
For APIs that require a specific body format, like GraphQL APIs (Monday.com) or non-standard REST endpoints, you can define the exact JSON body instead of building it from parameters.
When to use: Enable Custom Request Body when your API expects a specific JSON structure that can't be built automatically from simple key-value parameters. Most common with GraphQL APIs.
How to Enable
- Set the HTTP method to POST, PUT, or PATCH
- Toggle on Custom Request Body
- Write your JSON body template with {{variables}} for dynamic values
Available Variables
| Variable | Description |
|---|---|
| {{caller_phone}} | Customer's phone number (auto-filled) |
| {{employee_id}} | AI agent handling the call |
| {{call_id}} | Unique ID for this call |
| {{parameter_name}} | Any parameter name you define in Step 3 |
| {{action_name.field}} | Result from a previous action in the same call |
Example: GraphQL Query (Monday.com)
Monday.com uses GraphQL, so all requests are POST to / with a query in the body:
{
"query": "query { boards(ids: {{board_id}}) { items_page(limit: 10) { items { id name column_values { id text } } } } }"
}Example: Nested JSON Body
For APIs that expect a structured payload:
{
"customer": {
"phone": "{{caller_phone}}",
"name": "{{customer_name}}"
},
"request": {
"type": "support",
"priority": "{{priority}}",
"description": "{{issue_description}}"
}
}Tip: You can still add parameters in Step 3 alongside a Custom Request Body. The parameter definitions help the AI understand what data to collect from the customer, and the values get substituted into your body template during the interaction.