Workflows

A Workflow connects a Trigger to one or more steps that run when the trigger fires. You build workflows on a visual canvas, connecting nodes to define what happens, in what order, and under what conditions.

What a workflow contains

A workflow is a graph of connected nodes:

Trigger node — The single starting point: the event or schedule that begins the run.
Step nodes — The actions that run after the trigger, such as posting a Slack message, creating a Jira issue, or sending an email.
Condition nodes — Optional branches that compare a field and route the flow down a true or false path. Supported comparisons are equals, not equals, contains, greater than, and less than.

Nodes are joined by edges that define execution order; condition edges carry the branch (true or false) they apply to.

Building a workflow

On the Automations page, click New Workflow.
Start from scratch, or pick a predefined template as a starting point.
On the canvas, set the trigger, add step and condition nodes, and connect them.
Name the workflow and save it.

Templates

Templates give you a pre-wired trigger and step to start from. Available templates include:

| Template | Flow | |----------|------| | Get an email when a form is submitted | Form submitted → Send an email | | Thank customers who pay an invoice | Invoice paid → Send an email | | Welcome new site members | Visitor signs up → Send a welcome email | | Notify team for failed payments | Payment failed → Post a Slack message | | Create a Jira ticket for new leads | Lead created → Create a Jira issue |

Running a workflow

Workflows run automatically whenever their trigger fires. You can also open a saved workflow and click Run Now to run it on demand.

A workflow can be active or inactive — toggle it from the workflows table without deleting it. Inactive workflows do not run when their trigger fires.

Concurrency

When a new run starts while a previous run of the same workflow is still going, the workflow’s concurrency setting decides what happens: skip the new run, queue it to run after the current one, or replace the running one. The default is to skip.

Run history

Every workflow keeps a run history. Open a workflow to see its runs in a two-pane view: pick a run on the left to inspect it on the right. Each run shows:

Status — running, completed, failed, stopped, or pending.
Timing — when it started, when it finished, and total duration.
Trigger data — the data the trigger passed into the run.
Per-step results — each step’s status (in progress, completed, failed, skipped, or stopped), its output, any error, and how long it took.