Skip to content
Esc
navigateopen⌘Jpreview
Book a demo
On this page

Logic and timing

Waits, filters, if/else branches, and delivery windows.

Actions do the work; logic and timing decide who continues and when. These blocks live in the Time and Logic sections of the palette.

Wait

Pauses the contact before the next step. The default is 1 day; set any amount of Days, Hours, Minutes, or Seconds.

Flows with dynamic fields enabled get a second Wait type:

  • Wait for a period of time: the standard relative wait.
  • Wait until a specific date: waits relative to a date on the contact or event: pick the Event date and an Offset (amount, unit, and before/after). This powers “3 days before their membership expires” or “1 hour after their booking” style timing.

A classic follow-up sequence is just messages separated by waits:

Trigger: Added to list "New leads"
→ Send text (welcome)
→ Wait 2 days
→ Send text (offer)
→ Wait 5 days
→ Send email (last chance)

Filter

A gate. Add criteria (the same builder as dynamic segments) and only contacts who match continue past this step; everyone else stops there. Use it to narrow after a broad trigger, e.g. Form submission → filter Location equals Westwood → location-specific reply.

Conditional (if / else)

A fork. Contacts matching the criteria take the Yes branch; everyone else takes No. Each branch continues with its own steps, so both audiences get handled. Unlike a filter, nobody is dropped. The node summary reads If / else with the rule count.

Conditionals nest: put another conditional inside a branch for more granular routing.

Delivery windows

The editor’s Delivery window panel constrains when messages go out, regardless of when a contact reaches a send step:

  1. Toggle Limit delivery hours.
  2. Set allowed hours per day, Monday through Sunday. Apply to all days and Weekdays only fill the schedule quickly.
  3. Save delivery window.

If a contact hits a send step at 2 AM, the message waits until the window opens. Waits still elapse in real time; only sending is deferred.

Exit triggers

Covered in Triggers, but they’re part of your logic toolkit too: an exit trigger like Customer event: purchase turns any nurture flow into “message until they buy, then stop.”

Was this page helpful?