Application catalogue
n8n
Workflow automation you host yourself, with its encryption key and address set for you.
Updated
n8n is workflow automation you host yourself: you build workflows in its own editor, connecting the services it integrates with. Cloud creates it from the catalogue with its storage, its encryption key and its address settings in place. n8n's own documentation is at n8n.io, external link.
| Setting | Value |
|---|---|
| Image | docker.n8n.io/n8nio/n8n:2.40.3 |
| Port | 5678 |
| Volume | State, at /home/node/.n8n |
| Smallest size | Small |
| Values you are asked for | None |
The image is pinned to an exact release because n8n publishes no tag that follows a major version. The catalogue moves to a newer release only by a deliberate change, and a service you already run stays on the image it was created with.
Run n8n from the catalogue goes from an empty project to the n8n editor step by step.
Set it up
Create it
On a project, press Add a service, then Create on n8n under Services. Pick a size, keep or change Automatic backup, and press Create service.
Deploy
Press Deploy. When the deployment is Done, Cloud gives the service an address under the platform domain if it has no domain yet, and sends n8n that address in its environment.
Open the editor
Once the domain reads HTTPS active, press Visit on the service and continue in n8n itself.
Its environment
Until the service has a domain, the three address values are not sent and n8n's own defaults stand. They follow the platform domain while the service has one, even after you add your own domain. To have n8n use your own domain in its webhook and editor addresses, set N8N_HOST, N8N_WEBHOOK_URL and N8N_EDITOR_BASE_URL yourself on the Environment section, or remove the platform domain, after which they follow your oldest custom domain.
To use another time zone or any other value, set the same name on the Environment section; yours is used from then on.
Keep the encryption key
Do not remove or change N8N_ENCRYPTION_KEY once workflows hold credentials: n8n cannot read credentials stored under a different key. Keep a copy of it somewhere safe outside Cloud as well: the credentials in any copy of n8n's data are unreadable without it.
Its data
n8n keeps its workflows, credentials and settings under /home/node/.n8n, on the State volume Cloud attaches when the service is created, so they survive deploys.
The automatic backup of that volume is an archive of the whole volume. n8n is stopped while each archive is taken. An archive cannot be downloaded from the console, and Restore is not available yet, so keep your own copy of workflows that matter by exporting them from n8n. Backups and Volumes cover both.