You’re paying for three different subscription services that don’t talk to each other. Your CRM doesn’t update when someone fills out a contact form. Your team manually copies data from Airtable into Google Sheets every Monday morning. These aren’t edge cases—this is what happens when small businesses grow past five people and suddenly have six different tools that were never meant to work together.
n8n is workflow automation software that connects your business tools without requiring a developer on staff. It’s self-hostable, which means you can run it on your own server instead of paying per-workflow fees that scale with your business. For companies that have already committed to a specific tech stack and need those tools to actually communicate, n8n makes sense. For companies still figuring out what software they need, it’s premature.
What n8n Actually Does Well
n8n handles the repetitive data movement that eats up 4-6 hours per week for most small teams. When a customer submits a Typeform survey, n8n can automatically create a row in your Google Sheet, send a Slack notification to your sales team, and add that contact to your email sequence in Mailchimp. You build these workflows visually—dragging boxes and connecting them with lines—but you’re working with real data structures, not dumbed-down templates.
The tool includes over 400 pre-built integrations with common business software. More importantly, it has a webhook system and HTTP request node that let you connect to anything with an API, even if n8n doesn’t have a native integration. This matters when you’re using industry-specific software that mainstream automation tools ignore.
n8n runs on your infrastructure. You can install it on a $12/month DigitalOcean droplet or run it on AWS. This means your workflow execution costs don’t increase when you scale from 100 to 10,000 workflows per month. Companies processing customer data under GDPR or HIPAA requirements can keep everything on their own servers instead of routing sensitive information through a third-party automation platform.
Who Should Not Use n8n
If you don’t have someone on your team comfortable with basic server management, n8n’s self-hosted version will create more problems than it solves. The cloud-hosted version starts at approximately $20/month, but you’ll quickly hit execution limits that push you into the $50-100/month range. At that price point, you’re competing with Zapier or Make.com, which have more beginner-friendly interfaces.
Businesses under ten people who haven’t yet standardized their software stack should focus on picking better tools first. n8n is what you use after you’ve committed to specific platforms and need them to work together. It’s not a replacement for choosing integrated software from the start.
| Business Type | Recommended Approach | Why |
|---|---|---|
| Startup, 3-8 people | Use Zapier or built-in integrations | Your workflows will change monthly; don’t over-engineer |
| Established team, 10-30 people | Consider n8n if you have technical staff | Cost savings start to matter at this scale |
| Regulated industry (healthcare, finance) | n8n self-hosted | Data compliance requirements justify the setup complexity |
The Verdict by Business Size
n8n works for established small businesses with at least one technically capable person on staff and a clear list of integration problems to solve. If you’re currently paying Zapier $150+/month and hitting task limits, n8n’s self-hosted version will pay for itself in three months. If you’re just starting to automate and still figuring out your core tools, you’re adding infrastructure before you need it.
[CTA: Try n8n]
Key takeaways
- Self-hosting eliminates per-workflow costs but requires someone comfortable managing servers and troubleshooting deployment issues
- The 400+ integrations and custom webhook capabilities matter most for businesses using industry-specific software that mainstream automation tools don’t support
- Companies under ten people usually spend more time maintaining n8n workflows than they save—standardize your software stack first, automate second
StackSmall – June 2026