My use case is that I have a workflow that needs to run at different time intervals. Users can create multiple schedules for the same workflow. For example, if a user creates three schedules, the workflow should be triggered three times, once at each scheduled time.
How can we design and implement this so that the workflow executes according to all the schedules created by the user?
Welcome @mylearnings_abu to n8n community!
About your question, You don’t need multiple workflows for this – you can keep one workflow and let a single Schedule Trigger fire it at several different times.
Here’s a concrete example you can drop straight into your editor.
With this single trigger, the same workflow will run:
Every day at 9:00 AM
Every Monday at 3:30 PM
Every Friday at 12:00 PM (via the cron expression 0 12 * * 5)
So it covers your “one workflow, multiple schedules” requirement without duplicating any logic.
Hope this useful for you! Ask me anything if you need to clarify!
Thank you for sharing this . I have one more question like do we have any n8n api which we can use to add these trigger rules for a workflow . My use case is very dynamic like one user can create a schedule to execute workflow and i need to attach that rule to the workflow may be using n8n api? Please suggest what would be appropriate?
While it is technically possible to use n8n’s API to change a workflow’s schedule, it is not recommended. To do this, you would have to rewrite the entire “blueprint” of the workflow every time a user adds a rule. This is risky because one small mistake in the code could break the entire workflow, and it becomes very slow and unstable if many users are changing their schedules at the same time.
The better approach is to use a “Dispatcher” system. Instead of changing the workflow itself, you store all your user schedules in a simple database. You then create one separate “Manager” workflow that runs every minute to check that database. If the Manager sees that it is time for a specific user’s task to run, it simply sends a signal to trigger the main workflow.
This method is far more professional and scalable. It allows you to add, edit, or delete thousands of different schedules instantly in your database without ever needing to touch the n8n settings or re-publish your workflows. This keeps your system stable, prevents crashes, and makes it much easier to manage as your user base grows.
