"type": "agent") runs an LLM-backed step. It is the only node type with more than one handler class, and handler_class decides the shape of process.
Use this page when building nodes for Create a Workflow or Update a Workflow.
Choosing A Class
An
agent_advanced node cannot be used as a tool by another advanced agent. Only Basic and Custom agents, code utilities and integrations can be referenced in tool_references.agent_basic
You describe what the step should achieve; Opus generates the prompting.See Blueprint below.
agent_basic
agent_custom
You write the prompts verbatim. Opus sends them as given.agent_custom
agent_advanced
A blueprint agent that can call other handlers as tools.See Blueprint below. Identical to the
agent_basic blueprint.agent_advanced
Blueprint
Used byagent_basic and agent_advanced. Four fields are required — the blueprint is what Opus turns into prompts, so an empty description produces a weaker agent.
input_description and output_description describe the step’s input and output as a whole. Per-variable descriptions belong in input_schema and output_schema instead.