Delay
Pause before continuing
Delay holds a job in place for an amount of time you choose, then lets it continue, which is useful for spacing steps out or waiting a while before sending something like a reminder.
How it works
Not everything should happen the instant the step before it finishes. Delay is a deliberate pause: the job reaches this node, waits the length of time you set, and only then moves on to the next step. Nothing is lost while it waits, it simply sits paused.
The most common reason to use it is timing a follow-up. You might want a reminder to go out a day after the first message, or a second notice a week later. Placing a Delay before the sending step spaces those out without anyone having to remember to press send at the right moment.
It is also handy for gentle pacing when you do not want a burst of activity all at once. Insert a short wait and the downstream steps happen on a calmer schedule instead of firing back to back.
Common use cases
Real situations where this node earns its place in a flow.
Time a follow-up
Pause a flow so a follow-up email goes out a day later instead of instantly.
Space out delivery
Hold between sends to stay under a rate limit.
Give a grace period
Wait before escalating so the recipient has time to act first.
Delay in a workflow
A simple example of where this node sits in a flow.
What you set up
- Set how long the pause should last (for example a number of minutes, hours, or days).
- Place Delay in the flow right before the step that should wait.
- Remember the job stays parked for the whole duration, so plan follow-ups around that waiting window.
Common questions
Does a paused job cost anything while it waits?
Delay itself is plumbing and does no processing work while it counts down. Costs come from the steps that actually read documents or send messages, not from the wait.
Can I use it to schedule something days in advance?
Yes. You can set a long wait so a follow-up goes out a set number of days later, which is a simple way to time reminders and second notices.
Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.
amountHow long to wait before continuing; blank or non-positive makes the node a passthrough.
Type: numberunitUnit the wait amount is measured in.
Type: enum: seconds | minutes | hoursDefault:seconds
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": "delay",
"type": "card",
"position": {
"x": 160,
"y": 120
},
"data": {
"type": "delay",
"kind": "processor",
"title": "Delay",
"subtitle": "Pause before continuing",
"config": {
"amount": "0",
"unit": "seconds"
}
}
}