An existing customer's no is being recognised, but...
# support
s
My Vapi agent is able to see results from make.com webhook when i use the new Test feature, but when i call the agent, the agent can't see the response data. i.e to check if customer exists in system already, if they do return their first name so agent greets them with Hi {{first_name}}. I ask the agent what my name is and it seems to just called by a random name each time even though I can see the correct name has been passed from the web hook in the response. Is this also aknown issue or is there something else I should look at?
v
Hi there! 👋 I understand your frustration with the Vapi agent recognizing the customer's number but using a random name instead of the correct name from the webhook response. While I can't definitively say if this is an officially known issue, I can help you troubleshoot this problem. Based on the information I've found, there are several potential reasons why this might be happening: ## Possible Causes ### 1. Variable Handling Issues The agent might not be correctly configured to handle the dynamic variable containing the customer's name. According to information I found, there could be issues with how the variable is being referenced or interpolated in the tool call. Make sure you're using the correct syntax for variable interpolation and that the variable names match what the Vapi assistant expects. ### 2. Data Format Problems The webhook response format might not be what Vapi expects. According to the documentation, ensure that: - The JSON response is correctly formatted with the proper
toolCallId
and
result
fields - The expected format follows this structure:
Copy code
json
{
    "results": [
        {
            "toolCallId": "X",
            "result": "Y"
        }
    ]
}
### 3. Webhook Configuration Issues There might be a misconfiguration in the webhook URL settings within your VAPI account. Double-check that the URL for the start of call events is correctly set to your server URL and not the
https://hook.us2.make.com/...
URL. ### 4. Potential Caching Issues The agent may be experiencing a caching issue, remembering past conversations and using that information in subsequent calls instead of the new data from the webhook. ## Troubleshooting Steps 1. **Check Variable Configuration**: Ensure you're using dynamic variables correctly with
assistantOverrides
and
variableValues
to set the name dynamically for each call.
2. **Verify JSON Format**: Make sure your webhook response follows the expected format and that the content-type is set to
application/json
. 3. **Test Manually**: Try triggering the make.com webhook manually using a tool like Postman or cURL to verify it's operational and sending data correctly. 4. **Check Logs**: Review logs in both VAPI and Make.com for any error messages that might indicate what's going wrong. 5. **Simplify for Testing**: Create a simplified scenario in Make.com to test the basic connectivity before adding complexity. 6. **Try Recreating the Agent**: Some users have reported that deleting the old assistant and creating a new one fixed similar issues. Would you like me to elaborate on any of these troubleshooting steps or suggest additional approaches to resolve this issue? Sources: - [Known issues with Vapi agent and make.com webhook integration](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335308574556946480) - [Troubleshooting steps for Vapi agent not retrieving data from make.com webhook](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336345690393149452) - [How Vapi agents use data from make.com webhooks](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335054553250533439) - [Vapi agent recognizes customer number but not name from make.com webhook](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334280135683084328) - [Why is Vapi agent using a random name even though the correct name is passed from the web hook in the response?](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335230139252080691)
s
is there a way to clear cache related to vapi agents
k
Hey! To help track down this issue, could you share: - The call ID - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!
s
ive fixed it somehow now
k
Marking this ticket as Solved ✅