It was working ok last week and across 2 separate VPS endservers (N8N docker based) these are not receiving any requests from tool_calls anymore (except from Postman / macbook CLI [curl -I ]

Thanks for sharing the details! I couldn't find enough info to solve why VAPI isn't pushing tool requests to your N8N workflows anymore, especially since it was working last week and still works via Postman/CLI. There have been some recent updates to tool call schemas and workflow nodes, so you might want to double-check your workflow and tool call configurations just in case ([see changelog](https://docs.vapi.ai/changelog/2025/1/29)). I'm escalating this to a human teammate who can dig deeper and help you out!

I sent in my message in the Support section but am not yet helped yet the project am working on is urgently needed, But why vapi why😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭 😭

What do you need help with ?

Assistance with a payment issue on my Vapi account. I am trying to purchase more credits, but the transaction is being refused. Required Information 1.Email address used for your account login: vinemedia09@gmail.com Organization ID: 0d896d58-5618-4b8b-af8d-a3366c87ef6f Detailed description of the issue: I am attempting to purchase $10 in credits for my Vapi account. I have added a Visa card as a payment method and have a balance of approximately $13.50 USD. When I click "Purchase," the transaction is refused, and I receive an error message that states, "Couldn't purchase credits. Please enter a payment method to purchase credits." This is occurring despite a payment method being on file. My organization's wallet is frozen, and I cannot continue using Vapi. Screenshots of error messages or unexpected behavior are attached below I have verified that my card has sufficient funds and have used it for international transactions before. It appears to be a backend issue on Vapi's end, where the system is not recognizing the saved payment method. Thank you for your time and help. https://cdn.discordapp.com/attachments/1417182478170460160/1417220154785529866/Screenshot_2025-09-15_092837.png?ex=68c9b09f&is=68c85f1f&hm=6393c97e4b4ce40f046cf96511f4cabe961ce3f1b5091064a56d1f2aaecbf656& https://cdn.discordapp.com/attachments/1417182478170460160/1417220155271811266/Screenshot_2025-09-15_101145.png?ex=68c9b09f&is=68c85f1f&hm=e36c48cba99498c108240637072168bc0eb2dfd9b832f4725f9b870c0facea87&

I changed my response JSON code and added the POST method instead of GET in the webhook (n8n). It aways makes a POST request where it was a GET before. I do have other workflows in MAKE and it seems to accept both method with no discrimination....easier but invisible...!) { "results": [ { "toolCallId": "{{ $input.first().json.body.message.toolCalls[0].id }}"

I see where the issue might be—the switch from GET to POST in n8n could be why requests aren’t coming through, even though Postman works fine. I can help check your webhook setup and response JSON so it matches what VAPI expects. Would you like it to handle both GET and POST requests like MAKE, or keep it strict on one method? @AlexVendet

that was the solution thx for replying. POST is the only way in 🙂

Hi AlexVendet, Thanks for getting back to us. We are delighted to know your issue has been resolved. Please do let us know if you need further assistance. We will be closing this for now and have a great day ahead!