Just curious what people are using n8n for.
I just finished setting up a workflow that sends me a Telegram message every night about photography opportunities for the next day. It puts together weather data, POIs (which I defined for my location), sun/moon position, milky way visibility, cloud cover, etc. The message then simply tells me if it’s worth it going out in the morning.
You must log in or register to comment.
I use it for just two things, triggering a download with a docker tool over a webhook call I use in a userscript and calling a webhook of a media server on local file changes
A governmental-ish site I’m required to use doesn’t push notifications as mails, so you have to login daily to check for updates. Updates may happen multiple times daily or once a month. I automated my server to access the site once a day with my credentials, screenshot the notifications, parse them with ocr, and send myself a mail.
That’s pretty cool OP. I use n8n for various automation around the lab but the most recent would be an addition to my dashboard. The n8n routine will fetch the latest, animated, Solar Flare and Aura Forecast from sol24.net. I’ve always been fascinated with the sun and our atmosphere since I was a kid.
I’m not willing to run something that risky on my own infrastructure, therefore I wont run it. I can do all of those things with a handful of scripts or Home Assistant anyway.
May I ask why you consider n8n risky?
I’m not a slop jockey and I’m watching people plug these kinds of things into public data and having it do operations with financial/business impacts.
I’d rather employ a gremlin to write scripts.
I’m not a slop jockey
Are you aware that you are not required to run AI with n8n? There are two flavors: With AI and without.
lowcode environments are the O.G slop.
Wow! Well, you can keep your attitude.
Just look at the recent vulnerabilities it had. It just had a CVE 10 in January and March of this year.
Almost all of them affect authenticated users. The only ones that allow unauthenticated users access are for old versions. So to be honest: I am not that much concerned.
You aren’t concerned about a severity 10 vuln? Those are found in software with exceptionally bad qa and abandonware. That should give you pause about how hard n8n is “going fast and breaking things”.
Well, this “authenticated user” could be your fucking LLM and this is really concerning. Besides that a single CVE 10 is also very concerning no matter how old the affected version is.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters DNS Domain Name Service/System HTTP Hypertext Transfer Protocol, the Web IP Internet Protocol NAT Network Address Translation nginx Popular HTTP server
4 acronyms in this thread; the most compressed thread commented on today has 8 acronyms.
[Thread #242 for this comm, first seen 17th Apr 2026, 11:20] [FAQ] [Full list] [Contact] [Source code]
