A workflow is a sequence of customizable steps (actions) that are initiated by a trigger. Typically, the actions are executed in sequence. Workflows can carry data between each action step, enabling the workflow to build upon itself as it runs.
Workflows are highly flexible tools that can streamline a wide variety of processes:
- Automating simple actions - Such as, “if this happens, then do that.”
- Running ordered sequences - Where steps are completed in a specific order.
- Coordinating complex processes - Involving advanced logic and multiple conditions.
- Scheduling recurring tasks - That run automatically at set times.
- Integrating systems - To connect data and actions across different platforms.
Workflows are especially helpful when you need to coordinate multiple actions that run together or in sequence, or when one or more actions must be triggered on a schedule or through a webhook.
Workflow terminology
Review the following terminology related to Workflows:
- Workflow Definition (sometimes just Workflow) - The trigger, actions, and other settings that comprise a workflow.
- Workflow Run (sometimes just Run) - An invocation of a workflow definition, caused by the workflow’s trigger firing.
- Trigger - The way in which a workflow run is started.
- Action (sometimes Step) - An individual building block of a workflow, usually part of a sequence of actions or steps.
- Input (sometimes Output or Data Pipeline) - The input of an action is the data that the action will utilize. This input is always the output of the previous action or trigger that ran. For additional information, refer to our Data Pipeline Overview.
- Template (sometimes Expression or Function) - A way to reference data dynamically from the input of the current action, or produce other dynamic data such as the current date/time. Refer to the Template Engine page for documentation and examples regarding the template syntax.
Workflow states
A workflow can be in one of the following states:
| State | Can be run/triggered? | Can be edited? | Counts towards license? |
|---|---|---|---|
| Active |
Yes |
Yes |
Yes |
| Disabled |
No |
Yes |
Yes |
| Archived |
No |
No |
No |
Components of a workflow
The following are components of a workflow.
Trigger
The trigger is what starts the run of a workflow. The trigger may also optionally pass in initial data to the first action of the workflow, depending on the type of trigger.
Currently, the following triggers are supported - click one to view more details about it:
Action
An action is a step in the workflow sequence. Workflows must have at least one action. Actions create, modify, or manipulate data in the workflow, and can also connect to external systems to perform other tasks, retrieve or send data, and more.
Currently, the following actions are supported - click one to view more details about it: