Skip to main content
A wait-until step holds the Automation until a specific event is received. Unlike a delay, which resumes after a fixed time, this step resumes when something happens in your application. Common use cases:
  • Payment: Wait for a payment to succeed before sending a receipt.
  • Adoption: Wait for a user to complete an action to unlock a feature.
  • Verification: Wait for the user to verify their email before continuing.

How it works

Add a Wait for event step and configure the event to wait for.Automation for Event

Timeouts

When you set a timeout, the step will stop waiting after that duration. This prevents Automations from waiting indefinitely. When a wait-until step times out, it produces two possible connection types:
Connection typeWhen it’s used
event_receivedThe event arrived before the timeout
timeoutThe timeout elapsed without receiving the event
You can create different paths depending on whether the user took action within an given time period.
The maximum timeout is 30 days.

Filter rules

Use filter_rule to match events that meet only specific criteria. This is useful when the same event name might be sent with different payloads. For example, to wait specifically for a successful payment:
The filter rule supports the same operators as condition steps.

Configuration

config.event_name
string
required
The name of the event to wait for.
config.timeout
string
The maximum time to wait before timing out (e.g. "3 days", "1 hour"). Maximum: 30 days.
config.filter_rule
object
An optional rule object to filter incoming events.
Example