Workflows

Workflows chain AI calls, data transformations, API requests and human review steps into automated pipelines, without writing code. You design a workflow once and it runs on a schedule, on a webhook call, on a form submission, on an event in a connected service, or when you start it yourself.

Workflows is a product of its own. Open it from the product switcher. You need a role with the permission to read workflows; your administrator sets this under roles.

Core Concepts

Concept	Description
Trigger	What starts the workflow: manual, scheduled, webhook, form, an integration event, or a call from another workflow
Node	A single step: an AI agent, a code block, an HTTP request, a condition, a loop, a data table operation or an integration action
Edge	A connection between two nodes. Data produced by one node flows along edges to the next
Version	A deployed state of the workflow. Triggers only fire once a version has been deployed
Run	One execution from trigger to completion, with its own log, status and cost
Approval	A switch on a node that pauses the run until a person approves or rejects that step
Data Table	Persistent tabular storage that workflows read from and write to across runs
Subworkflow	A deployed workflow that other workflows call like a function

When to Use Workflows

Workflows fit when you need to:

Run the same AI task again and again on new input, such as new emails, form submissions or a daily data pull
Chain several AI calls, where one step's output feeds the next
Combine AI with external systems: read issues from Jira, process them with an AI agent, post the result to Slack
Have a person confirm a step before it takes effect

For one-off or conversational tasks, use Chat instead.

How a Workflow Executes

Trigger fires: a form is submitted, a schedule is due, a webhook receives a request, an integration reports an event, or you click Run test

Nodes execute in order: each node runs when its incoming edges have data. Conditions and loops decide which path runs

Data flows forward: every node exposes named outputs. Downstream nodes reference them as {{nodeName.outputs.fieldName}}, or you insert them from the Variables panel

Run completes: the history shows the status, duration and cost of every node. Failed nodes show their error

Group	Entries
Workflows	Overview, Statistics, Approvals, Templates, and Budgets & limits (only with permission to manage billing)
Data & Integrations	Data Tables, External Integrations (opens the integrations page in your settings), Secret Stores
Users	All Users (only with permission to read users)