Hello, I am using Make.com to automate a Vapi call, but I am having trouble with the customer name not being recognized or processed correctly by the Vapi assistant. Could you help me understand why the customer name I send through the Vapi module on Make is not working as expected?

@shfq Hello! I'd be happy to help you troubleshoot the issue with the customer name not being recognized correctly by the Vapi assistant when using Make.com. To assist you effectively, I'll need a bit more information: 1. Could you please provide the exact format or method you are using to send the customer name to the Vapi module on Make? 2. Are there any specific error messages you're receiving, or is the name just not being recognized? 3. Have you checked if the customer name field is correctly mapped in your Make.com scenario? Once I have these details, I'll be able to offer more targeted advice or suggest the next steps to resolve the issue.

Just because you put the name - does not mean it's being used in the prompt. That is just there for your reference.

@Vapi No, there are no error messages. In the prompt, I tried using [name] and {{name}}.... https://cdn.discordapp.com/attachments/1280967295262527558/1280969271643476039/image.png?ex=66da0319&is=66d8b199&hm=164069b42d25219c5c8d8738bf71407e9d3884640a18e7d767e0ccca1edc344a&

@shfq I see, it sounds like there might be an issue with the way the customer name is being formatted or passed through the prompt in Make.com. Typically, Make.com uses double curly braces

{{ }}

to reference data from previous modules in a scenario. Here's what you can check to ensure the customer name is being processed correctly: 1. **Data Mapping**: Make sure that the customer name is correctly mapped from the source (e.g., a database, form input, etc.) to the Vapi module. The mapping should look something like

{{some_module.some_field}}

. 2. **Prompt Structure**: Ensure that the prompt in the Vapi module is structured to include the mapped customer name. For example, if your prompt is "Hello, [name]! How can I assist you today?" you should replace

[name]

with the mapped field, like this: "Hello, {{customer_name}}! How can I assist you today?" where

customer_name

is the correct field from the previous module. 3. **Data Format**: Check if the customer name contains any special characters or formatting that might not be recognized by the Vapi assistant. It should be a plain text string. 4. **Module Configuration**: Review the Vapi module configuration in your Make.com scenario to ensure that all required fields and data types are correctly set up. If after checking these points the issue persists, it might be helpful to test the Vapi call with a hardcoded customer name directly in the prompt to see if the issue is with the data mapping or with the Vapi assistant processing the name. If you need further assistance, please provide more details about your scenario configuration, and I'll do my best to help you resolve this issue.

That has nothing to do with variables

@Chowderr Can you provide more details?

If you are using make, you have have to use a HHTP module. If you want the information to be dynamic just map it.

your not passing dynamic variables using assistant overrides correctly check this https://docs.vapi.ai/assistants/dynamic-variables and it will work correctly.

Ok, I'll try it. Thanks!

How did you solve this problem? I have exactly the same problem.