Workflow concepts
This guide documents Workflows as currently exposed in the product UI.
What is a workflow?
A workflow is a visual, node-based way to run one or more AI-powered steps in sequence. You design the workflow in the builder, then run it by providing input parameters (and optionally attachments).
A workflow is made up of:
- Nodes: The building blocks (Input, Task steps, Output, notes).
- Edges: Connections that define the order of execution.
- Tasks: Each Task node represents an execution step.
- Runs: Each time you execute a workflow, you create a workflow run with its own status and outputs.
Where to find workflows
In the app UI, workflows are available at:
- Workflow list:
/workflows-task - Workflow builder:
/workflows-task/<workflow-id>
Core concepts
Input node
The Input node defines:
- Input parameters (the fields you fill in when running)
- A prompt template (a shared template you can use across tasks)
Input parameters are referenced in prompts using placeholders like:
{{customer_name}}{{ticket_id}}
Task nodes
A Task node is a single step in the workflow. It typically includes a prompt where you can reference input parameters.
When tasks are connected, the workflow executes them in order (from the first task after Input through to Output).
Output node
The Output node marks the end of the workflow path. Connecting your last task to Output makes it clear where the workflow finishes.
Runs, status, and results
When you run a workflow:
- A workflow run is created
- The run gets a status:
RUNNING,COMPLETED, orFAILED - The run stores:
- the input parameters you provided
- any attachments
- the final response
- per-task prompts and outputs
Variables & templating
Use {{name}} placeholders in prompts.
Tips:
- Variable names must match the input parameter name exactly.
- Renaming an input parameter updates references in the Input node’s prompt template.
What is not currently exposed in the workflows UI
Some workflow concepts may exist elsewhere in the platform, but are not exposed in the current workflows UI, including:
- Scheduling / cron-based runs
- Event-based triggers
- Real-time run progress streaming via SSE in the workflow run UI