Node referenceFlow control
WAIT_FOR_EVENT
WAIT_FOR_EVENT node.
What it does
WAIT_FOR_EVENT node.
Inputs & outputs
| Input handle |
|---|
| None |
| Output handle |
|---|
| None |
Configuration
No configuration.
Example
How it works
WAIT_FOR_EVENT pauses a Workflow until a communication event happens — such as a sent email being opened or a link being clicked — or until a timeout elapses. Wire in the internalCorrelationId (the tracking ID emitted by an earlier SEND_MAIL or messaging node), and configure the event to wait for plus a timeout via time and timeUnit (MINUTE, HOUR, DAY, MONTH, YEAR). The node snapshots and suspends execution; when the event arrives the Workflow resumes with result: true, or result: false if the timer expires first. See Wait & resume for how suspended executions are stored and revived.
Example
Scenario: Send a follow-up only if the recipient hasn't opened the first email within two days.
- A SEND_MAIL node sends the campaign and emits a tracking/correlation ID.
- Add a WAIT_FOR_EVENT node. Wire that ID into
internalCorrelationId, set theeventto the email-opened event, and settime=2,timeUnit=DAY. - Branch on
result: iffalse(no open before the timeout) send a reminder; iftrue, skip it.
SEND_MAIL ──(correlationId)──► WAIT_FOR_EVENT ──(result)──► branch