Skip to main content
n8n is a source-available workflow automation tool — a self-hosted Zapier alternative with hundreds of integrations. You build workflows visually by chaining nodes, and trigger them on a schedule, a webhook, or manually. This guide covers configuring n8n on Suji. Check the version and release notes shown in the marketplace before installing or upgrading. n8n is maintained upstream; Suji provides the marketplace packaging.

​
Before you install

Nothing to prepare — no API keys or tokens. You’ll set up your admin account in the browser after install, and add credentials for individual integrations from inside n8n as you build workflows.
The packaged n8n version uses an interactive owner-account setup on first run. There is no generated password and no credentials file — the first person to open the URL creates the owner account, so set yours up immediately after install (see below).

​
Install

Dashboard → Apps → n8n → Install: There are no secrets to fill in. A Small VPS with spare capacity is a starting point for light workflows. The template limits n8n to 1 GiB; execution size and concurrency determine actual needs. See Recommended size. Click Deploy. Follow deployment progress until the install is running. Startup time varies with image downloads, initialization and VM capacity. You’ll get a public URL like https://n8n-<random>.suji.fr — that’s the n8n editor, served over HTTPS through the tunnel.

​
First connection — create your owner account

  1. Open the install URL (https://n8n-<random>.suji.fr).
  2. n8n shows a Set up owner account screen on first run.
  3. Enter your email, name, and a password. This becomes your admin login.
  4. You’re taken straight into the workflow editor.
The URL is public the moment the install is running. Until you complete the owner setup, anyone who reaches it can claim the owner account. Do the setup right after deploy — don’t leave a fresh install unclaimed.
On later visits the same URL shows a Sign in screen instead. Forgot the password? Reset it from a shell — see Troubleshooting.

​
Build your first workflow

Inside the editor:
  1. Click Add first step and pick a trigger (Manual, Schedule, or Webhook).
  2. Add action nodes and connect them by dragging between the node dots.
  3. For nodes that talk to an external service (Slack, Google, an HTTP API…), n8n prompts you to add a credential — these are stored encrypted on the install’s volume.
  4. Click Execute workflow to test, then publish or activate the workflow using the control shown by your n8n version so its production triggers can run.

​
Webhooks & external triggers

Webhook and “Wait for webhook” nodes generate a callback URL using the install’s public address, e.g. https://n8n-<random>.suji.fr/webhook/.... Give that URL to the external service.
  • Test vs Production URLs — the test URL listens while you explicitly run a webhook test; the production URL belongs to the published/active workflow. Use the production URL for real integrations.
  • OAuth-based credentials (Google, etc.) use the same public host for their redirect URL — register that redirect in the provider’s console.

​
Day-to-day management

​
Troubleshooting

Reset it from the dashboard’s per-app Terminal (pick n8n):
This resets user management to its pre-setup state and removes user accounts; it is not a single-user password change. Back up first and check n8n --help plus the documentation for your installed version before running it.
Always reach n8n through its https://<subdomain>.suji.fr URL. n8n sets a secure cookie; if you tunnel directly to the plain-HTTP container port, the browser refuses the cookie and login fails. The public Suji URL uses HTTPS; the tunnel forwards to the app’s internal HTTP service.
Check the URL shown by the Webhook node before registering it externally. The template does not set an explicit WEBHOOK_URL. If the generated host is wrong, set WEBHOOK_URL to your full public HTTPS address in the install’s Variables tab and click Apply changes.
n8n isn’t reachable through the tunnel yet. Usually it’s still starting — wait ~30 s and retry, especially right after an upgrade. If it persists, the Logs tab shows why the container isn’t up.

​
Where things live

Saved credentials are encrypted with the key in /home/node/.n8n/config. If you lose the volume, you lose that key and can’t decrypt your stored credentials — you’d have to re-enter them. Keep this in mind before uninstalling: choose keep data during uninstall if you want to preserve workflows and credentials.
  • The template declares 512 MiB minimum and 1 GiB recommended memory, with a 1 GiB container limit. These are starting estimates; a workflow processing large payloads can exceed them.
  • Memory/CPU pressure comes from what your workflows do — heavy data transforms, large HTTP payloads, or many concurrent executions. Review both VM capacity and the container’s memory limit for large or concurrent executions.
  • If you run other apps on the same VM, remember the VM’s total CPU/memory is shared.

​
Licence

n8n’s upstream licence includes Sustainable Use and Enterprise terms. Check the terms for your intended use and any paid features; hosting on Suji does not grant an n8n commercial licence.

​
Reporting issues