Workflow Subagents and Tools

Subagent nodes change how the Agent handles one part of a Workflow. Tool nodes perform required external actions and route from their combined result.

Configure a Subagent#

Give the Subagent a label and optional additional prompt. It may override the model and temperature, add knowledge documents, and add Tools. Overrides are merged onto the base Agent configuration; additional resource IDs are combined without duplicates rather than replacing the base list.

Choose an entry behavior: Auto, Generate immediately, or Wait for user. Wait for user pauses when the node is entered without a new customer signal. Generate immediately produces a response on entry. Auto follows the runtime's normal signal-aware behavior. Enable Prevent subagent loops when the same Subagent must not be entered twice while processing one customer message.

Configure a Tool node#

A Tool node can contain up to 10 Tools. Operade prepares each call, runs the Tools in parallel, then records results in configuration order. A Tool with no parameters skips argument-generation LLM work. A Tool with parameters uses a forced model call for its arguments.

The node succeeds only when every Tool succeeds. Use Result edges for “all succeeded” and “at least one failed.” An ordinary webhook failure does not cancel its siblings, while an internal execution error fails the Workflow.

Assignments belong to the webhook Tool, not the Workflow Tool node. The node can execute a Tool that has assignments, and later Workflow expressions can read those resulting variables.

Verify resources#

Draft readiness checks missing Tools and knowledge documents, and runtime checks Tools again before execution. Test both Result branches and confirm external side effects happened once. See Tool runtime and Workflow runtime troubleshooting.