About the Timer Node
The Timer Node puts Profiles on hold during a specific period of time before they move onto the next node.
There are three timer settings
This timer setting allows you to choose a period of time for Profiles to wait.
Choose between 1 to 10 minutes, hours, days and weeks, and a specific time for Profiles to proceed to the next node.
If you set the Timer Node to wait 1 day, and proceed at 15:00, then the following will happen:
A Profile that enters the flow at 14:00 will wait for 1 day and 1 hour before they move onto the next node.
A Profile that enters the flow at 15:00 will wait for 1 day before they move onto the next node.
A Profile that enters the flow at 15:01 will wait for 1 day, 23 hours and 59 minutes before they move onto the next node.
This timer setting specifies exactly at which time and day of the week the Profiles will proceed to the next node.
Choose a specific time and day(s) of the week.
This timer setting pauses Profiles for a period of time of your choice, depending also on the day of the week, before they're allowed to proceed to the next node.
Choose a start and a finish for the time range. You may add as many time ranges as you want by clicking Add new time range.
Wait for dynamic time
This timer setting works like Specific Time, but the time is based on data in the incoming event.
For example an airline might want to send you a text message two days before your flight to ask if you want to book a seat.
There are three settings to take into consideration when working with this timer setting:
Base date: The data in the incoming event that should be use as a base for the timer setting.
Before or after: Whether profiles should leave the node before or after the base date
Offset: How long before or after the base date profiles should leave the node.
In the above airline example the setting would be used like this
Base date: Departure date
Before or after: Before
Offset: 2 days