JIHO
12/13/2025, 4:20 PMChiranjeet Mishra
12/13/2025, 4:21 PMVapi Support Bot
12/13/2025, 4:21 PM{} request body, ensure your tool's configuration includes a properly defined body schema with the parameters you want to send. For example:
json
{
"type": "apiRequest",
"method": "POST",
"url": "https://your-n8n-webhook-url",
"body": {
"param1": "{{variable1}}",
"param2": "{{variable2}}"
}
}
Update your tool in the Vapi dashboard to match this structure—this will ensure parameters are included in the request body sent to n8n. For more details, see the [API reference](https://docs.vapi.ai/api-reference/tools/create?explorer=true).
Source:
- [API Reference: Create Tool](https://docs.vapi.ai/api-reference/tools/create?explorer=true)Ridham Golakiya
12/13/2025, 4:38 PMRidham Golakiya
12/13/2025, 4:39 PMJIHO
12/13/2025, 9:02 PMJIHO
12/14/2025, 12:50 AMJIHO
12/14/2025, 1:07 AMJIHO
12/15/2025, 11:12 PMVapi Support Bot
12/15/2025, 11:13 PM{} request body, make sure your tool configuration explicitly defines the body property with all required parameters mapped to variables. For example:
json
{
"type": "apiRequest",
"method": "POST",
"url": "https://callivo.app.n8n.cloud/webhook/callivo-lead",
"body": {
"notes": "{{notes}}",
"car_make": "{{car_make}}",
"car_year": "{{car_year}}",
"sheet_id": "{{sheet_id}}",
"car_model": "{{car_model}}"
// Add other fields as needed
}
}
Descriptions are optional and not required for the body to populate. For more details, see the [API reference](https://docs.vapi.ai/api-reference/tools/create?explorer=true).
Source:
- [API Reference: Create Tool](https://docs.vapi.ai/api-reference/tools/create?explorer=true)JIHO
12/16/2025, 10:56 PMJIHO
12/16/2025, 10:57 PMVapi Support Bot
12/16/2025, 10:58 PMbody property in your tool configuration like this:
json
{
"type": "apiRequest",
"method": "POST",
"url": "https://callivo.app.n8n.cloud/webhook/callivo-lead",
"body": {
"notes": "{{notes}}",
"car_make": "{{car_make}}",
"car_year": "{{car_year}}",
"sheet_id": "{{sheet_id}}",
"car_model": "{{car_model}}"
// Add all other fields as needed
}
}
Descriptions are optional and do not affect the request body. Update your tool to match this structure and test again—this should resolve the {} body issue. For more details, see the [API reference](https://docs.vapi.ai/api-reference/tools/create?explorer=true).
Source:
- [API Reference: Create Tool](https://docs.vapi.ai/api-reference/tools/create?explorer=true)JIHO
12/17/2025, 12:51 AMVapi Support Bot
12/17/2025, 12:52 AM{} in the request body if your body property is correctly defined and mapped to variables.
Make sure your tool configuration includes all required fields in the body section, like this:
json
"body": {
"notes": "{{notes}}",
"car_make": "{{car_make}}"
// Add all other fields as needed
}
If you still see {} during testing, double-check that your variables are properly set and referenced in the configuration.
For more details, see the [API reference](https://docs.vapi.ai/api-reference/tools/create?explorer=true).
Source:
- [API Reference: Create Tool](https://docs.vapi.ai/api-reference/tools/create?explorer=true)JIHO
12/17/2025, 12:59 AMVapi Support Bot
12/17/2025, 1:00 AMbody property with all required fields mapped to variables, like this:
json
"body": {
"notes": "{{notes}}",
"car_make": "{{car_make}}",
"car_year": "{{car_year}}"
// Add all other fields as needed
}
If you still see {} in the test, double-check your variable mappings and configuration.
For more details, see the [API reference](https://docs.vapi.ai/api-reference/tools/create?explorer=true).
Source:
- [API Reference: Create Tool](https://docs.vapi.ai/api-reference/tools/create?explorer=true)JIHO
12/17/2025, 1:02 AMVapi Support Bot
12/17/2025, 1:04 AM{} in the request body, double-check that your tool configuration includes a body property explicitly mapping each field to its variable, like this:
json
"body": {
"notes": "{{notes}}",
"car_make": "{{car_make}}",
"car_year": "{{car_year}}"
// Add all other fields as needed
}
You do not need to add variables in any "second request body section"—all variables should be mapped in the main body property as shown above. For more details, see the [API reference](https://docs.vapi.ai/api-reference/tools/create?explorer=true).
Source:
- [API Reference: Create Tool](https://docs.vapi.ai/api-reference/tools/create?explorer=true)JIHO
12/17/2025, 1:07 AMVapi Support Bot
12/17/2025, 1:08 AMbody property. It should look like this:
json
"body": {
"notes": "{{notes}}",
"car_make": "{{car_make}}",
"car_year": "{{car_year}}"
// Add all other fields as needed
}
If the body property is missing or empty, update it to include all required fields mapped to their variables. For more details, see the [API reference](https://docs.vapi.ai/api-reference/tools/create?explorer=true).
Source:
- [API Reference: Create Tool](https://docs.vapi.ai/api-reference/tools/create?explorer=true)JIHO
12/17/2025, 1:53 AMVapi Support Bot
12/17/2025, 1:55 AM{} despite a correct schema, try **deleting and recreating the tool from scratch**—sometimes the visual schema builder can cache old definitions and not update properly. After recreating, define your body property as shown below and test again:
json
"body": {
"customer_name": "{{customer_name}}",
"phone_number": "{{phone_number}}",
"damage_description": "{{damage_description}}"
// Add all other fields as needed
}
This often resolves persistent {} issues caused by UI or caching glitches. For more details, see the [custom tools troubleshooting guide](https://docs.vapi.ai/tools/custom-tools-troubleshooting).
Source:
- [Custom tools troubleshooting](https://docs.vapi.ai/tools/custom-tools-troubleshooting)JIHO
12/18/2025, 1:05 AMVapi Support Bot
12/18/2025, 1:07 AMvariableExtractionPlan, so if variableExtractionPlan.schema.properties is empty, the request body will show {}.
Currently, the documentation does not specify a way to populate variableExtractionPlan from the dashboard UI—this may be a limitation or a UI bug.
Action: Try editing your tool via the API to manually set variableExtractionPlan as shown in the [API reference](https://docs.vapi.ai/api-reference/tools/create?explorer=true):
json
"variableExtractionPlan": {
"schema": {
"properties": {
"customer_name": { "type": "string" },
"phone_number": { "type": "string" },
"damage_description": { "type": "string" }
}
}
}
If this resolves the issue, report the missing UI support to Vapi support for a permanent fix.
Source:
- [API Reference: Create Tool](https://docs.vapi.ai/api-reference/tools/create?explorer=true)JIHO
12/18/2025, 1:12 AMVapi Support Bot
12/18/2025, 1:14 AMvariableExtractionPlan, use the following API call:
Endpoint:
PATCH https://api.vapi.ai/tool/718c989a-994c-4706-a8a1-39815afad815
Payload example:
json
{
"variableExtractionPlan": {
"schema": {
"properties": {
"customer_name": { "type": "string" },
"phone_number": { "type": "string" },
"damage_description": { "type": "string" }
// Add other fields as needed
}
}
}
}
This will populate variableExtractionPlan for your tool. See the [API reference](https://docs.vapi.ai/api-reference/tools/update) for more details.
Source:
- [Update Tool API Reference](https://docs.vapi.ai/api-reference/tools/update)Chiranjeet Mishra
12/18/2025, 9:52 PMJIHO
12/20/2025, 2:43 AM