Workflow automation that wires apps and AI nodes
n8n is a fair-code workflow platform (Sustainable Use License). A visual canvas for webhooks, cron, existing systems and AI nodes — Docker self-host or official Cloud.
Editorial update 2026-09-05; GitHub statistics snapshot 2026-10-19.
Turn synthetic inquiries into review-only results
Download, inspect and compare. The tutorial specifies isolation and the CLI evidence boundary; no sending or actual approval.
Prepare synthetic files and a disposable instance
Obtain test authorization. Use only the shipped 12 cases, not production data, credentials or website dependencies. Documented UI steps are not verified GUI behavior.
workflow.json + fixtures.json + expected-output.jsonInspect the three nodes before import
Only Manual Trigger and two all-items JavaScript Code nodes. CLI --separate generated a fresh ID in the tested version; see the tutorial for the full environment and commands.
Manual Trigger → Synthetic Fixtures → Review Only - Never SendCompare every item and stop for review
Actual CLI output and pairing matched all 12 expected items: 2 drafts, 1 missing-information, 3 policy-review, 6 invalid-input. No sending; labels do not mean a person reviewed anything.
requiresHumanReview: true
sendAllowed: falsePitfalls
Not an MIT license
Internal self-hosting is fine; a paid multi-tenant n8n host hits the Sustainable Use License. Read LICENSE.md before you sell it.
Don't overload AI Agent nodes
Define permissions, inputs, failures and tests before adding tools for a task. Tool count does not establish reliability. This exercise uses no model or external tool, so review routing can be checked separately.
Do not expose a local test configuration
Follow official deployment guidance for authentication, HTTPS, backups and WEBHOOK_URL behind a proxy. Choose database and queue arrangements for your requirements; a database name alone does not establish production suitability.
Beside Dify & Zapier
These are documented emphases, not exclusive capabilities. Choose by the task, verified features and deployment requirements rather than treating positioning as a feature boundary.
| Tool | License | Surface | Positioning | Best for |
|---|---|---|---|---|
| n8n | Fair-code · SUL | Visual workflows | App integrations + cron/webhooks + AI nodes | Repetitive ops, self-hosted automation |
| Dify | Apache-2.0 + conditions | AI app builder | RAG, chat apps, model providers | SME PoC / knowledge Q&A |
| Zapier | Proprietary SaaS | No-code automation | Huge SaaS catalog, fully hosted | Non-ops business teams |
Official Directory
Official
- Official site (n8n.io)
Product, Cloud and self-hosting entry.
- GitHub repository
Source. Fair-code, Sustainable Use License.
Docs & Install
- Documentation
Docker install, nodes, workflows and hosting.
- Docker install docs
Official recommended self-host install.
Community
- Community forum
Q&A and troubleshooting.
Related
- n8n Cloud
Official hosted option if you don't want to run servers.
Latest Updates
2026-09-04 · GitHub · n8n-io/n8n
n8n keeps shipping: visual workflows + native AI nodesFair-code workflow platform, self-host or Cloud. GitHub lists 400+ integrations. 200k+ stars.
LaoJin's Pick
FAQ
- What is n8n?
- n8n is a fair-code workflow automation platform: a visual canvas that wires apps, webhooks, cron and AI nodes. Self-host or use official Cloud.
- Is n8n open source? Is it free?
- It's under the Sustainable Use License (fair-code), not Apache/MIT. Self-hosting for your own internal automation is allowed; selling it as a competing multi-tenant host needs a commercial license. Cloud is billed separately.
- How do I install n8n?
- Official docs recommend Docker. Create a volume, run `n8nio/n8n`, open http://localhost:5678. For production follow the official Docker/Compose guide — don't expose 5678 raw.
- n8n vs Dify vs Zapier?
- Repetitive ops, webhooks and scheduled sync often start with n8n; knowledge Q&A and chat apps often start with Dify; fully hosted SaaS integrations often start with Zapier. These are emphases, not exclusive features; stacks can combine them.
- What was actually tested in the inquiry exercise?
- The synthetic workflow was CLI-imported, exported and executed in disposable n8n 2.37.10 / Node 24.20.0. All 12 outputs and pairs matched the independent oracle. The editor returned 404 in that npm setup and is unverified; no customer, model, delivery or business-performance test occurred.
Evidence: version-specific CLI run · GUI unverified
12 synthetic inquiries, each paired with a review result
n8n 2.37.10 / Node 24.20.0 output and pairing matched the independent oracle. No model, customer data or sends; a queue label does not deliver a review task.
Follow the complete walkthrough →Connecting an existing operation? Start with field names, source permissions and who may approve—not raw customer records.
Discuss input and review requirementsView service scopeCite This Hub
We encourage you to capture this hub into your knowledge base, research, or feed it straight to an AI agent under CC BY 4.0.
How this hub stays current
Version and links live in src/content/n8n.ts; star snapshots sync via GitHub API.