What it actually does
n8n is a visual workflow builder where you drag nodes onto a canvas, connect them, and drop into custom code whenever the visual layer runs out. It has been around since 2019, which in this catalog makes it genuinely mature.
The AI capabilities are native rather than bolted on: multi-step agents, tool use, human approval steps, and your own data and models. It connects to OpenAI, Anthropic, Google, or open-source models, and switching providers does not mean rearchitecting. It is both an MCP client and an MCP server.
For most teams this is the honest first stop. If your automation is "when a form is submitted, enrich the lead, score it, write it to the CRM, and post to Slack", n8n does that today with no custom code and you can self-host it so the data never leaves your infrastructure.
The licence is fair-code rather than fully open source — worth reading if you plan to build a commercial product on top of it.
Who it's for
- 01
Any team automating a workflow that touches more than two SaaS tools
- 02
Ops leads who want to build automation without waiting for engineering
- 03
Companies that need self-hosting for data residency or compliance
- 04
Engineers who want a visual layer but refuse to be trapped in one
Where it earns its keep
- Lead routing: capture, enrich, score, write to CRM, notify the owner
- Scheduled reporting that pulls from several systems into one digest
- Human-in-the-loop approvals sitting between an AI step and a real action
- Syncing data between tools that have no native integration
- Prototyping an automation in an afternoon before deciding whether to build it properly
Use it, or skip it
Reach for it when
- The workflow is integration-heavy and the logic is moderate
- Non-engineers need to see and modify the automation
- Self-hosting is required
- You want to validate an automation before investing in custom code
Skip it when
- The logic is complex enough that a visual graph becomes harder to read than code
- You are building a commercial product on top of it — check the fair-code licence first
- Extreme throughput or latency requirements; this is orchestration, not a data pipeline engine
- Your workflow is one API call — a script is simpler
10 automations
Ideas, not tutorials. Each one is work a team does by hand today.
- 01Sales
Inbound lead pipeline
Form submission triggers enrichment, ICP scoring, CRM write, and a Slack ping to the owning rep within a minute.
- 02Founders
Weekly founder digest
Pull revenue, signups, churn, and support volume from four systems into one scheduled message every Monday.
- 03Marketing
Content publishing chain
Draft, route for human approval, then publish to blog, newsletter, and social on approval.
- 04Operations
Churn early warning
Watch usage drop-offs and support sentiment together, and open a task for success when both trend down.
- 05Finance
Invoice reconciliation
Match incoming invoices against purchase orders and escalate only the mismatches to finance.
- 06Support
Support ticket triage
Classify incoming tickets, attach account context, and route to the right queue with a suggested reply.
- 07Marketing
Competitor change alerts
Poll competitor pricing and changelog pages, diff them, and post material changes to a channel.
- 08Operations
Onboarding checklist automation
When a deal closes, create the accounts, send the welcome sequence, and schedule the kickoff automatically.
- 09Operations
Approval-gated AI actions
Put a human approval node between any AI-generated output and the action that sends it to a customer.
- 10Operations
Data sync between silos
Keep two systems with no native integration in sync on a schedule, with conflict reporting.
Want one of these running by Friday?
LimeDock builds these as real workflows inside your stack — deployed to your cloud, wired into your Slack and CRM, with the code in your repo. You pay a build fee and your own API keys, nothing else.
Source
Repository stats were read from the GitHub API and reflect the last time we refreshed this entry. The editorial breakdown above is LimeDock’s own analysis — we are not affiliated with n8n-io.
https://github.com/n8n-io/n8n