run_workflow tool. The LLM decides when to call the tool and maps user intent to workflow_name and input; your orchestration engine runs the steps in order, retries on failure, and returns a structured result.
Source: examples/agent_with_workflows/
What it demonstrates
- Deterministic workflow execution — steps defined in your engine, not improvised by the LLM
WorkflowTool+WorkflowRunnerinterface — pluggable engine (in-process, Temporal, Conductor, Argo, etc.)- Agent waits until the workflow finishes —
Executeblocks onWorkflowRunner.Run - Long-running config —
AgentModeAutonomous,WithTimeout,WithToolExecutionConfigsized for workflow duration
Run
Fromexamples/:
In-process runner — no infrastructure needed:
LLM_APIKEY in examples/.env.
Key code
Execute blocks on WorkflowRunner.Run — the agent run stays open until the workflow finishes or a timeout fires.
Expected output
Learn more
Deterministic Execution
What deterministic means, wait semantics, timeouts, orchestration runners
Execution config
Tool execute timeout and max attempts