Deploy n8n (Queue Mode) - Pinned, Tested, 3.0-Ready
Pinned, tested n8n in queue mode with worker, Postgres and Redis
Just deployed
/home/node/.n8n
Just deployed
/var/lib/postgresql/data
Redis
Just deployed
/data
n8n-worker
Just deployed
Deploy and Host n8n (Queue Mode) on Railway
n8n in queue mode - main, worker, PostgreSQL and Redis - pinned to a release we tested (n8nio/n8n 2.42.3), with the n8n 3.0 defaults already set, your owner account created from variables (no open setup page) and a generated encryption key shared by main and worker.
About Hosting n8n (Queue Mode)
n8n is a workflow automation platform: connect apps and APIs, run schedules and webhooks, add AI steps, with your own logic in Code nodes. This template runs it in queue mode: the main service serves the editor, the API and webhooks, and a separate worker runs the executions, with Redis as the job queue and PostgreSQL storing workflows, encrypted credentials, executions and binary data. The version is pinned, so a redeploy does not jump to n8n 3.0 (October 2026) on its own - you upgrade when you decide. A fresh n8n normally lets the first visitor create the owner; here the owner is created at start from N8N_OWNER_EMAIL and a generated password. Tested on a fresh throw-away VM: setup page closed, wrong password refused, a webhook executed by the worker, login after restart.
Common Use Cases
- Automate work between apps and APIs (CRM, e-mail, Slack/Telegram, sheets, databases) with webhooks and schedules
- Run AI agent and LLM workflows with your own API keys, with a worker so long jobs do not block the editor
- Move an existing n8n to a pinned, tested setup before the n8n 3.0 upgrade
Dependencies for n8n (Queue Mode) Hosting
- PostgreSQL (workflows, encrypted credentials, executions, binary data)
- Redis (the job queue between main and worker)
Deployment Dependencies
- Upstream image: https://hub.docker.com/r/n8nio/n8n (2.42.3, pinned by digest)
- n8n docs: https://docs.n8n.io/hosting/
- n8n v3.0 breaking changes: https://docs.n8n.io/changelog/v30-breaking-changes/
- Template source + test result: https://github.com/localhavenstore/railway-n8n
- Guide - upgrading n8n on Railway to 3.0: https://localhavenstore.github.io/guides/n8n-railway-3-0-upgrade.html
Why Deploy n8n (Queue Mode) on Railway?
Railway runs the four services, networking, HTTPS domain and backups for you, so you get a production-style n8n (editor + worker + queue + database) without managing a server. This template adds what most n8n templates skip: a pinned, tested version, the owner created from variables, a generated encryption key shared by both services, and the n8n 3.0 defaults.
New to Railway? Our referral link: https://railway.com?referralCode=j8As-k - you get USD 20 of credit, we get a share of your usage. Not affiliated with Railway or n8n GmbH. Made with AI assistance and tested by us (Localhaven).
Template Content
N8N_OWNER_EMAIL
REQUIRED: your login e-mail. The owner account is created from it at start (no open setup page).
Redis
redis:8.2n8n-worker
localhavenstore/railway-n8n