Conditions & Delays

Conditions & Delays

What Are Conditions?

Condition nodes add branching logic to your workflow. Each condition evaluates a check and produces two outputs: Yes (condition is true) and No (condition is false). Connect different actions to each output to create decision trees.

Document Conditions

• Check Status — Is the document in a specific status? Choose from: draft, sent, viewed, signed, paid, void, or cancelled.
• Check Type — Is the document a specific type? Choose from: invoice, quote, contract, or proposal.
• Is Paid? — Has the document been fully paid?
• Signatures Complete? — Have all required signatures been collected?
• Check Amount — Compare the document amount using operators: greater than, less than, greater than or equal, less than or equal, or equal to a specified value.
• Check Days — Compare the number of days since a date (e.g., days since sent) using the same operators.
• Has Line Items? — Does the document have at least one line item?
• Is Overdue? — Has the document passed its due date without full payment?

Contact Conditions

• Check Contact Field — Check any field on the contact. Operators: equals, not equals, contains, is empty, is not empty.

Tag Conditions

• Has Specific Tag — Does the contact or record have a particular tag?
• Has Any Tag — Does the contact or record have at least one tag from a specified list?
• Has All Tags — Does the contact or record have every tag from a specified list?
• Has Tag in Group — Does the contact or record have any tag from a specified tag group?

Scheduler/Booking Conditions

• Check Booking Status — Is the booking in a specific status (pending, confirmed, cancelled, etc.)?
• Check Booking Field — Check a custom field value on the booking form data.
• Booking Created By — Was the booking created by a guest (public page) or by an admin (internal)?
• Check Scheduler — Does the booking belong to a specific scheduler?
• Booking Location Type — Is the meeting location a specific type (in-person, phone, Google Meet, Zoom, etc.)?
• Has Additional Guests — Did the guest add extra attendees to the booking?

Logic Conditions

• Random Split — Randomly route a percentage of runs down the “Yes” path. Use this for A/B testing workflows (e.g., 50% of new leads get email template A, 50% get template B).

Delay Nodes

Delay nodes pause the automation for a specified duration before continuing to the next step:

• Wait Days — Pause for a number of days (e.g., wait 3 days before sending a follow-up email).
• Wait Hours — Pause for a number of hours.
• Wait Until — Pause until a specific time or date.

While waiting, the automation run is saved in a “waiting” state. When the wait time elapses, execution automatically resumes from where it left off.

Building Decision Trees

Chain conditions together for complex logic. For example:

1. Trigger: Payment Received
2. Condition: Check Amount > $5,000 → Yes: Notify account manager → No: continue
3. Condition: Has Tag “VIP”? → Yes: Send personalised thank-you email → No: Send standard receipt
4. Delay: Wait 7 days
5. Action: Send follow-up email asking for a review