Wait Step

Pause your workflow before proceeding to the next step.

Wait Types#

Duration#

Wait for a specific amount of time (minutes, hours, or days).

Time#

Wait until a specific time of day. Uses your organization's timezone.

If less than 10 minutes until target time, waits until next day to prevent spam.

Day of Week#

Wait until a specific day and time (e.g., Monday at 9:00 AM).

If target day/time passed this week, waits until next week.

Event (before or after a date)#

For a webinar, a live or a launch, set the Event date once in Workflow settings > General (for example 19 November 2026 at 12:30, Europe/Paris). Then each Event wait counts from that date, whatever day the subscriber signed up:

With a time of day, the wait keeps that local time even across a daylight saving change. Without one, it is an exact offset from the event start.

To give each subscriber their own session, pick a custom field under Per-subscriber date that holds a date such as 2026-11-19 12:30. It overrides the workflow date for that subscriber.

Date#

Wait until a fixed date and time, for example the moment doors close.

When the date already passed#

A subscriber who arrives after a wait's date never gets that reminder late. Someone who signs up the day before the live skips the "3 days before" and "2 days before" emails and only gets the reminders still ahead:

• by default, the run skips the emails, SMS and actions after the passed wait and lands on the next wait of the path (a condition, split or goal is never skipped);
• to route it yourself, add a Passed path to the wait (agents: an edge with sourceHandle: "PASSED");
• lateToleranceMinutes lets a run that is only a few minutes late still continue normally.

Changing the event date and publishing again moves every subscriber waiting on these steps to the new date.

Timezone#

Configure your timezone in Settings > Email Settings. Default is Europe/Paris.

Workflow Wait Until#

WAIT_UNTIL pauses until either subscriber filters match or a subscriber event arrives. It must have both MATCHED and TIMEOUT paths.

Filter mode:

{
  "id": "wait-until-customer",
  "type": "WAIT_UNTIL",
  "config": {
    "mode": "FILTER",
    "filters": [
      {
        "type": "TAG",
        "field": "tags",
        "operator": "BELONGS_TO_ANY",
        "tagIds": ["tag-customer"]
      }
    ],
    "timeout": { "duration": 7, "unit": "days" }
  }
}

Event mode accepts the complete Workflow event list and strict tagIds, product, or campaignId event filters. A timeout is optional in storage, but the graph still requires a TIMEOUT edge so every route is explicit.

While waiting, the run uses status WAITING, stores nextActionAt for timeouts, and can set waitingForAudienceChange so relevant subscriber updates wake evaluation.

Incremental schedules#

Wait values are relative to the previous step. For J0/J1/J3/J5, configure waits of 1 day, 2 days, and 2 days—not absolute waits of 1, 3, and 5 days.

Related Documentation#

• Workflows Overview - Learn about workflow automation
• Email Step - Send emails after waiting
• Action Step - Perform actions after waiting