Schedule router
Branch on time of day
Schedule router sends a job a different way depending on the time, the day, or whether it arrived during business hours, so after-hours work can take its own path.
How it works
This node reads the clock, not the document. It looks at when a job arrives (the hour, the day of week, inside or outside your business hours) and steers it down the path that fits that moment, so timing alone can change how something is handled.
The common use is separating the workday from everything else. A submission that lands at 2pm on a Tuesday can go straight to your team, while one that arrives at midnight or on a weekend can be queued, auto-acknowledged, or held until morning, all without anyone watching the inbox.
It pairs naturally with a delay step or an after-hours auto-reply. Where Router branches on what the paperwork says, Schedule router branches on when it showed up, so you can use both in the same flow.
Common use cases
Real situations where this node earns its place in a flow.
Handle after-hours differently
Send jobs that arrive overnight down a queue-for-morning path and daytime ones straight through.
Hold weekend work
Branch weekend submissions to a Monday batch instead of paging someone off-hours.
Route by arrival window
Apply different logic during a promotion window versus outside it.
Schedule router in a workflow
A simple example of where this node sits in a flow.
What you set up
- Define your business hours and the time zone they are measured in.
- Create a path for each time window you care about (business hours, after hours, weekends).
- Decide what the off-hours path does: hold, auto-acknowledge, or route to an on-call step.
Common questions
Which time zone does it use?
The time zone you set for your business hours, so 'after hours' matches your local clock rather than the server's. Set it once when you configure the windows.
Can I treat weekends differently from weeknights?
Yes. You can define separate windows for weekdays, weeknights, and weekends and give each its own path, so a Saturday submission need not be handled like a Tuesday evening one.
Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.
scheduleConfigreqTime-of-day branches { timezone, branches:[{ id, label, windows:[{ days, start 'HH:MM', end 'HH:MM' }] }] }; first matching window wins, else __else__. Ranges can wrap past midnight.
Type: JSON string
How this node appears inside a workflow's nodes[] array (the shape you see in the Developer export / import). A full workflow is { nodes: [...], edges: [...] }.
{
"id": "schedule-router",
"type": "card",
"position": {
"x": 160,
"y": 120
},
"data": {
"type": "schedule-router",
"kind": "processor",
"title": "Schedule router",
"subtitle": "Branch on time of day",
"config": {
"scheduleConfig": "[]"
}
}
}