A workflow column stores a workflow output for each row. Configure a workflow group to map row values to inputs and select one or more output columns. Run rows manually, or enable Auto-run workflow to process new and changed rows.
What you will learn
Attach, bind, run
Configure the workflow, map input columns, and select its output columns. One row run can fill several output columns.
Stages cascade
A workflow group can read outputs from another group. Enable auto-run and configure Run after dependencies to process the stages in order.
Every cell is a run
Every value was produced by a real run, and the cell remembers it. Open a cell's menu to view the execution behind it: every block as a span, with timing and cost.
Errors explain themselves
A failed row says so in the cell. Its trace shows exactly which block failed and why, and re-running the cell runs the workflow again for just that row.
Configure a workflow group
Select the workflow, map row values to its inputs, and choose the columns that receive its outputs. A single row run can write several columns. If a later group depends on those outputs, configure Run after and enable Auto-run workflow for the stages that should run automatically.
Watching it run
Run a single row and the cell reports the run as it moves, queued, then running, then the value. Turn on auto-run and the whole column fills in a cascade; type a new company into a blank row and the pipeline runs it end to end, the domain first, then the score, without a single click.
Every cell records its run
Take one value: a lead score of 75. The cell remembers the run that wrote it: open its menu and view the execution, a real trace where every block is a span, with its timing and cost. Output cells from the same workflow group can share a row run. When a row fails, the cell says so, its trace shows which block failed and why, and re-running the cell re-runs the workflow for just that row.