Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.
Find a file
2019-08-28 17:25:19 +02:00
docker 📚 Improve README text 2019-08-26 22:09:31 +02:00
docs 📚 add an awesome collection of n8n workflows 2019-08-21 22:47:27 +02:00
packages Return response code 500 in case workflow fails 2019-08-28 17:25:19 +02:00
.editorconfig Initial commit to release 2019-06-23 12:35:23 +02:00
.gitignore Initial commit to release 2019-06-23 12:35:23 +02:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2019-06-23 17:48:38 +02:00
CONTRIBUTING.md CONTRIBUTING : add TOC 2019-08-21 23:18:09 +02:00
lerna.json Initial commit to release 2019-06-23 12:35:23 +02:00
LICENSE.md Rename LICENSE files to LICENSE.md 2019-06-23 17:55:43 +02:00
package.json 📚 Update development cycle documentation and add placeholder tests 2019-08-14 13:45:18 +02:00
README.md 📚 wording and layout on the main README 2019-08-21 23:01:42 +02:00

n8n - Workflow Automation Tool

n8n.io - Workflow Automation

n8n is a free node based "Open Source" (with Commons Clause) Workflow Automation Tool. It can be self-hosted, easily extended, and so also used with internal tools.

n8n.io - Screenshot

Is still in beta so can not guarantee that everything works perfectly. Also is there currently not much documentation. That will hopefully change soon.

Demo

📺 A short demo (< 3 min) which shows how to create a simple workflow which automatically sends a new Slack notification every time a Github repository received or lost a star.

Usage

Start

Execute: npm run start

Hosted n8n

If you are interested in a hosted version of n8n on our infrastructure please contact us via: hosting@n8n.io

What does n8n mean and how do you pronounce it

Short answer: It means "nodemation"

Long answer: I get that question quite often (more often than I expected) so decided it is probably best to answer it here. While looking for a good name for the project with a free domain I realized very fast that all the good ones I could think of were already taken. So, in the end, I choose nodemation. "node-" in the sense that it uses a Node-View and that it uses Node.js and "-mation" for "automation" what the project is supposed to help with. Did however not like how long the name was and could not imagine writing something that long every time in the CLI. That is when I then ended up on "n8n". Sure does not work perfectly but does neither for Kubernetes (k8s) and did not hear anybody complain there. So I guess it should be ok.

Development Setup

Have you found a bug 🐛 ? Or maybe you have a nice feature to contribute ? The CONTRIBUTING guide will help you get your development environment ready in minutes.

License

Apache 2.0 with Commons Clause