My API requests in my workflow no longer work. They were working fine 2 days ago, but since then it gets stuck on the "Tool" function in my workflow and never processes or moves past it. Additionally, when I create an API request in my workflow instead of using a tool, it doesn't save my body properties. If I add properties in the API request and click save, it ends up empty after refreshing.

Thanks for reporting this issue. Based on recent updates, the

HttpRequest

node is now deprecated and replaced by the

ApiRequest

node, which may affect workflows if not updated. Could you confirm if your workflow is still using the old

HttpRequest

node, or have you already migrated to the new

ApiRequest

node? This will help narrow down the cause of the problem. Sources: - [Changelog: API Request Node, Improved Retries, and Enhanced Message Controls (2025-02-01)](https://docs.vapi.ai/changelog/2025/2/1) - [API Request Node Documentation](https://docs.vapi.ai/workflows/nodes/api-request)

Maybe this is related: yesterday I could not get any function - posting to webhook - working from within the workflow. The assistant itself - w/o workflow- triggered them flawlessly. Not sure about today have not tried yet

Interesting, thanks for sharing! So do you have the assistant linked to the workflow and trigger it that way? Or is there way to add API requests to the assistant without a workflow?

No I have the assistant (old) on phone line 1, the workflow (new) on another phone line. I started re-doing the whole assistant in a workflow for fine tuning purposes. They are separate from each other. The workflow worked fine til the day before yesterday and w/o me changing anything the function calls in my workflow that call a webhook do not work anymore , just like that and all of a sudden. The exact same function works 100% of the time when the "old" assistant triggers them. So it is not the function, it is some issue within Workflows...

Hey! 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!