Journeys allows for a Node to set delivery rules, including the Wait for Event option, which allows you to configure the node to wait up to a specified number of days for an Inbound Webhook event.

When a Journey Node is configured for to wait for an Inbound Webhook, an explicit Webhook Endpoint URL will be provided.

Waiting Journey Nodes can be triggered by sending a POST request to the provided Webhook Endpoint URL with the following payload structure:

Param NameRequiredTypeDescription
emailYesStringThe email address of the customer
session_dataNoJSON ObjectMetadata to be attached to the customer's current journey session metadata


The customer must actively be queued on the specific waiting journey node at the time this request is sent.


When cloning a journey, each node configured to wait for a webhook will receive a new explicit Webhook Endpoint URL.