What n8n is, and when we refuse to use it

What n8n is, and when we refuse to use it

n8n is an open-source, node-based workflow tool. You connect apps and APIs on a canvas and write JavaScript when a node is not enough. You can self-host it or use their cloud.

We have used it for internal glue: "when a form lands, create a row, notify Slack, send an email." That is a good fit.

What it is good at

• Internal ops that change weekly (new CRM field, new Slack channel).
• Non-engineers editing a step without a deploy, if you accept the risk.
• Prototyping an integration before you write Elysia code.

What we do not put in n8n

• Auth for end users of a SaaS.
• The only copy of pricing or permission logic.
• Anything that must be tested in CI with the rest of the repo.
• A customer-facing chatbot that has to cite private documents. That belongs in an API with logs. See agentic workflow vs chatbot.

If the workflow is the product, you will outgrow the canvas. Then you rewrite it anyway, under deadline.

Self-host versus cloud

Self-host if credentials cannot leave your VPC and you have someone who will patch the box. Cloud if this is a side process and downtime is an email, not a payroll miss.

n8n stores credentials. Treat the instance like production, not a toy VM.

How this shows up in training

We show n8n so students see the difference between glue and a system of record. Assignments still require an Elysia route they can test. Automations that cannot be explained in a PR description get rejected.

For custom APIs and integrations, see IT consulting or schedule a call.