What Is n8n? A Complete Guide for Operations Teams

n8n (pronounced "n-eight-n") is a fair-code workflow automation platform that lets you connect business applications, automate repetitive tasks, and build complex workflows through a visual drag-and-drop editor. Unlike fully proprietary tools like Zapier, n8n can be self-hosted on your own infrastructure, so your data never leaves it. The native integration library covers the tools most B2B operations run on (Salesforce, Stripe, Slack, Jira, Google Workspace, HubSpot) and anything missing gets handled by the HTTP node, which in practice means the catalogue size matters far less here than it does on platforms without one.

If your operations team is still copying data between systems, manually sending follow-up emails, or spending hours on invoice processing, n8n is built to eliminate that work entirely.

How Does n8n Work?

n8n uses a node-based visual editor where each node represents a trigger, an action, or a piece of logic. You connect nodes together on a canvas to build workflows that run automatically.

For example, a simple workflow might look like this: a new deal closes in Salesforce (trigger node), which creates an invoice in Stripe (action node), sends a notification to a Slack channel (action node), and creates a project in Jira (action node). That entire sequence runs without anyone touching a keyboard.

What makes n8n different from other automation platforms is its "code when you need it" approach. You can build 90% of your workflow visually, then drop into JavaScript or Python for complex data transformations or custom logic. This makes it accessible to operations managers who prefer visual building while still being powerful enough for developers who need full programmatic control.

Why Are Operations Teams Choosing n8n in 2026?

Several factors are driving n8n's rapid adoption among B2B operations teams.

Cost structure. n8n charges per workflow execution, not per individual step. A single workflow execution costs the same whether it contains 2 steps or 50 steps. On platforms like Zapier, every step counts as a separate task, which means a complex workflow can burn through your monthly allocation quickly. A self-hosted n8n instance running on a VPS at $15 to $25 per month can replace $500 or more in monthly Zapier costs for high-volume workflows.

Self-hosting and data control. For companies handling sensitive financial, healthcare, or client data, self-hosting eliminates third-party data processing concerns entirely. Your data never leaves your infrastructure. n8n can run on Docker, a Kubernetes cluster, or a basic virtual private server.

AI-native capabilities. n8n now includes over 70 dedicated AI nodes with deep LangChain integration. You can build workflows that use GPT-4, Claude, or local language models to analyze documents, classify emails, generate responses, and make routing decisions, all within the same visual workflow editor you use for everything else.

Enterprise-grade features. n8n supports role-based access control, SSO via SAML and LDAP, audit logging, encrypted secret stores, version control through Git, and isolated environments for staging versus production deployments.

How Does n8n Compare to Zapier and Make?

This is the most common question operations leaders ask, and the answer depends on your team's technical comfort level and workflow volume. (For a deeper head-to-head, see our n8n vs Zapier vs Make comparison.)

Zapier is the easiest to get started with. Its interface is the most intuitive, and it has the largest pre-built integration catalogue of any platform, which genuinely matters if the tool you need to connect is obscure. But it is the most expensive at scale because it charges per task, and it offers no self-hosting option. If you run simple, low-volume automations and want zero learning curve, Zapier works well.

Make (formerly Integromat) sits in the middle. It offers a visual builder that is more flexible than Zapier's linear structure, supports branching and conditional logic more naturally, and costs significantly less per operation. Make is a strong choice for teams that need moderate complexity without writing code.

n8n is the most powerful and cost-effective option for teams willing to invest a bit more time in setup. It handles complex logic, custom API calls, AI integrations, and high-volume workflows better than either alternative. The tradeoff is a steeper learning curve and the need for some technical knowledge, especially for self-hosted deployments.

For most B2B operations teams processing more than a few thousand workflow executions per month, n8n delivers the best long-term value.

What Can Operations Teams Automate With n8n?

Here are the most common use cases we build for clients at Ops Automators.

CRM to billing automation. When a deal closes in Salesforce or HubSpot, n8n automatically generates an invoice in Stripe, syncs payment status back to the CRM, and sends reminders for overdue payments. This eliminates the manual handoff between sales and finance that causes billing delays and errors.

Client onboarding workflows. A new client signs a contract, and n8n triggers a cascade of actions: creates a project in Jira, assigns consultants based on availability, schedules a kickoff call through Calendly, sends welcome emails, provisions tool access, and notifies the team in Slack. What used to take a project manager two hours of setup happens automatically in seconds.

Cross-platform data sync. n8n keeps data consistent across systems that do not natively integrate. Salesforce opportunity updates sync to Jira milestones. Google Calendar events sync to personal calendars for conflict detection. Invoice data in Stripe syncs to accounting platforms. Every manual copy-paste between systems is a potential automation.

AI-powered document processing. n8n workflows can receive documents (contracts, invoices, reports), send them to an AI model for analysis and data extraction, and route the extracted information to the right systems automatically. A contract comes in, AI identifies the key terms, and the relevant fields populate in your CRM without anyone reading the document manually.

Error monitoring and alerting. n8n can monitor your other automations and business processes, detect failures or anomalies, and alert the right people through Slack, email, or SMS before small issues become big problems.

How Do You Get Started With n8n?

You have two options: n8n Cloud or self-hosting.

n8n Cloud is the fastest path. You sign up, get a hosted instance, and start building immediately. Cloud plans start at $20 per month and include automatic updates, managed infrastructure, and support. This is the right choice if you want to start building workflows today without thinking about servers.

Self-hosting gives you maximum control and the lowest long-term cost. You install n8n using Docker (the most common method) or npm on any Linux server. A basic DigitalOcean or AWS instance running n8n costs $15 to $25 per month regardless of how many workflows you run. Self-hosting requires some technical knowledge for initial setup, updates, and maintenance: our complete self-hosting guide walks through the production setup.

For most operations teams, we recommend starting with n8n Cloud to learn the platform and validate your first few workflows, then migrating to self-hosted once you are running production workloads and want to optimize cost.

What Does It Cost to Build Automations in n8n?

The n8n platform itself is affordable (free for self-hosted, $20+ per month for Cloud). The real cost is in designing, building, and testing the workflows.

If you build in-house, the primary cost is your team's time. A straightforward two-system integration might take a few hours. A complex multi-system workflow with error handling, conditional logic, and AI components can take days or weeks to get right.

If you hire a consultant or agency like Ops Automators, simple integrations typically run $2,500 to $5,000, mid-complexity workflows (three to five connected systems) range from $5,000 to $15,000, and full operations overhauls with multiple interconnected workflows can reach $25,000 to $50,000.

The payback period is usually fast. If an automation saves your team 10 hours per week at an effective rate of $50 per hour, that is $2,000 per month in recovered capacity, and a $5,000 project clears in under three months. The one line people leave out of that arithmetic is maintenance: connectors break when vendors change APIs, and somebody has to notice and fix it. Our breakdown of what automation actually costs puts numbers on the ongoing side as well as the build.

Three situations where you shouldn't pick n8n

We build most of our client work on this platform, so treat the following as the part we'd rather you read.

You need two automations and nobody owns them. n8n rewards a person who checks on it. If the honest answer to "who looks at the execution log on a Tuesday" is nobody, use Zapier. It costs more per task and that's the correct trade, because you're buying somebody else's uptime. A cheaper platform that quietly stops running is not cheaper.

You're self-hosting to save money and that's the only reason. The $15 to $25 a month VPS is real, and so is everything around it: upgrades, backups of the workflow database, credential rotation, TLS, watching disk fill up with execution history. That's not hard, but it's a small standing obligation and it belongs to somebody. If nobody wants it, n8n Cloud at $20 a month removes the whole category. Self-hosting earns its keep when data residency requires it or when volume makes the arithmetic overwhelming. Below that, you're paying in attention rather than dollars.

Your workflows are one trigger and one action, forever. The reason to accept a node editor is branching, loops, transformations, and inline code. If your automations genuinely are "form submits, row appears in a sheet," you're carrying the complexity of a general-purpose tool for none of its benefit. Native integrations between the two apps, or Zapier, will do it and stay done.

None of that describes most operations teams past twenty people, which is why we ship on n8n. But it describes enough of them that we say it out loud on scoping calls, usually before anyone asks.

If you're in the "we want the capability but not the maintenance" middle, that's the gap we fill: design, build, host, monitor. Tell us what breaks in your week and we'll tell you whether it's an n8n problem or something you can fix without a platform at all.