watsonx Orchestrate

 View Only

 Cannot use OPENAPI tools inside workflows

Antonio Brau's profile image
Antonio Brau posted Tue February 10, 2026 11:54 AM

Hi everyone, I’m trying to use an OpenAPI tool inside an ADK workflow, but I can’t get input mapping to work.

The tool node runs, but it always calls the endpoint with empty query parameters, so I consistently get a 422 response.

In the docs I found that the tool node supports an input_map field, but in the ADK implementation I’m using I can’t find input_map anywhere (the aflow.tool(...) signature also doesn’t show it). So I’m not sure if the docs are outdated, or if I’m using the wrong API.

What I tried:

  • I attempted to map the tool inputs in different ways (example in the screenshot), but none of the mappings seem to be applied.

  • From orchestrate tools list -v, it looks like the tool input variables are exposed as query_{query_parameter}. I also tried mapping using that naming convention, with no results.

At this point it feels like the tool node is not picking up any input schema to validate/bind, so the query params stay empty no matter what I do. Has anyone run into the same issue, or knows the correct way to map workflow inputs into an OpenAPI tool in ADK?

Screenshots attached.

Am I missing something? Any help would be appreciated.



Enrico Nello's profile image
Enrico Nello posted Wed February 11, 2026 09:12 AM

+1

Same here, i'm struggling too when it comes to make openAPI tool working inside workflows... it seems to miss the input params 

Laurent de Clermont-Tonnerre's profile image
Laurent de Clermont-Tonnerre posted Thu February 12, 2026 02:20 PM

Hi can you share the specs causing the issue so we can take a look?

It should work, one of the ADK examples uses OpenAPI.
james colin's profile image
james colin posted Fri February 13, 2026 04:52 PM

It looks like the workflow isn’t passing inputs to the OpenAPI tool, which is why the requests are empty. This often happens if the tool’s input schema isn’t detected or if your ADK version doesn’t support an input map.

Make sure the tool is registered correctly and that the input names in your OpenAPI spec exactly match what the workflow expects. If the problem continues, try testing with a simple OpenAPI spec to isolate whether the issue is with the spec or the workflow configuration.

Related Content