Skip to main content
A workflow runs several steps in order and passes data from one to the next. For example: run a skill that lists competitor prices, keep only the ones below your price, then post them to Slack.

​
Steps

​
Inputs

Every workflow starts with an API trigger. It lists the workflow’s inputs, each with a name, a type, and an optional default. Steps use an input by writing {{inputs.<name>}}. Scheduled runs use the defaults. The inputs are the workflow’s contract, just like a skill’s. Callers and AI assistants read it to know what to send.

​
Passing data between steps

Any step setting can use the output of an earlier step: When a whole setting is a single reference, the value keeps its type, so {{inputs.limit}} in Max results becomes the number 3. Inside longer text it is pasted in as text.

​
What a workflow returns

A workflow run returns the rows of its last step as outputs. If several steps end the workflow, outputs has one set of rows per final step, keyed by step name. Each step’s own status and row count are in the run too. See Runs.

​
Ways to start a workflow

The same ways as a skill: the Run button, the API, an AI assistant (each workflow is a tool named workflow_<slug>), or a schedule. See Build a workflow.

​
Cost

A workflow run is charged a base fee or the sum of its steps’ costs, whichever is higher, never both. Skill, agent, and code steps use credits. HTTP and transform steps do not. See Credits.