Thank you for filing this feature request. The following is not meant to criticize you or anyone who is not working at the company.
I think this is underrated and ignored. (Dear n8n Team, why do you lead people to the – allegedly friendly – forums and have them file feature requests here in an unconstructive manner and where they don’t get addressed, when companies like Tailscale show how one should be doing it. Is this a GitHub feature where you wanted to save a few euros & incompetence, or is is just incompetence?)
That is what I expect from any modern solution used to schedule things.
cron / crontab on Unix-like systems were plain text files which should be managed with care. If you have several pages of crontabthat regularly need attention, then you are doing something wrong (and yet I see people doing exactly this in the workplace). Theres anacron which does things differently and uses a folder structure.
Systemd has systemctl list-timers. No sysdamin today should accept anything inferior to this.
Again, that is something I expect from a software that does scheduling, and pretends to do it well, or it’s a complete failure.
Imagining home users, or worse company employees, creating more than a few handful of workflows with schedules, without an overview (and without saving successful executions). DevOps, DevOps, DevOps, SRE and AI. I don’t believe anyone who pretends that this is normal. This is madness!
n8n has it’s own API. Before writing this post, while I was exploring n8n, I already created a curl | jq command to render a list of workflows with it’s (active) triggers. I guess I need to look at this again and include the schedules to and post it here. I hoped that this wouldn’t be a concern by the time I know enough about n8n.
… and, if its not a dashboard yet, shouldn’t this be a templated workflow? The closest thing I can find so far: Activate and deactivate workflows on schedule using native n8n API | n8n workflow template
(Checking my notes, … nope, no curl | jq command. This was actually the first workflow I created and the usecase I had for the n8n API. Somewhat ironic.
)
I’m amazed by the potential the software has. Unfortunately, the IT industry suffers from technical debt caused by innovation / disruption without a plan and technophobic people looking for an office job where they don’t have to do anything (= mismanagement).