Q: n8n vs Zapier vs Make — is that AI engineering?

No, but both have their place, and it's worth being clear about which path is which.

n8n, Zapier, and Make are no-code automation tools. You build workflows on a visual canvas: a trigger fires (an email arrives), and connected blocks run in sequence (extract the attachment, summarize it with an LLM, post the summary to Slack). All three now have AI blocks, so you can call models and build simple agents without writing code.

There is real demand for this. Small businesses everywhere want their processes automated, and they'll happily pay someone who can wire up their intake forms, invoices, and follow-up emails. People build entire freelance careers and consultancies on exactly this: create a profile on Upwork or similar platforms, apply for automation jobs, deliver n8n workflows. If you want to run an automation consultancy for small businesses, or automate your own small business, these tools are a legitimate way to do it.

But that path is not AI engineering, and the difference shows up in who's buying. Small businesses need workflows glued together. Medium and large enterprises need robust, production-grade AI systems: proper retrieval with your own chunking and embeddings, evals that prove output quality is holding, traces you can debug, guardrails, security, cost control at scale. You cannot deliver that with a visual automation tool, and enterprises don't hire for it that way.

So if you're already an engineer (software, data, cloud) and you're building a career in AI engineering, your toolset is different: Python, LLM APIs, vector databases, agent orchestration, AWS. That's what AI Engineer roles at the salaries on this page require. Knowing n8n won't hurt you, and it's fine for quick internal automations. But don't confuse the two paths: one is automation services for small business, the other is an engineering career. This page is about the second one.