Issue Summary: I'm using VAPI with Make.com to schedule and manage appointments. When I call VAPI to schedule an appointment, it correctly asks for my name, service, and date. For example, I say: Name: Josh Date: April 4 at 1 PM Service: Regular checkup This data is then sent to a Make.com webhook. However, there is no dedicated customer name field in the webhook data. Instead, the description contains merged details like "scheduleJoshRegular checkup". The appointment is then successfully added to my Google Calendar. Problem with Cancellation: When I test canceling the appointment through VAPI, it asks for my name and appointment date. I provide: Name: Josh Date: April 4 at 1 PM However, the webhook does not find and delete the event because the appointment in Google Calendar does not store "Josh" as a separate customer name—it only contains the description "scheduleJoshRegular checkup". To work around this, I tried canceling using "scheduleJoshRegular checkup" as the name, and the system was able to locate and delete the event successfully. But this is not ideal. What I Need: VAPI should send a customer name field separately, instead of merging it into the description. The system should be able to locate, reschedule, or cancel appointments based on the actual customer name, not just the description. Make.com should receive the correct information to process cancellations and reschedules properly. Question: How can I configure VAPI to send a distinct customer name field so that I can reliably manage appointments in Make.com and Google Calendar? the screenshot i have attached is the information coming from vapi to make.com (webhook) @Mason https://cdn.discordapp.com/attachments/1349889569301991455/1349889569834663987/Screenshot_2025-03-13_1802311.png?ex=67d4be21&is=67d36ca1&hm=0ccc342012820d1cfd28220f2f3f5d24bba2f6c140d8d2c076b9c80710b4597e&

Hi there! I can help you configure VAPI to send the customer name as a separate field instead of merging it into the description 👍 Based on the screenshot you shared, I can see how the customer name "Josh" is being merged with other data in the description field as "scheduleJoshRegular checkup", which is causing issues with cancellations. Here's how to fix this: ### 1. Use

assistantOverrides

with

variableValues

When making a call using the VAPI API, modify your configuration to use dynamic variables:

javascript
const call = await vapiClient.calls.create({
  phoneNumberId: "your-phone-number-id",
  assistantOverrides: {
    variableValues: {
      customer_name: "Josh" // This will be sent as a separate field
    }
  }
});

### 2. Alternative: Use

metadata

for customer information You can also use the metadata field to include customer details:

javascript
const call = await vapiClient.calls.create({
  phoneNumberId: "your-phone-number-id",
  assistantOverrides: {
    metadata: {
      customerInfo: { name: "Josh", service: "Regular checkup" }
    }
  }
});

### 3. Verify webhook configuration Make sure your webhook URL in VAPI matches exactly what's provided by Make.com - check for typos or extra spaces. ### 4. Test the integration After making these changes, use a tool like Postman to test your webhook and verify the customer name is being sent as a separate field. This should allow Make.com to receive the customer name as a distinct field that can be used for appointment management, including cancellations and reschedules. Let me know if you need any clarification on these steps! Sources: - [Discord Thread](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341835905656291369) - [Discord Thread](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341746304744685599) - [Discord Thread](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1343862805463302184)

Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!