Run tools from a workflow

Requirements

The tool must be active and authorized for at least one agent assigned to the workflow. Validate the process again if authorization is removed or the tool changes.

Configure the node

Add a Tool node, select an authorized action, and define its JSON inputs. Use only fields accepted by the tool contract.

Never place passwords, tokens, or secret headers in the workflow. Credentials belong in protected tool configuration.

Handle results

Connect the node to steps that interpret its output. Provide an error route when the tool depends on an external API, variable data, or rate limits.

A successful HTTP response does not always mean the business operation succeeded. Check relevant output fields before confirming it to the user.

Test without causing changes

Begin with a simulation and mocked tools. Verify arguments and routing without creating records, sending messages, or changing external systems.

For a real test, use controlled data, avoid repeating non-idempotent actions, inspect the target system, and review node output.

Repeating a run can repeat its external effect. Do not use testing as a retry mechanism without understanding the tool contract.

Apply least privilege

Authorize only required tools. Do not expand access merely to make validation pass; verify which assigned agent should execute the process.