GuideAccelerate plan

Add delays and conditions

Pause a workflow with Wait/Delay and branch it with Conditional Split, using the builder or an expression.

4 min readRole: Super Administrator or higherAutomationsUpdated October 25, 2026
Open in the app

Wait/Delay pauses a workflow before the next step, for example to ask for a review 30 minutes after a visit. Conditional Split checks something and sends the workflow down one of two paths, for example only messaging clients who have an email address.

Wait/Delay is available on every plan. Conditional Split needs the Accelerate plan or higher.

Before you start

Add a delay

  1. 1

    Step 1 of 2

    Add a Wait/Delay step

    Click Add next step where the pause should happen, or use Add Node, and choose Wait/Delay.

  2. 2

    Step 2 of 2

    Choose the duration

    Click the step and pick a Duration. The options go from 5 minutes up to 24 hours. Click Save, then Save at the top of the editor.

    You will see:

    The step reads Wait/Delay with the number of minutes it waits.

Things to know about waits:

  • A run that is waiting shows as Running in History.
  • The wait doesn't recheck anything. If an appointment is canceled during the wait, the next steps still run, unless you add a Conditional Split after the wait. Note that the condition checks the values from when the run started, not the current ones.
  • Saving changes to the steps, or turning the workflow off, cancels runs that are waiting.
  • To wait longer than 24 hours, chain several Wait/Delay steps.
  • After a wait, a person can get another message on an address that already got one earlier in the run. See The Send Notification step explained.

Add a condition

  1. 1

    Step 1 of 4

    Add a Conditional Split step

    Click Add next step and choose Conditional Split. If it asks you to upgrade, your plan doesn't include it.

  2. 2

    Step 2 of 4

    Build the condition

    Click the step to open Update Conditional Node. On the Builder tab:

    1. Under Match, choose All conditions or Any condition.
    2. Click Add condition.
    3. Pick a variable, an operator and a value. For example: appointment status is Confirmed.

    Statuses of appointments and invoices show a list to pick from. You can add more conditions and remove one with Remove condition.

    Click Save.

  3. 3

    Step 3 of 4

    Fill both paths

    The step now shows Add step (If true) and Add step (If false). Add the steps for each path. Every path needs to end with End Workflow, even if one path does nothing else.

  4. 4

    Step 4 of 4

    Save the workflow

    Click Save at the top of the editor.

Operators

Variable typeOperators
Text, email and phoneis, is not, contains, does not contain, starts with, ends with, is empty, is not empty
Numberis, is not, is greater than, is at least, is less than, is at most, is empty, is not empty
Yes or nois true, is false
Status listsis, is not, is one of, is not one of, is empty, is not empty

Write an expression instead

For conditions the builder can't express, open the Expression tab and write one expression between double curly braces. For example, {{ $event.data.object.status === "confirmed" && !!$event.data.object.client.emailAddress }} is true for confirmed appointments whose client has an email address.

How the result is read:

  • false, no, empty text and missing values count as false.
  • Everything else counts as true, including true, yes, any other text and any number, even 0.

To test a number, compare it inside the expression, for example {{ $event.data.object.totalDue > 0 }} on an invoice trigger.

Keep the whole condition inside one pair of braces. In {{ $event.data.object.status }} === "confirmed", the comparison sits outside the braces, so the result is plain text, and plain text always counts as true.

If you write an expression the builder can't show, the Builder tab tells you so. Keep editing on the Expression tab, or click Start over in builder.

Common questions

No. A wait is always a fixed length from when the run reaches it.