n8n (pronounced n-eight-n) helps you to interconnect every app with an API in the world with each other to share and manipulate its data without a single line of code. It is an easy to use, user-friendly and highly customizable service, which uses an intuitive user interface for you to design your unique workflows very fast. Hosted on your server and not based in the cloud, it keeps your sensible data very secure in your own trusted database.
Follow these steps to get the add-on installed on your system:
Important: Make sure you've added this addon repository to your Home Assistant addon library: https://github.com/Rbillon59/hass-n8n
- Navigate in your Home Assistant frontend to Supervisor -> Add-on Store.
- Find the "hass-n8n" add-on and click it.
- Click on the "INSTALL" button.
timezone: Europe/Berlin
env_vars_list: []
cmd_line_args: ""List of the n8n environment variables. You can add as many environment variables as you want to the list through the UI. The format is the following:
SOME_ENVIRONMENT_VARIABLE: some-value (the regular expression is ^[A-Z_0-9]+: .*$ )
All the available environment variables are available here : https://docs.n8n.io/hosting/environment-variables/environment-variables/
The command line to start n8n. If you want to use a custom command line, you can use this variable.
In n8n you can add external node modules by setting the NODE_FUNCTION_ALLOW_EXTERNAL environment variable with the list of npm packages you need.
For example, to install the lodash and the moment packages, in the UI, set the env_vars_list variable to:
NODE_FUNCTION_ALLOW_EXTERNAL: lodash,momentThe addon is presented via a Home Assistant Ingress for additional security.
This means that in addition to n8n's credentials, n8n can't be accessed without being authenticated with Home Assistant as well, even when accessing it remotely.
If you use Nabu Casa remote URL, the addon can't fetch your Nabu Casa remote URL programmatically, in that case, you need to set the EXTERNAL_URL environment variable to your Nabu Casa remote URL for things like OAuth2 credentials to work properly (setting the right redirect URLs).
If you are using a manual external URL, Ingress traffic is not relayed via this in a safe manner. In that case, you need to expose port 5678 of the container to a certain port (for instance, 5678) on Home Assistant, under the "Network" section of the configuration tab of the addon.
Webhooks, triggers and the n8n API can't go via an Ingress, since having Home Assistant authentication on top of it would break the webhook (they need to be publically accessible and unauthenticated).
For this reason, the addon exposes all webhook or API traffic on port 8081.
For the n8n API, webhooks and some webhook-based triggers to work properly, you need to open up a tunnel for port 8081 to the internet via the Cloudflared addon or something similar.
When done, set the WEBHOOK_URL environment variable to the URL of the tunnel.
If you want to, you can expose n8n without requiring to go through the Ingress. This is done in the "ports" section of the "configuration" tab of the addon, for port 5678. Note that you need to enable "hidden port bindings" for that port to show up. It is not exposed by default.
Just start the addon and head to the addon's web UI.
https://docs.n8n.io https://docs.n8n.io/getting-started/tutorials.html
This addon is published under the Apache 2 license. Original author of the addon's bundled software is n8n.
Got questions?
You can open an issue on GitHub.
Repository: https://github.com/Rbillon59/hass-n8n
This can happen depending on which browser you are using. To work around it, copy the URL of the popup window and paste it into a new tab in the main window. Then the authorization will complete.
![@renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=64&v=4){kind=small}
![@github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=64&v=4){kind=small}
![@dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=64&v=4){kind=small}
