--- title: "Deploy n8n Outreach" description: "lead enrichment and email sequences" category: "Automation" url: https://railway.com/deploy/n8n-outreach --- # Deploy n8n Outreach lead enrichment and email sequences **[Deploy n8n Outreach on Railway](https://railway.com/template/n8n-outreach)** Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/n8n-outreach/manifest.json - **Creator:** onepush - **Category:** Automation ## Template content ### n8n - **Image:** n8nio/n8n:2.36.8 - **Health check:** /healthz - **Public domain:** Yes ### Postgres https://devicons.railway.app/i/postgresql.svg - **Image:** ghcr.io/railwayapp-templates/postgres-ssl:18 ### Redis https://cdn.sanity.io/images/sy1jschh/production/0ce0bfdcfbdbf69662b1116671f97c2dd788b655-157x157.svg - **Image:** redis:8.2 - **Start command:** `/bin/sh -c "rm -rf $RAILWAY_VOLUME_MOUNT_PATH/lost+found/ && exec docker-entrypoint.sh redis-server --requirepass $REDIS_PASSWORD --save 60 1 --dir $RAILWAY_VOLUME_MOUNT_PATH"` ### n8n-worker - **Image:** n8nio/n8n:2.36.8 - **Start command:** `n8n worker` - **Health check:** /healthz ## Documentation # Deploy and Host self hosted n8n Outreach (Open-Source Outreach Automation) on Railway n8n Outreach turns a Google Sheet into a lean, self-hosted cold email engine: enrich leads through webhooks, build multi-step Gmail sequences that respect sending limits, and scale volume with queue-mode workers. Deploying on Railway gives you Postgres, Redis, and horizontal worker scaling without managing infrastructure, so high-volume sends stay reliable and audit-ready. Self-host n8n Outreach on Railway in queue mode with an n8n editor, dedicated worker, PostgreSQL, and Redis Bull so webhooks and long workflows stay off the UI—flat infrastructure cost instead of per-task SaaS billing. ## About Hosting n8n Outreach open-source software on Railway (self hosted n8n template) n8n Outreach is a self-hosted n8n workflow stack for lead enrichment and email sequences. It uses the official n8n Docker image in queue mode, where an editor writes executions to Postgres and Redis Bull queues, and one or more worker containers pull jobs to call enrichment APIs, update spreadsheets, and send Gmail messages. Because everything runs on Railway, you can scale workers during a campaign spike, keep execution data in your own database, and trigger enrichment webhooks without a third-party SaaS gateway. The workflow pattern is simple: a Sheet row is enriched by Clearbit, Hunter, or a custom endpoint, then the Gmail node sends a personalized email, logs the outcome, and schedules the next step. Queue mode prevents long-running enrichment calls from blocking the editor, and multiple workers let you parallelize sequences across different domains or inboxes while staying within Gmail’s daily sending quotas. This is a practical alternative to closed outreach tools because workflow logic, credentials, and recipient data stay under your control. ## Why Deploy n8n Outreach, the Instantly alternative on Railway (Railway Free Trial) Instantly is popular for cold email but locks you into per-seat and sending-volume pricing, with limited visibility into the underlying queue or retry logic. n8n Outreach flips that model: the fair-code n8n Community Edition is free, and you only pay for Railway infrastructure. You get the same sequence builder, lead rotation, and deliverability controls, but you can add custom enrichment steps, branch on webhook payloads, and store every execution log in Postgres. Railway’s free trial lets you test the full queue-mode setup before committing, and there is no per-contact fee when you send 10,000 or 100,000 emails as long as Gmail’s limits allow it. 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 Outreach 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. ### Railway vs Other Hosting Providers and VPS for n8n Outreach self hosting | Provider | Setup Effort | Scaling Workers | Managed Postgres/Redis | Cost Predictability | Best For | |---|---|---|---|---|---| | Railway | One-click template, env vars pre-mapped | Horizontal with service replicas | Built-in, auto-backup | Pay-as-you-go, trial credit | Fast queue-mode deployment without DevOps | | DigitalOcean | Manual Droplet + Docker Compose | Manual resize or load balancer | Separate managed DB costs extra | Fixed monthly droplet | Teams comfortable with SSH and systemd | | AWS | ECS/Fargate or EC2, IAM, VPC | Auto-scaling policies but complex | RDS + ElastiCache add significant cost | Highly variable, can balloon | Enterprise with existing AWS footprint | | Hetzner | Bare metal or cloud VM, manual setup | Manual or k3s cluster | Self-managed Postgres/Redis | Very low, predictable | Budget self-hosters willing to manage servers | If queue mode is overkill, Railway also hosts the [cheapest n8n without queue mode](https://railway.com/deploy/n8n) for lightweight single-instance automation. ## Common Use Cases for hosted n8n Outreach - Sheet-to-Gmail drip sequences: every new Google Sheets row becomes a lead that enters a multi-touch sequence with delays, conditions, and stop-on-reply logic. - Lead enrichment webhooks: Clearbit, Hunter, Apollo, or custom APIs return company size, tech stack, and verified emails before the first touch. - Multi-domain sending: separate workers per domain or inbox to keep daily Gmail volume under 200-400 sends per address. - Event-triggered outreach: webhook from a signup, trial, or abandoned cart enriches the contact and sends a personalized follow-up in minutes. - CRM and Slack sync: after each send, update HubSpot, Pipedrive, or Slack with open, reply, and bounce data. - Inbound reply routing: parse Gmail replies with AI nodes, tag sentiment, and move leads to a different sequence. ## Dependencies for n8n Outreach Docker hosted on Railway Queue mode is not optional for high-volume outreach. The editor alone with SQLite cannot process parallel sequences, and the n8n documentation explicitly states SQLite does not support queue mode. You need Postgres for workflow and execution metadata, Redis for Bull queue coordination between editor and workers, and persistent storage for n8n’s config and encryption key. Railway handles all three as services attached to the template, and the only manual step is setting environment variables so editor and workers share the same database, Redis, and encryption key. ### Deployment Dependencies for Managed n8n Outreach Service (Outreach Automation) Railway provisions a Postgres database and a Redis instance when you deploy the n8n Outreach stack. The editor service uses the official n8n image and listens on port 5678. One or more worker services run the same image with the command `n8n worker`. Both editor and worker connect to Postgres through `DB_TYPE=postgresdb` and to Redis through the Bull queue configuration. A shared volume mounted at `/home/node/.n8n` stores credentials, encryption keys, and installed community nodes. Railway’s internal networking lets editor and workers reach each other over service hostnames, and you can expose the editor publicly for webhook URLs while keeping workers private. ### Implementation Details for n8n Outreach (Using n8n official docker image) Use image `n8nio/n8n:2.36.8` for both editor and worker. Editor command can stay default, but the worker must run `n8n worker`. Set `EXECUTIONS_MODE=queue` on all services so the editor never executes workflows directly. Configure `DB_TYPE=postgresdb` with your Railway Postgres connection string. Redis Bull queue connects to the Railway Redis service. Mount a volume at `/home/node/.n8n` to persist `N8N_ENCRYPTION_KEY` and any installed nodes. Never lose the encryption key—existing credentials become unreadable without it. Set `WEBHOOK_URL` to the public editor URL so webhook-triggered enrichments and inbound Gmail replies resolve correctly. Add `N8N_PROXY_HOPS=1` because Railway places the editor behind a proxy. Enable `EXECUTIONS_DATA_PRUNE=true` to keep Postgres from filling with old run logs during long sequences. Port 5678 is the editor’s HTTP interface; workers do not need public exposure. ## How does n8n Outreach compare against other cold email and outreach platforms Most cold email SaaS tools bundle a sequence builder, inbox rotation, and deliverability monitoring behind a monthly subscription. n8n Outreach separates the workflow engine from the sending infrastructure, so you own the queue, retries, and enrichment logic. That means more setup but far more flexibility, especially when you need custom data pipelines or want to avoid per-contact pricing. ### n8n Outreach vs Instantly (Instantly Alternative) Instantly provides warmup, rotation, and analytics in a polished UI, but you pay per active lead and cannot run custom code between enrichment and send. n8n Outreach replicates core sequences with Gmail nodes and lets you insert any HTTP request, AI step, or data transform. Instantly’s deliverability network is managed for you; n8n Outreach requires you to respect Gmail’s own quotas and warm up domains manually. ### n8n Outreach vs Smartlead (Smartlead Alternative) Smartlead is strong on unlimited inbox rotation and master inbox management. n8n Outreach can rotate senders across multiple Gmail accounts using per-worker credentials, but you must build the rotation logic. Smartlead includes built-in AI reply categorization; n8n Outreach can call OpenAI or other LLMs through n8n nodes. Self-hosting on Railway typically costs less at high volume because Smartlead charges per sender and seat. ### n8n Outreach vs Lemlist (Lemlist Alternative) Lemlist focuses on personalized images and deliverability, but its automation depth is limited. n8n Outreach cannot natively generate dynamic images unless you wire an external API, yet it offers unlimited conditional branching, webhook enrichment, and multi-channel follow-ups. Lemlist is easier for beginners; n8n Outreach is for operators who want complete audit logs and data ownership. ### n8n Outreach vs Apollo (Apollo Alternative) Apollo includes a massive B2B database and engagement suite, but sending limits and seat costs scale quickly. n8n Outreach has no built-in lead database; you bring your own Sheet and enrichment APIs. Apollo’s data quality is hard to match, but n8n Outreach lets you use Apollo’s API as an enrichment source and then send through your own Gmail, avoiding Apollo’s sending fees entirely. ## How to use n8n Outreach (the OSS Outreach Automation)? Queue-mode workers keep executions off the editor so webhooks stay fast under load. Queue-mode workers keep executions off the editor so webhooks stay fast under load. Queue-mode workers keep executions off the editor so webhooks stay fast under load. ## Similar templates - [N8N Main + Worker](https://railway.com/deploy/n8n-main-worker) — Deploy and Host N8N with Inactive worker. - [Evolution API with n8n](https://railway.com/deploy/evolution-api-with-n8n) — Automate WhatsApp workflows with Evolution API, n8n, and Postgres. - [Postgres Backup](https://railway.com/deploy/postgres-s3-backups) — Cron-based PostgreSQL backup to bucket storage Open this page in a browser: https://railway.com/deploy/n8n-outreach