Planning a workflow
Create a workflow from a plain-language goal, review the proposed pipeline on the canvas, and save it.
The console creates workflows from a goal: you describe what you want to happen, and the planner proposes a pipeline of agents from your workspace. The proposal lands on an editable canvas, so you always review — and can fully rework — the plan before saving.
Open Build → Workflows and click Create workflow. The screen has three parts: the goal prompt, the pipeline canvas, and the name/schedule form.
Select a workspace from the Build picker first. The planner only composes agents from the selected workspace, and the saved workflow belongs to it.
Describe your goal
Type a goal in plain language — for example, "Summarize new support tickets and draft replies" — and click Generate workflow. The planner looks at the agents available in your workspace and returns a proposed pipeline: which agents to call, in what order, and how each step's message is wired to user inputs and to previous steps' outputs.
Two outcomes are possible:
- A pipeline is generated — the proposed nodes appear on the canvas below, ready to edit.
- No pipeline could be generated — the planner returns a message explaining why (for example, no suitable agents exist for the goal). You can refine the goal and try again, or build the pipeline manually on the canvas.
If the planner backend is unreachable, the screen tells you so and manual building still works — goal planning is a convenience, not a requirement.
Edit the pipeline
The canvas is fully editable whether you started from a generated plan or from scratch: add agents, remove nodes, drag to connect, and rewire the order. The agent picker offers the workspace's deployed agents plus any registered external agents (see Agents in workflows).
Each node's message can carry input placeholders that resolve at run time:
$userinput.<key>— a value the person (or schedule) starting the run provides. Every distinct key becomes a required input field on the Run panel.$<nodeId>.<key>— a value from an earlier node's output, which is how data flows from one step to the next.
A node can also carry its message values baked in, in which case the run needs no input for that step.
Name, schedule, and save
Below the canvas, give the workflow a name (required) and optionally a schedule:
- No schedule (manual run) — the workflow only runs when someone starts it.
- Hourly / Daily / Weekly / Monthly — the platform creates a recurring trigger that starts a run automatically (daily/weekly/monthly fire at 09:00 UTC; weekly on Monday, monthly on the 1st).
Click Save workflow. The workflow is created in the active state and the console takes you to its detail page, where you can run it immediately. The schedule can be changed or removed later by updating the workflow.
Saving does not run the workflow. Nothing executes until you start a run or the schedule fires — see Running and monitoring.