https://vapi.ai/ logo
Join Discord
Powered by
Variable {{name}} on First Message.
# support
l
Hello, I have an automation in Make that is using the Vapi module to make outbound calls. In this automation, I am sending the variable NAME. Additionally, I am referencing this variable within the "First Message" field as {{name}}. However, when the call is made, Vapi does not use the name. It's as if it ignores the variable. What could it be?
v
message has been deleted
@Leandro Dias Hello! It sounds like you're doing everything correctly by passing the variable 
NAME
into your automation and referencing it in the "First Message" field. If Vapi is not recognizing the variable, there could be a few reasons: 1. **Variable Format**: Ensure that the variable 
NAME
is correctly formatted and passed into the Vapi module. The variable placeholder should match the format expected by Vapi, which is typically 
{{name}}
. 2. **Variable Scope**: Check if the variable 
NAME
is within the correct scope and is accessible at the point where the "First Message" is being set. 3. **Module Configuration**: Verify that the Vapi module in your Make automation is configured correctly to accept and process variables. 4. **Data Type**: Make sure that the 
NAME
variable is being passed as a string, as other data types might not be processed correctly. 5. **API Limitations**: There might be limitations or specific requirements in the Vapi API that are not met, such as needing to encode or format the variable in a certain way. If you've checked all of these and the issue persists, it might be necessary to look into the logs or error messages provided by Make or Vapi to diagnose the problem further. If you're unable to resolve the issue, please reach out to support for more detailed assistance.
You can continue this conversation by mentioning me in the message.
l
I have already checked all the points you mentioned and they are all correct. I also checked the log in Vapi and saw that it is not receiving the variable that Make is sending to Vapi. In Make, the name variable is being populated correctly. What should I do now?
v
@Leandro Dias If you've confirmed that the 
NAME
variable is correctly populated in Make and the issue seems to be on the Vapi side where the variable is not being received, here are a few steps you can take to troubleshoot further: 1. **Check Integration Settings**: Review the integration settings between Make and Vapi to ensure that the data is being sent in the expected format and that the correct endpoint is being used. 2. **Review API Documentation**: Double-check the Vapi API documentation to confirm that you're using the correct parameter names and data structures when sending data from Make. 3. **Test the API Manually**: Try to make a direct API call to Vapi using a tool like Postman or cURL with the 
NAME
variable to see if the issue persists. This can help isolate whether the problem is with the Make integration or with Vapi itself. 4. **Contact Support**: Since you've already checked the logs and the variable is not being received by Vapi, it might be time to contact Vapi support for further assistance. They may be able to provide more insight into why the variable isn't being received and help you resolve the issue. 5. **Check for Updates**: Ensure that both Make and Vapi are up to date, as there may have been updates or bug fixes that address this issue. 6. **Review Error Messages**: If there are any error messages in the logs, review them for clues as to what might be going wrong. If you need to contact Vapi support, be prepared to provide them with details of your setup, the steps you've taken to troubleshoot, and any relevant logs or error messages. This information will help them assist you more effectively.
l
still not working 😦
still not working
v
@Leandro Dias I'm sorry to hear that the issue is still unresolved. It seems like we've exhausted the basic troubleshooting steps. At this point, it would be best to reach out to Vapi support for more in-depth assistance. They will have the necessary tools and access to help diagnose and fix the problem. Please provide them with all the relevant details, including the steps you've taken, the configuration settings, and any logs or error messages. This will help them understand the context and provide you with a solution more quickly. Would you like me to guide you on how to contact Vapi support or assist you with any other information you might need before reaching out to them?
l
YES
v
@Leandro Dias Great, I'm here to help you prepare to contact Vapi support. Here's what you can do: 1. **Gather Information**: Compile all relevant information including: - Description of the issue. - Steps you've taken to troubleshoot. - Screenshots of your Make automation setup. - Logs from Make and Vapi that show the variable is not being passed correctly. - Any error messages you've encountered. 2. **Check Documentation**: Have a quick look at the Vapi documentation one more time to ensure there isn't a step or configuration you might have missed. 3. **Contact Details**: Find the contact details for Vapi support. This could be an email address, a support ticket system, or a phone number, depending on what Vapi provides. 4. **Reach Out**: Contact Vapi support using the gathered information and contact details. Be clear and concise in your communication to help them understand the issue quickly. 5. **Follow Up**: If you don't get a response within a reasonable time frame, don't hesitate to follow up. Support teams can be busy, and a gentle reminder can help ensure your issue gets addressed. Remember to be patient and cooperative with the support team as they work to help you resolve the issue. If you need further assistance with gathering information or have any other questions, feel free to ask.
s
can you send one latest call_id?
l
Hi. call_id: 14696b4c-9a5f-424f-931e-7e2ae42cd065
s
It is because variableValues isn't set
l
Hi, I set the variable, but isn`t work.
s
@Leandro Dias can you please join the office hour? https://discord.gg/RwCPr9yN?event=1288049123458682942
8 Views
PreviousNext
Powered by