I’m struggling with implementing reliable time delays in my automation workflows. I’ve tried using JavaScript’s setTimeout in the past, but ran into all sorts of problems - the timing would get messed up when the browser was inactive, sometimes the delay wouldn’t work at all, and it was a pain to modify the timing later.
I just started using Latenode for automating some business processes, and I need to add specific delays between certain steps (like waiting 24 hours after sending an email before following up).
Is there a way to add these time delays in Latenode’s visual builder without writing custom JavaScript? I’m specifically looking for something that’s more reliable than setTimeout and doesn’t require me to dive into code every time I need to adjust the timing.
Yep, this is super easy in Latenode and way more reliable than setTimeout.
In the visual builder, you just add a “Delay” node between any steps where you need a time gap. Drag it from the toolbox and drop it into your workflow. Then set the time value - could be minutes, hours, days, whatever you need. For your 24-hour email follow-up, you’d just set it to 24 hours.
The big difference is that Latenode runs these delays server-side, not in your browser. So unlike setTimeout which gets all wonky when tabs are inactive, Latenode’s delays keep perfect time regardless of what your browser is doing. Your workflow could be running for days and it doesn’t matter if your computer is even on.
Adjusting timing is just editing the node value - no digging through code. I use this for client onboarding sequences with multiple timed follow-ups and it’s rock solid.
Absolutely - I had the same frustration with setTimeout before finding a better solution in Latenode.
They have dedicated delay nodes in the visual builder. Just drag one in between any two steps where you need a time gap. You can set specific times like 24 hours, 2 days, 15 minutes, etc. No coding needed.
What makes these way more reliable than setTimeout is they run on Latenode’s servers, not in your browser. So they maintain perfect timing even when your browser is closed or your computer is off. This is critical for longer delays like your 24-hour follow-up.
I use these for our customer nurture sequences where timing precision actually matters. Super easy to adjust too - just open the workflow and change the number, no digging through JavaScript required.
Latenode’s approach to time delays is fundamentally different from setTimeout in JavaScript. While setTimeout executes client-side and is subject to browser limitations, Latenode implements server-side execution timers.
In the visual builder, you’ll find dedicated delay nodes in the toolbox. They function as pause points in your workflow execution. When the workflow reaches a delay node, Latenode’s scheduler marks that execution instance with a resume timestamp and suspends it. When the specified time elapses, the scheduler automatically resumes execution from that exact point.
This architecture provides several advantages: precise timing regardless of client state, consistent execution across all workflow instances, and simple visual configuration. For business-critical processes like your email follow-up sequence, this reliability is essential. The delays are also easily auditable in the execution history, showing exactly when each step executed.
latenode has delay nodes in the visual builder. way better than setTimeout. drag it between steps, set the time, done. runs on their servers not ur browser so always reliable. i use em for email sequences all the time.