What Is n8n? The Automation Engine Behind Modern Businesses
A plain-English introduction to n8n — what it does, why you need it, how it fits in the stack, and how it compares to Zapier and Make.
When I built SendJob — a job dispatch automation system for HVAC and plumbing businesses — I needed something to tie everything together. I had Supabase storing job records, Twilio for SMS, Resend for emails, and Stripe for payments. The tools were all there. What I didn’t have was anything to make them talk to each other.
That’s where n8n came in.
n8n is the engine that runs underneath everything. It’s the piece most business owners never see — but without it, there’s no automation. There’s just a collection of disconnected tools and a lot of manual work.
This guide is a plain-English introduction to what n8n is, why it matters, and how it fits into a real business stack. No coding required to follow along.
What n8n Actually Is
If you’re a business owner, here’s the simplest way to think about it: n8n is the invisible engine that connects your tools and runs your automations on autopilot. When a customer submits a form, n8n can save their info to your database, send them a confirmation email, text your technician, and create an invoice — automatically, in sequence, without anyone touching a keyboard.
If you’re a builder, here’s what’s under the hood: n8n is a self-hostable, open-source visual workflow automation tool. You build workflows on a canvas by connecting nodes. Each node is a step — a trigger, an action, or a piece of logic. You connect them with wires. When the workflow runs, it executes the nodes in order.
What makes n8n stand out technically:
- 400+ built-in integrations — Supabase, Stripe, Twilio, Slack, HubSpot, Airtable, and hundreds more. If there’s no built-in node, you can use the HTTP Request node to call any API.
- A Code node — Write real JavaScript when you need custom logic that no pre-built node can handle.
- Webhook support — Any external system can trigger a workflow by hitting a URL.
- Self-hostable — You can run n8n on your own server. No per-task pricing, no execution limits imposed by a vendor.
- Visual and code hybrid — You don’t have to write code, but you can. That’s a rare combination.
The no-per-task-pricing point matters more than it sounds. Most automation tools charge based on how many times your workflows run. n8n’s cloud plans charge based on active workflows and monthly executions, but the self-hosted version is completely free. When you’re running thousands of automations a month — which happens fast in a real business — that difference is significant.
Why You Need It
Here’s what happens to a field service business without an automation layer.
A customer calls to book a job. Someone manually creates a record in whatever system you use. Someone manually assigns it to a technician. When the technician is on their way, someone manually texts the customer. When the job is done, someone manually sends an invoice. If the customer doesn’t pay, someone manually follows up.
That’s five manual touchpoints for a single job. Multiply that by 20 jobs a day, and you have a full-time job that consists entirely of copy-pasting information between tools and sending messages that could have been sent automatically.
In SendJob, the same flow runs like this: a job is created in the database → n8n detects the new record → automatically texts the customer with a booking confirmation → notifies the assigned technician → when the job status is updated to “enroute,” automatically texts the customer an ETA → when the job is marked complete, automatically sends an invoice via email. No one touches anything.
The other reason you need an automation layer is that things fall through the cracks without one. A new lead comes in at 9pm. Without automation, they might not hear back until the next morning. With n8n, they get an immediate confirmation email and someone on your team gets a Slack notification — no matter when it happens.
Manual processes also don’t scale. If your business doubles, you can’t just double your admin staff. You need systems that grow without proportional headcount.
Where n8n Fits in the Stack
Think of your tech stack like a city. Supabase is the warehouse — it stores everything. Twilio is the phone company — it sends and receives SMS. Resend is the post office — it handles email. Stripe is the bank — it processes payments.
n8n is the traffic system. It decides what goes where, when, and under what conditions. Nothing in the city moves without it.
Here’s how that looks in practice:
- Supabase stores your data — customers, jobs, invoices, technicians
- Twilio sends SMS messages to customers and techs
- Resend sends transactional emails — confirmations, receipts, reminders
- Stripe handles payment links and invoice creation
- n8n orchestrates all of it — it watches for events, pulls data, makes decisions, and calls the other tools in the right order
The key insight is that n8n doesn’t replace any of these tools. It sits on top of them. Each tool does one thing well. n8n is what makes them work together as a system.
How n8n Talks to the Rest of the Stack
Let me walk through a concrete example — the new customer inquiry flow in SendJob — so you can see how n8n connects the pieces.
1. Something triggers the workflow. In this case, a customer submits an inquiry form on the website. The form posts data to an n8n webhook URL. n8n receives the payload and the workflow starts.
2. n8n queries Supabase. It checks whether this customer already exists in the database. If they do, it updates their record. If they don’t, it creates a new one. This uses n8n’s Supabase node, which connects directly to the database using an API key.
3. n8n sends an SMS via Twilio. With the customer record confirmed, n8n calls the Twilio API to send a confirmation text: “Thanks for reaching out. We’ll be in touch within the hour.” This uses the Twilio node with your account credentials.
4. n8n sends a welcome email via Resend. At the same time (or in sequence, depending on your workflow design), n8n calls the Resend API to send a branded welcome email with more detail about what to expect next.
5. n8n creates a payment link via Stripe. If the inquiry is for a specific service with a known price, n8n can immediately generate a Stripe payment link and include it in the email — turning an inquiry into a potential sale in the same workflow.
Every step in that flow is a node in n8n. You can see exactly what’s happening, modify any step, add conditions (“only send the payment link if the service type is X”), and test the whole thing before it goes live.
n8n vs the Alternatives
You’ve probably heard of Zapier. Maybe Make (formerly Integromat). Here’s an honest comparison.
Zapier is the most well-known automation tool. It’s simple, has a good UI, and has thousands of integrations. The problem is the price. Real business usage — running workflows hundreds or thousands of times a month — costs $20-$50+ per month at minimum, and it gets expensive fast. Zapier also has limited branching logic. You can’t build complex conditional workflows easily. And you can’t self-host it.
Is Zapier fine? Yes — if your workflows are simple and you don’t mind the cost. A single webhook → send an email type of workflow is totally reasonable in Zapier. But the moment you need IF/ELSE logic, loops, custom code, or you start hitting execution limits, you’ll feel the constraints.
Make (Integromat) is a solid middle ground. Better visual interface than Zapier, more flexible logic, cheaper pricing, and it handles complex scenarios better. If I had to choose between Zapier and Make for a mid-complexity workflow, I’d choose Make. But Make doesn’t have a Code node worth using for serious transformations, and it doesn’t self-host. For most things I build, n8n gives me more control.
Microsoft Power Automate is aimed at enterprises already deep in the Microsoft ecosystem. If you’re running a small field service business or building something lean, Power Automate is overkill and genuinely clunky to work with. Skip it.
Pipedream is developer-focused and code-first. It’s powerful if you want to write code, but the visual workflow experience is weaker than n8n’s. It’s also a managed cloud service — no self-hosting.
n8n wins on: complexity, customization, price at scale, and the ability to self-host. The trade-off is a slightly steeper learning curve than Zapier, and the interface can feel overwhelming at first. But once you’ve built a few workflows, it clicks fast.
What n8n Costs
Self-hosted (open source): Free. You run it on your own server — a VPS on DigitalOcean, Railway, Render, or wherever. You pay for the server (typically $5-$10/month for a small VPS), not for n8n itself. No execution limits. No workflow limits. Full access to every feature.
n8n.io Cloud — Free tier: 5 active workflows, 2,500 executions per month. Enough to learn and build your first few automations.
Starter: $24/month — 15 active workflows, 10,000 executions per month. Good for a small business with moderate automation volume.
Pro: $60/month — Unlimited workflows, 50,000 executions per month. For businesses running automations at real scale.
For most people starting out, the free cloud tier is the right place to begin. You can build and test without spending anything. When you outgrow it — or when you want to run a serious production system — self-hosting is the answer. It costs almost nothing and removes all the limits.
What to Expect as You Go Deeper
This was the overview. You now know what n8n is, why it matters, and how it fits into a stack alongside Supabase, Twilio, Resend, and Stripe.
Here’s where this series goes from here:
The basics guide covers setting up n8n, understanding the interface, and building your first real workflow — from trigger to action. That’s where you start actually building.
The advanced guide goes into branching logic, error handling, the Code node, and real API integrations. That’s where you learn to build workflows that actually hold up in production.
The walkthrough builds a complete lead capture system end to end: form submission → Supabase insert → welcome email via Resend. Step by step, no skipping ahead.
Start with the basics and work through them in order. Each guide builds on the last.
Ready to build your first workflow? Start with The Basics →