DashboardSign inStart your trial

In this guide · BuildClose guide

Control the Flow

Use conditions, loops, delays, and branch controls to decide what a workflow does next.

Control steps shape the work between its start and its final action. Use them to choose a path, repeat work for a list of items, wait for the right moment, or bring parallel paths back together. Workflow logic is free.

#Condition

Use a Condition when the next step depends on information in the workflow. For example, send a high-value lead for approval, route an unverified email to review, or skip records that are missing an email address.

Each branch checks a value with a rule such as equals, contains, greater than, or is empty. Combine rules with and or or when more than one thing must be true.

#Loop

Use a Loop to repeat part of a workflow for every item in a list. For example, draft one follow-up for each lead returned from a table, or process each attachment in an email.

Put the steps that should repeat inside the loop. Each pass has the current item available in the variable picker.

#Delay

Use a Delay when a workflow should wait before it continues. You can wait for a length of time, until a specific time, or until a value resolves. Delays are useful for follow-ups, cooling-off periods, and time-based handoffs.

A workflow waiting in a delay does not use credits.

#Human Review

Use Human Review when a person should approve, reject, edit, or provide input before the workflow continues. It is the right control step before a consequential action, such as sending an outbound email or changing a customer record.

See Approvals to choose a review type, assign reviewers, and set confidence-based review behavior.

#Bring branches back together

After a workflow splits into branches, use one of these controls to decide when to continue:

  • Any (First): continue when the first branch finishes. You can cancel the remaining branches if they are no longer needed.
  • All (Wait): continue only after every branch finishes. Choose whether one failure should stop the workflow, be collected for review, or be allowed when enough branches succeed.

#See also