Workflow concepts and use cases
Understand definitions, nodes, runs, approvals, and Work Packs.
| Term | What it controls |
|---|---|
| Workflow | The saved definition of steps, edges, input mappings, and policies. Activate a draft to make it runnable. |
| Node | A step such as a capability call, a data transform, a branch, an approval, or a delivery. A canvas note documents the flow. |
| Run | One execution against a saved definition snapshot, with its own project, inputs, status, and step records. |
| Approval | A decision recorded for a specific run and step. An explicit gate or the policy of a capability can pause execution before an action. |
| Work Pack | A reusable package that can carry a workflow, intake fields, connection or role requirements, and delivery expectations. |
Use a workflow when the work recurs and you can describe the input, sequence, output, and review points. For example, a recurring research brief can take a question and an indexed source set, collect citations, and return a draft for review. Start exploratory work in Chat until you know which inputs and outputs are stable.
Follow one result through the workspace
A flow in Flow Library can have several runs with different inputs. Open Runs & Approvals to find the run that matches your project and timestamp. Inspect its definition snapshot, the node with the latest meaningful status, and any approval or artifact tied to that run. Changes to the canvas apply to later runs after you save and activate the updated definition.
When other people need the same setup, document the intake fields and result, then use a Work Pack to carry that setup. Review the recipient’s project, role permissions, model, and connection bindings again after installation.
Continue with node selection or runs and approvals.