Overview of workflows
A workflow describes what should happen when a record changes, someone starts it manually, or a scheduled time arrives. You connect steps to create Tasks, work with records, make decisions, or wait for a person or a deadline.
For example, a newly created service request can create a linked follow-up Task. A more involved workflow can ask for approval, wait for the answer, and create different Tasks depending on the decision.
The building blocksโ
| Term | Meaning |
|---|---|
| Trigger | The event or schedule that starts a run. A published workflow has exactly one trigger. |
| Step | One action, such as creating a Task or waiting for an answer. |
| Connection | Determines which step follows, including the outcome of a decision. Moving a step on the canvas does not itself change execution order. |
| Run | One execution with its own input, progress and results. A run can remain active while waiting. |
| Version | A saved definition of the workflow. Published versions are fixed; new changes are made in a draft. |
Steps execute sequentially along the selected path. Branches can converge through a Join. Workflows currently support up to 20 action steps, without loops or parallel execution.
Choose the right kind of stepโ
Use the built-in Task, record and logic steps for operations you can configure directly. Use a Script for a calculation or custom procedure. Use an Agent when the work needs model interpretation, such as classifying a description. Agents return validated results that later steps can use.
From draft to executionโ
Save keeps your work, including incomplete configuration. Preview evaluates what it can without creating a run or changing data. Publish makes a valid version available for execution; the first publication also enables the workflow. A matching trigger then starts a run.
Each run keeps the exact publication, dependencies and input captured when it started. Later edits do not change that run. Pausing stops new runs, while existing runs continue.
Start with Build your first workflow. Then explore triggers, data mappings, publishing and run monitoring. For complete examples, see Workflow recipes.
Find a guideโ
| Build | Operate |
|---|---|
| Triggers and Schedules | Drafts and publishing |
| Data and Logic | Monitoring runs |
| Tasks and Human questions | Troubleshooting |
| Record actions | Permissions and limits |
| Scripts and Agents | Recipes |