2019-06-23 13:35:23 +03:00
|
|
|
# n8n - Workflow Automation Tool
|
|
|
|
|
2019-07-26 14:11:21 +03:00
|
|
|
![n8n.io - Workflow Automation](https://raw.githubusercontent.com/n8n-io/n8n/master/docs/images/n8n-logo.png)
|
2019-06-23 13:35:23 +03:00
|
|
|
|
2019-06-27 19:45:28 +03:00
|
|
|
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.
|
2019-06-23 13:35:23 +03:00
|
|
|
|
2019-07-26 14:11:21 +03:00
|
|
|
<a href="https://raw.githubusercontent.com/n8n-io/n8n/master/docs/images/n8n-screenshot.png"><img src="https://raw.githubusercontent.com/n8n-io/n8n/master/docs/images/n8n-screenshot.png" width="550" alt="n8n.io - Screenshot"></a>
|
2019-06-23 21:56:42 +03:00
|
|
|
|
2019-06-23 13:35:23 +03:00
|
|
|
Is still in beta so can not guarantee that everything works perfectly. Also
|
|
|
|
is there currently not much documentation. That will hopefully change soon.
|
|
|
|
|
2019-08-09 12:19:36 +03:00
|
|
|
|
|
|
|
|
2019-06-27 19:45:28 +03:00
|
|
|
## 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:
|
|
|
|
|
|
|
|
[https://www.youtube.com/watch?v=ePdcf0yaz1c](https://www.youtube.com/watch?v=ePdcf0yaz1c)
|
|
|
|
|
2019-06-23 13:35:23 +03:00
|
|
|
|
2019-08-09 12:19:36 +03:00
|
|
|
|
2019-06-23 13:35:23 +03:00
|
|
|
## Usage
|
|
|
|
|
2019-06-24 14:21:07 +03:00
|
|
|
Information about how to install and use it can be found in the cli package [here](https://github.com/n8n-io/n8n/tree/master/packages/cli)
|
2019-06-23 13:35:23 +03:00
|
|
|
|
2019-06-24 14:21:07 +03:00
|
|
|
And information about how to run it in Docker [here](https://github.com/n8n-io/n8n/tree/master/docker/images/n8n)
|
2019-06-23 13:35:23 +03:00
|
|
|
|
|
|
|
|
2019-08-09 12:19:36 +03:00
|
|
|
|
2019-06-23 13:35:23 +03:00
|
|
|
## Development Setup
|
|
|
|
|
2019-08-14 09:30:54 +03:00
|
|
|
A guide how to set everything up can be found in the file [CONTRIBUTING.md](CONTRIBUTING.md)
|
2019-06-23 13:35:23 +03:00
|
|
|
|
2019-08-09 12:19:36 +03:00
|
|
|
|
|
|
|
|
2019-06-23 13:35:23 +03:00
|
|
|
## Start
|
|
|
|
|
|
|
|
Execute: `npm run start`
|
|
|
|
|
|
|
|
|
2019-08-09 12:19:36 +03:00
|
|
|
|
|
|
|
## Hosted n8n
|
|
|
|
|
|
|
|
If you are interested in a hosted version of n8n on our infrastructure please contact us via:
|
|
|
|
[hosting@n8n.io](mailto:hosting@n8n.io)
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-08-09 18:11:41 +03:00
|
|
|
## 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.
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-06-23 13:35:23 +03:00
|
|
|
## License
|
|
|
|
|
2019-06-24 14:21:07 +03:00
|
|
|
[Apache 2.0 with Commons Clause](https://github.com/n8n-io/n8n/blob/master/packages/cli/LICENSE.md)
|