Single-step agent workflows vs Advanced mode (canvas editor)

Prefer a workflow with one configurable agent step unless teams need multiple canvas steps, branching, or strict separation of phases. Delegation is always serial—no parallel sub-agents.

Harriet offers a simplified workflow with one configurable agent step, or Advanced mode (canvas editor) for multi-step graphs. The underlying agent capability is the same; canvas adds structure.

Guidance for admins

Default toward single-step when business owners can express the process as one agent with skills, instructions, and optional delegatable skills for sub-agents. Fewer steps mean fewer failure modes and simpler audits.
Use the canvas when you need multiple operations, result routing / branching, or different skill packs per phase (for example lookup vs send vs confirm as distinct steps).
Delegation always runs one sub-agent at a time; the parent pauses until that sub-agent completes. Two independent external conversations happen in series, not in parallel. Set sub-agent timeout and a clear on error path on the main agent.
High volume (very long entity lists in one run) is a poor fit for a single agentic pass: prefer batching, separate runs, or smaller triggers so each execution stays bounded.

For end-user-oriented examples and a fuller comparison, see the HR article When should I use a single-step agent workflow instead of the canvas editor? (same product concepts, HR-focused scenarios).

For field-level settings on agent steps, see How do I configure an agent step in a workflow? Delegation security boundaries are covered in What is the security model for workflow sub-agents?