Delay

Delay node halts the workflow for a given time period before moving to the next step. It is best used in case of reminders and re-engagement notifications where you want to bring back user to the product after a period of their last action.

There are 3 types of delay types available: Fixed (fixed for all users), Dynamic (Passed in trigger payload), Relative (relative to a future timestamp, eg. 10 mins before task due time).

In case of dynamic delay, delay duration is computed using the data from trigger payload. Dynamic delays are helpful for reminders where the schedule is dictated by the user or when reminders need to be sent before the event or task due date.

For instance, you might want to send a reminder one day before an interview date. In such scenarios, the reminder schedule can also be user-defined, resulting in variable delays per user. Consider the example of Google Calendar, where each user sets their own reminder schedule for meetings—some opt for reminders 10 minutes before, while others prefer 30 minutes before. Dynamic delays accommodate these individual preferences seamlessly.

You can add duration key as a JQ-expression. Below are some examples of how to add duration key in JQ format:

General format for duration key at parent level is .duration_key

If the duration key is a nested event property key like shown below, enter it in the format .appointment_details.time

properties = {													  
  "appointment_details": {  
    "time": "2024-03-02T20:34:07Z",  
    "location": "1775 Stanford Ave, Menlo Park, CA 94025"  
  }

Your duration key variable can be computed to either:

An ISO-8601 timestamp (e.g. 2024-03-02T20:34:07Z) which must be a datetime in the future, or
A relative duration unit, which can be
- an integer like 50, considered as duration in seconds.
- an interval string defined as xxdxxhxxmxxs, where d = day, h = hour, m = minutes and s = seconds

When the duration key specified is missing, or resolves to an invalid value, workflow execution will stop and corresponding error will be logged in the logs

GETTING STARTED

CORE CONCEPTS

WORKFLOW BUILDER

SUPRSEND BACKEND SDK

SUPRSEND CLIENT SDK

Notification Inbox

PREFERENCE CENTRE

VENDOR INTEGRATION GUIDE

INTEGRATIONS

MONITORING & DEBUGGING

MANAGE YOUR ACCOUNT