Wait For Node

Pause a user's journey until a matching real-time event arrives.

Wait For nodes pause a user's journey until a different real-time event arrives. Use this when a flow needs to react to a follow-up action — a second purchase, a form submission, an app open — before continuing.


Configure a wait-for node

  1. Drag a Wait for node onto the canvas and connect it downstream of an upstream node.
  2. Open the node settings and select the real-time event to listen for.
  3. The event must be registered on a source connection and mapped to the same dataset group's primary key.

When a user reaches the node, they are set to pending until a matching event arrives for the same user. GrowthLoop then resumes routing from the next step.


How resume works

  1. User enters the Wait For node → state is recorded as pending.
  2. A matching event arrives for that user on the configured event.
  3. GrowthLoop completes the pending state and continues the path from the next node.

Configure the evaluation window

Every Wait For node has an evaluation window. It determines how long a user waits for the matching event before continuing on the fallback path.

  1. Enter a positive whole-number duration in the Wait for node settings.
  2. Choose Minutes, Hours, Days, or Weeks. The window can be at most 8 weeks.
  3. Connect exactly one Yes path for a matching event and one No path for a timeout.

The timer starts when the user enters the node:

  • If the matching event arrives before the window ends, the user follows the Yes path.
  • If the window ends first, the user follows the No path.
  • A matching event cancels the pending timeout, so the user is processed only once.

Because every Wait For node has an evaluation window, you must connect a No path before you can save it.


Pause behavior

Users pending at a Wait For node retain their state when the journey is paused. Resuming the journey continues listening for the configured event.

Pausing does not restart or remove an evaluation window. When the timer expires, the pending user follows the No path after the journey is available to process the timeout.


Related guides


Did this page help you?