Vapi tool is working when i put make.com webhook url .. But its not working when i add n8n.io webhook url in custom tool section .

VAPI does not trouble shoot automation platforms by the way. But are you on the cloud or self hosted?

message has been deleted

On Cloud itself. Vapi tool's has inbuilt integration of make.com . For n8n we have to add as custom tools.

@Kishore Kumar It seems like there might be an issue with the configuration of your n8n.io webhook URLs. The status code 404 indicates that the URL cannot be found, which suggests that the webhook URL might be incorrect or not properly set up in n8n. The status code 400 indicates a bad request, which could mean that the data being sent to the n8n webhook is not in the expected format or is missing required fields. Here are a few steps you can take to troubleshoot the issue: 1. **Verify the Webhook URL**: Make sure that the n8n.io webhook URL you've entered in the VAPI custom tool section is correct. It should be the exact URL provided by n8n when you set up the webhook node. 2. **Check n8n Configuration**: Ensure that your n8n workflow is active and properly configured to receive the data from VAPI. The webhook method (GET, POST, etc.) should match what VAPI is using to send the data. 3. **Inspect Payload Format**: Review the data payload that VAPI is sending to n8n. Ensure that it matches the expected format that your n8n workflow is configured to handle. 4. **Check for Typos or Errors**: Double-check for any typos or errors in the webhook URL or the data payload. 5. **n8n Webhook Settings**: In n8n, make sure that the webhook is set to the correct HTTP method and is listening for requests. 6. **Firewall or Network Issues**: If you're using n8n cloud, there shouldn't be any firewall issues, but if you're using a self-hosted version, ensure that your network configuration allows incoming requests to your n8n instance. 7. **Logs and Error Messages**: Use the logs and error messages from both VAPI and n8n to get more insight into what might be going wrong. If after checking these steps the issue persists, you may want to reach out to n8n support for further assistance, as the problem might be on their end or there might be additional configuration needed that is specific to n8n's platform.

its still a webhook, no difference whatsoever. Also it looks like it is not recieving the tool call becuase its not set or maybe it came in after that data?

can you share the call id

CALL ID : a1a49ca6-91e1-4ff7-9e13-6adda120e463

are you using a test webhook or production? Also have you tried both?

Its test url

Try the production. That is why I ask if you were on cloud or self hosted. I am not sure if that wil fix the problem - but for some reason sometimes test would not work. I self host though - I dont pay. So the setup is different then cloud.

OK

If that's hard-coded then that might be why.

i have used that as sample . "results": [ { "toolCallId": "ef206012-081f-4697-b1a3-6a835b9aff3e", "result": " first name is {{ $json["First Name"] }} and the surname is {{ $json["Surname"] }} emailid is {{ $json["Email"] }} " } ] }

all your other webhooks work?

No. Webhooks from make.com work . N8N doesn't work

your returning response in wrong format, your supposed to return an object but instead returning strigified object. (trunucating response)

ts
🔵 17:32:37:690 Server Message Successful. (https://khyber.app.n8n.cloud/webhook-test/edfe3d17-bf74-452c-8ce4-066affc79aa9). Response: {
  "{\n    \"results\": ": {
    "\n        {\n            \"toolCallId\": \"ef206012-081f-4697-b1a3-6a835b9aff3e\",\n            \"result\": \" first name is Stuart and the surname is Stirling emailid is stuart@yahoo": {
      "com \"\n        }\n    ": {
        "\n}": [