I am trying to build a workflow in which I want only specific nodes—four nodes—to run in a loop indefinitely, executing every day. Initially, I will provide the necessary variables in a subflow at the beginning, and the workflow will perform some initial steps before entering the loop. I want it to function similarly to this workflow: Monitor competitors’ websites for changes with OpenAI and Firecrawl | n8n workflow template.
We have a built-in timer trigger, and below I am sharing how to use it. In addition to built-in trigger nodes, integrations also have callback/polling trigger sub-types, where the polling type comes with a scheduling feature. Polling triggers also have scheduler capabilities, so any integration trigger with a scheduled type can be used just like the built-in timer.
I want a standalone wait/sleep function that will pause execution for a certain period before proceeding to the next node. For example, if I want to wait for one hour before retrieving new data and processing it in the next node, what should I do?
1 Like
For the functions like these, official nodes will be coming soon. Once these nodes are available, necessary operations such as wait/sleep can be easily dropped and used between the desired nodes.
1 Like
Our officially developed Delay Node is now live and ready to use! 
It allows you to introduce a controllable pause in your app, making it ideal for throttling processes, adding intentional delays, or waiting for external conditions.
You can view the node details and learn how to use it in the technical documentation below:
1 Like