Request API from workflow not working
# supportj
Jmallia
05/22/2025, 4:53 PMHi VAPI Team,
I’ve set up a conversation workflow where one of the nodes is an API Request intended to send data captured during the call to a webhook. However, when the conversation reaches this node, the call appears to get stuck, and the API request is never made.
Could you please advise if there’s a specific configuration required for the API Request node, or if this might be an issue on your end?
Thank you for your support.
v
Vapi Support Bot
05/22/2025, 4:55 PMThank you for your message. To help diagnose the issue, could you please confirm if you are using the new
ApiRequestHttpRequestj
Jmallia
05/22/2025, 5:07 PMIt's the new one since this was made yesterday and this isn’t a configuration issue, as the same setup sometimes works, but most of the time it doesn’t. In the request body, I'm simply sending values captured from the call using variables.
Jmallia
05/22/2025, 5:08 PMAlso the page API Request Node Configuration is giving Page Not Found
k
Kings_big💫
05/22/2025, 5:53 PMEnsure the webhook URL and method are correct, the webhook returns the required toolCall Id and results format, your assistant is properly configured to use the tool..
j
Jmallia
05/22/2025, 6:27 PM@Kings_big💫 I'm not sure I fully understood. I’ve set up the request with the webhook URL, but that’s only meant to trigger another workflow on n8n. I'm not using any tools just the API Request node.
c
Chiranjeet Mishra
05/23/2025, 4:50 AMHey! To help track down this issue, could you share:
- The call ID
- When exactly this happened (the timestamp)
- What response you expected to get
- What response you actually got instead
This would really help us figure out what went wrong!
j
Jmallia
05/23/2025, 8:17 AMHi @User,
Here are the details you requested to help investigate the issue:
Call ID: ccc93c12-0bc8-445a-8549-f102b4d1fc98
Timestamp: 22 May 2025, 17:18
Expected Behaviour: The conversation should have triggered an API Request to an n8n webhook, and then proceeded to the next message to conclude the call.
Actual Behaviour: The call got stuck at the API Request node and did not proceed further.
I'm also sharing the Workflow ID for reference: ed64ba29-dd2f-4096-aa23-53edc9698a1c in case you'd like to review the setup directly.
Let me know if you need anything else!
v
Vapi Support Bot
05/23/2025, 8:19 AMSuggestion: Try enabling the "run in the background" (async) mode for your API Request node. This can help prevent the workflow from getting stuck if the webhook is slow to respond or intermittently unavailable.
To enable async mode:
- In your API Request node configuration, toggle the Mode option to "run in the background".
This allows the workflow to proceed without waiting for the API response, which may resolve the issue with stuck calls.
[See API Request Node documentation for details](https://docs.vapi.ai/workflows/nodes/api-request).
Sources:
- [API Request Node Documentation](https://docs.vapi.ai/workflows/nodes/api-request)
- [Changelog: API Request Node, Improved Retries, and Enhanced Message Controls](https://docs.vapi.ai/changelog/2025/2/1)
j
Jmallia
05/23/2025, 8:20 AMI tried this but it still didn't work
v
Vapi Support Bot
05/23/2025, 8:22 AMThank you for your detailed updates. Since async mode did not resolve the issue and your configuration appears correct, could you let us know if there are any error logs or messages visible in the workflow or call logs when the API Request node gets stuck? This information would help us pinpoint the root cause.
Reference: [API Request Node Documentation](https://docs.vapi.ai/workflows/nodes/api-request)
Sources:
- [API Request Node Documentation](https://docs.vapi.ai/workflows/nodes/api-request)
- [Changelog: API Request Node, Improved Retries, and Enhanced Message Controls](https://docs.vapi.ai/changelog/2025/2/1)
j
Jmallia
05/23/2025, 8:31 AMYes in the call log details there are some messages in the logs tab. However in the workflow I am not seeing any messages
v
Vapi Support Bot
05/23/2025, 8:33 AMNext step:
Since error messages appear in your call logs but not in the workflow logs, please copy and share the exact error message(s) from the call log's "logs" tab. This will help support identify the root cause and provide a targeted fix.
Tip: You can find these logs in the call details section of your Vapi dashboard.
Reference: [API Request Node Documentation](https://docs.vapi.ai/workflows/nodes/api-request)
Sources:
- [API Request Node Documentation](https://docs.vapi.ai/workflows/nodes/api-request)
- [Changelog: API Request Node, Improved Retries, and Enhanced Message Controls](https://docs.vapi.ai/changelog/2025/2/1)
j
Jmallia
05/23/2025, 8:35 AMHere are the logs from the call log details. Can you guide where I can find workflow logs?
https://cdn.discordapp.com/attachments/1375154703079440435/1375391669997797487/message.txt?ex=683184cf&is=6830334f&hm=00c233bfde922551de84e27d83460232d20d11a649cc0acf24ee7bc7dd531f1f&
c
Chiranjeet Mishra
05/24/2025, 1:21 AMI am reviewing your call id and looks like the info you gave it wasn't passed to any API nodes. Would you mind copying your workflow code and sending it here in this thread? On your workflow page next to the call button is the code button. Paste it here and we will look at it
c
Chiranjeet Mishra
05/26/2025, 11:35 AMlooking into it.
Chiranjeet Mishra
05/26/2025, 12:08 PMFrom your call started logs, I can see that the edge from conversation_1747818774651 to apiRequest_1747818524128 has this configuration:
Copy code
{
"from": "conversation_1747818774651",
"to": "apiRequest_1747818524128",
"condition": {
"type": "ai",
"prompt": ""
}
}Chiranjeet Mishra
05/26/2025, 12:09 PMTo fix this you need to set the AI condition prompt to:
after the hold message is completealways proceed to API requestj
Jmallia
05/26/2025, 8:18 PMCan you guide me on what needs to be done exactly please?
c
Chiranjeet Mishra
05/27/2025, 1:13 AMClick on the condition node between the Conversation and API request node, then in the empty prompt paste in:
Copy code
always proceed to API request3 Views