When to use SuperFlow
A single Lyzr agent handles tasks that fit one model with a set of tools. SuperFlow is the right choice when:- The workflow involves multiple steps that are not all LLM calls, for example: fetch from an API, run an agent, branch on the result, call another agent.
- The flow requires branching or looping based on data (if/else, case switching, iterate over a list).
- A human needs to approve something mid-flow before the workflow continues.
- You want to schedule the workflow to run on a cron (every Monday morning, every 5 minutes, and similar schedules).
- You are composing several agents together, such as a researcher feeding a writer feeding an editor.
Mental model
A SuperFlow is a graph of nodes connected by edges:- Every node has inputs and outputs, and data flows along the edges as JSON.
- Each node receives the output of the nodes upstream of it, does its job, and emits its own output downstream.
- A SuperFlow always starts with one Trigger node, which defines what input the workflow accepts.
- Downstream nodes can reference any upstream node’s output using expressions like
{{ $('Trigger').json.email }}.
The SuperFlow editor
A new SuperFlow opens with a Trigger node already on the canvas. The SuperFlow editor has three areas. The node library on the left lists every node you can add, the canvas in the middle holds the flow, and the Build with AI panel on the right lets you create or change the flow by describing it.
Node library
The node library groups nodes by category, such as AI, Safety, Control Flow, Data, and Apps. Select a category tab to browse its nodes, or type in Search nodes to find a node by name. To add a node, drag it onto the canvas or double-click it. See Node types for the nodes in each category, and the node reference for how each node works.Build with AI
Build with AI creates a flow from a plain-language description. It designs the flow from SuperFlow’s nodes, draws each node on the canvas as it goes, and adds a plain-language summary of what the flow does. You can start a flow this way and then refine it by hand, or keep working in the chat. To build a flow with AI:- In the Build with AI panel, describe what the flow should do in a sentence or a paragraph. For example, “Read prospects from a Google Sheet, research each one, draft an outreach email, and hold it for approval before sending.”
- To point the flow at resources you already have, select + and attach an agent, knowledge base, guardrail policy, SuperFlow, or tool for it to use.
- Review the flow on the canvas and read the summary.
- Select Run sample input to test the flow end to end before you deploy it.
- To change the flow, describe the change in the same chat, for example “Add an approval step before the email is sent, and route rejections back to the drafting node.”
Ctrl+Z to undo the last change Build with AI made.
Create an agent from the editor
When a flow needs an agent that does not exist yet, you can build it from the editor and use it in the flow straight away.- Add an AI Agent node to the canvas and open it.
- Under Use Agent, select Create agent. The agent builder opens, with Back to SuperFlow in the top right if you want to return without creating the agent.
- Set up the agent’s role, goal, instructions, model, and any knowledge, tools, skills, or features it needs. The builder works the same way as the Studio Builder.
- Select Create & use. SuperFlow creates the agent and uses it in the AI Agent node.
Built for production workloads
Durable execution. Every meaningful step (LLM call, tool call, HTTP request, code execution, loop iteration) is journaled to durable storage before completion. A service restart in the middle of a 50-step workflow resumes from the exact point of failure, not from the beginning. Exactly-once side effects. A step that has already run successfully will never run again. No double charges, no duplicate emails, no re-fired API calls on retry. Once the journal records a step as completed, the engine treats it as final.- Durable execution. Every meaningful step (LLM call, tool call, HTTP request, code execution, loop iteration) is journaled to durable storage before completion. A service restart in the middle of a 50-step workflow resumes from the exact point of failure, not from the beginning.
- Exactly-once side effects. A step that has already run successfully will never run again. No double charges, no duplicate emails, no re-fired API calls on retry. Once the journal says “this step completed,” the engine treats that as final.
- Pauses are free. A SuperFlow waiting on a human approval, a schedule, or a delay consumes essentially no resources. Runs can wait hours, days, or weeks and resume exactly where they paused.
- Crash-safe schedules. Cron triggers use durable timers, not in-memory schedulers. A schedule won’t “miss a tick” because the runtime was down.
- Per-node retries with exponential backoff. Configure every node that talks to an external system to retry on transient failures. Retries are themselves durable: the retry count survives restarts.
- Error edges for graceful failure. When retries are exhausted, opt into an error output that routes failures to a recovery path (a fallback API, a Wait for Approval for human escalation, or a notification) instead of failing the whole run. Strictly opt-in per node.
- Live and historical observability. Watch a run in real time on the canvas; replay every past run with full per-node outputs preserved. OpenTelemetry traces are emitted end-to-end.
Triggers
Every SuperFlow starts with a Trigger node. Four modes are available:
Webhook example:
Expressions
Downstream nodes reference upstream outputs using expressions. All expressions use the{{ }} syntax:
Full JavaScript is valid inside
{{ }}, including ternary operators, array methods, and string operations. Use the field reference picker (plug icon) to build expressions without typing paths manually.
Node types
Nodes are organized in a palette by category:AI
Apps
Control Flow
Safety
I/O and Compute
Data Transform
Human-in-the-Loop
Document
Utility
Running and monitoring
During execution, the canvas shows real-time node status:- Amber pulse: currently executing
- Green check: completed successfully
- Red cross: errored
- Blue pause: awaiting human approval
- Pause: cooperative pause at node boundaries
- Resume: continues from the stopping point
- Terminate: cancels the run permanently