Deploy N8N (w/ task runners)

Deploy and Host n8n with Task Runners on Railway

n8n is a powerful workflow automation platform for connecting APIs, applications, databases, AI models, and business processes. This template pairs n8n with PostgreSQL and dedicated external Task Runners, providing a cleaner architecture for executing Code node tasks separately from the main n8n process.

About Hosting n8n with Task Runners

This template deploys a self-hosted n8n stack with PostgreSQL for persistent application data and dedicated n8n Task Runners for isolated task execution.

The Main service hosts the n8n editor, APIs, webhooks, scheduling, and workflow orchestration. PostgreSQL stores workflows, credentials, execution history, and other persistent n8n data. The separate Task Runners service connects to n8n's task broker and executes supported Code node tasks outside the main n8n process.

Unlike n8n Queue Mode deployments, this template does not require Redis or separate workflow workers, keeping the infrastructure smaller while still providing dedicated task execution.

Included Architecture

Common Use Cases

• Build AI-powered workflows and AI agents
• Connect APIs, databases, SaaS applications, and internal systems
• Run JavaScript and supported Python tasks through dedicated Task Runners
• Automate backend processes and API integrations
• Build webhook-driven automation
• Process and transform data inside workflows
• Automate CRM, notifications, reporting, and business operations
• Connect LLMs and AI services to existing applications
• Build scheduled and event-driven workflows
• Self-host automation while keeping control of your data

n8n vs Other Workflow Automation Platforms

n8n is particularly well suited to technical teams that need flexible workflow logic, API integrations, custom code, AI automation, and control over where their automation infrastructure runs.

Dependencies for n8n with Task Runners Hosting

• n8n Main — workflow editor, API, webhooks, scheduling, and orchestration
• n8n Task Runners — dedicated external execution environment for supported Code node tasks
• PostgreSQL — persistent relational database
• Railway Private Networking — communication between Main, Runners, and PostgreSQL
• Shared Runner Authentication Token — securely authenticates Task Runners with the n8n task broker
• n8n Encryption Key — protects stored credentials and encrypted application data

Deployment Dependencies

• n8n Documentation: https://docs.n8n.io/
• n8n Task Runners: https://docs.n8n.io/hosting/configuration/task-runners/
• Task Runner Environment Variables: https://docs.n8n.io/hosting/configuration/environment-variables/task-runners/
• n8n Database Configuration: https://docs.n8n.io/deploy/host-n8n/configure-n8n/choose-n8ns-database
• n8n Docker Deployment: https://docs.n8n.io/deploy/host-n8n/install-options/install-with-docker
• Railway n8n Guide: https://docs.railway.com/guides/n8n
• Railway Private Networking: https://docs.railway.com/networking/private-networking

Implementation Details

This template uses external Task Runner mode.

                    ┌──────────────┐
                    │    Users     │
                    └──────┬───────┘
                           │
                           ▼
                    ┌──────────────┐
                    │   n8n Main   │
                    │ UI / API /   │
                    │ Webhooks     │
                    └──────┬───────┘
                           │
               ┌───────────┴────────────┐
               │                        │
               ▼                        ▼
       ┌──────────────┐         ┌──────────────┐
       │ PostgreSQL   │         │ Task Broker  │
       │ Persistent   │         │    :5679     │
       │ Data         │         └──────┬───────┘
       └──────────────┘                │
                                       ▼
                               ┌──────────────┐
                               │ Task Runners │
                               │ n8nio/runners│
                               └──────────────┘

The Main service runs n8n using PostgreSQL as its database backend and exposes the Task Runner broker over Railway's private network.

The Runners service uses the official:

n8nio/runners

container image and connects privately to the task broker running on the Main service.

A shared N8N_RUNNERS_AUTH_TOKEN is used to authenticate communication between n8n and its external Task Runners.

This architecture intentionally does not use:

Redis
n8n Worker
EXECUTIONS_MODE=queue

Task Runners and Queue Mode solve different problems. Task Runners provide a separate execution environment for supported tasks such as Code node execution, while Queue Mode distributes complete workflow executions across n8n workers using Redis.

This makes the template a useful middle ground between a basic single-container n8n deployment and a larger Queue Mode deployment with Redis and multiple workers.

Why Use External Task Runners?

External Task Runners are particularly useful when workflows rely heavily on custom JavaScript or Python logic while keeping the main n8n application process focused on workflow orchestration.

Why Deploy n8n with Task Runners on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying n8n with Task Runners on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.