Build Workflows around days and dates
New time conditions and record based schedules help Workflows act at the moment that matters.
A closer look
What changed
Workflow conditions can evaluate a time of day, one or more days of the week, or a calendar date when a field does not include time. Record schedules can also start a Workflow before or after a stored date, including supported shift and break times.
Why it matters
Automations can follow the timing of real operations instead of treating every date field the same. This helps teams keep messages inside working hours and act around shifts or deadlines.
How to use it
- 1Choose a date or time field in a Workflow condition or record based schedule.
- 2For a condition, select a time, a set of weekdays, or the available date mode.
- 3For a record schedule, choose the date field and whether the Workflow should start before or after it.
- 4Set the offset, review the label shown on the node, then verify and publish.
Example
Send a reminder only on weekdays, two hours before a scheduled shift begins.
Availability
Available to eligible accounts with Workflows access. Record based schedules require a supported date field on the selected record type.
Ask Customer SuccessGood to know
- Time conditions use the account timezone and show its abbreviation when it differs from the device timezone.
- Record schedule offsets are limited to 365 days.
- Scheduled break end is not available as a preset because it is calculated rather than stored as its own date field.
Time and day conditions
Route a Workflow based on the time of day or day of week, such as sending reminders only during working hours.
Schedules relative to a record
Start work before or after a date stored on a record, such as an upcoming shift or certification deadline.
