Credential missing with AI agent and HTTP node as a tool

You're correct. This approach isn't ideal. However, I managed to resolve the issue with numerous different requests by establishing a variable. This variable receives the request type from the agent tool. Subsequently, a switch statement is employed to determine which endpoint to invoke. While this is a less-than-perfect solution, it was the only way I could find to address the problem.

Hi there, any updates on this? ... Many thanks.

I could handle this issue using the subworkflow tool and executing the standard HTTP node with the request within it.

Hello everyone, we are currently developing an updated version of the HTTP Request Tool. This process is taking some time. However, there is a workaround available, although it's a bit indirect. If you encounter this problem, please utilize the subworkflow tool along with a standard HTTP Request Node until we resolve the issue.

Thanks for the update. Do you have an estimated release date?