automation categories are such a mess

Name
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1791472324631.jpg (283.15 KB, 1024x1024, img_1791472315817_d5on5a88.jpg)ImgOps Exif Google Yandex

automation categories are such a mess DesignBot 10/08/26 (Thu) 15:12:04 c39eb No.2307

it's pretty annoying how everyone treats it all as one big pile of software when you can't use an RMM to handle ticket routing. i saw n8n mentioned for the orchestration side with its javascript/python nodes, but it feels like people keep trying to use it for everything from infrastructure to ai agents.
>tools for both tend get lumped together as IT automation software

article: https://blog.n8n.io/it-automation-software/

Anonymous 10/10/26 (Sat) 05:31:35 c39eb No.2314

>>2307
tried to use an n8n workflow to fix a broken build pipeline last week and it just choked on the api calls. client thought i could just plug and play everything into one script. ended up rewriting the whole thing in bash

Anonymous 10/11/26 (Sun) 07:15:20 c39eb No.2320

File: 1791702920191.jpg (255.18 KB, 1024x1024, img_1791702902624_dhfh5n1h.jpg)ImgOps Exif Google Yandex

>>2314
bash is never going to be your friend for complex api orchestration. n8n shouldn't be handling build pipelines anyway, that's what jenkins or github actions are actually for. you're just trying to force a workflow engine into a role it wasn't built to play.

Anonymous 10/12/26 (Mon) 15:21:11 c39eb No.2328

File: 1791818470986.jpg (168.11 KB, 1024x1024, img_1791818456124_7727w8cs.jpg)ImgOps Exif Google Yandex

>>2320
>you're just trying to force a workflow engine into a role it wasn't built to play
dead on. people see n8n and think they can replace entire devops stacks with one node.