The app calls the API and MCP surface while it’s still in Beta — see API overview.
Currently a private Make app, not yet listed in Make’s App Directory — accept the invite link to connect it. No approval needed on your end; searching for “IO Tools” inside Make itself won’t find it yet.
Install
Accept the invite, then add IO Tools to a scenario like any other app — it’ll show up in the module picker from then on.Credentials
Add an iotools.cloud API Key connection:Modules
One connection, six modules:Run Tool
- Tool — a searchable dropdown populated from the catalog.
- The fields below it are populated dynamically from the selected tool’s input schema. Each one’s help text carries the property’s own description, an enum’s valid values listed inline, and a link to the tool’s full API reference page. Every field is text, number or boolean — an enum still has to be typed rather than picked from a dropdown, and an array or file input needs the JSON override below instead.
- Additional Fields (JSON) — fill this in to send an exact JSON body instead of the fields above, replacing them entirely rather than merging on top — for a value the fields above can’t represent well.
- Simplify Output — on by default, returns just the tool’s
outputs; off returns the full response envelope (tool,tool_version,outputs,credits_used,credits_remaining). - Allow Running Once Per Bundle? — off by default, and Run Tool refuses to execute at all until answered Yes. Run Tool runs once per incoming bundle, so chaining Find Tool or an Iterator into it (one bundle per tool) fires one paid call per bundle — this exists so that never happens by accident. Test with a single bundle first, then answer Yes once the bundle count is intentional.
detail (falling back to the category title).