Deploy n8n Intercom

Deploy and Host self hosted n8n Intercom (Open-Source Intercom Automation) on Railway

The moment an Intercom conversation opens at 2 a.m. and nobody pings Slack, you learn what inbox automation actually means. This Railway template runs queue-mode n8n with Postgres and Redis Bull, so conversation webhooks survive spikes and still reach the CRM—no polling, no dropped closures.

Self-host n8n Intercom 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 Intercom open-source software on Railway (self hosted n8n template)

Queue mode splits the editor from a worker process. On Railway, that means two n8n containers sharing Postgres and Redis Bull. The editor stays responsive while workers chew through payloads. The big gotcha: SQLite cannot run queue mode. That’s why this template pins DB_TYPE=postgresdb. The volume at /home/node/.n8n keeps workflows and credentials persistent across deploys, and EXECUTIONS_DATA_PRUNE=true stops Postgres from ballooning with old execution logs.

Why Deploy n8n Intercom, the Intercom Workflows alternative on Railway (Railway Free Trial)

Intercom Workflows handles a few inbox events, then charges per seat and outbound action. The minute you need a conversation.closed summary in Slack, a HubSpot deal update, and a DM to the assigned rep, native Workflows gets brittle. n8n does all three in one visual workflow without per-event fees. If you only need a light Intercom-to-Slack bridge, the cheapest n8n without queue mode is the right call. For webhook reliability under load, deploy this.

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 Intercom 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 Intercom self hosting

Railway sits in the middle: managed Postgres and Redis without IAM policies, first deploy in minutes.

Common Use Cases for hosted n8n Intercom

A support lead opens a chat about enterprise pricing. The webhook fires, n8n looks up the company in HubSpot, sees $80k ARR, and posts a “Hot lead” message to #sales-triaging Slack with a link to the Intercom inbox. Other common flows: conversation.closed events triggering a CSAT survey after a 10-minute delay; contact attribute syncs into a CRM custom object on lead.updated; assignment alerts pinging the right regional Slack channel; weekly digests of conversations tagged “bug”; and escalation checks for conversations untouched for 4 hours.

Dependencies for n8n Intercom Docker hosted on Railway

You need an Intercom workspace with webhook access, a Slack bot token, and a CRM with API key or OAuth. Railway supplies Postgres for workflow and execution storage, Redis Bull for the queue, and two n8n containers pulling from n8nio/n8n:2.36.8.

Deployment Dependencies for Managed n8n Intercom Service (Customer Messaging Automation)

Three Railway services: Postgres, Redis, and n8n. The editor runs the main n8n process on port 5678; the worker runs n8n worker. Both connect to the same Postgres and Redis because Redis is the job broker and Postgres is the source of truth. Set EXECUTIONS_MODE=queue and DB_TYPE=postgresdb on both containers. Mount a persistent volume at /home/node/.n8n or every deploy resets your Intercom webhook URLs.

Implementation Details for n8n Intercom (Using n8n official docker image)

Both containers use n8nio/n8n:2.36.8. The editor listens on port 5678 and writes jobs to Redis Bull. The worker runs n8n worker with no port exposed. Set WEBHOOK_URL to your Railway public URL so webhook paths build correctly, and N8N_PROXY_HOPS=1 because Railway’s proxy sits in front. Generate N8N_ENCRYPTION_KEY once and never lose it—losing it orphans every saved credential. EXECUTIONS_DATA_PRUNE=true keeps Postgres lean after thousands of Intercom events.

How does n8n Intercom compare against other customer messaging automation platforms

n8n Intercom is a self-hosted automation layer built on n8n queue mode. It ingests Intercom conversation webhooks and routes them to Slack or CRM. Compared to native Intercom Workflows or helpdesk tools, n8n Intercom gives full control over payloads, retries, and custom branching without per-execution pricing.

n8n Intercom vs Intercom Workflows (Intercom Workflows Alternative)

Intercom Workflows handles simple triggers inside Intercom but limited external webhook branching and retries. n8n Intercom lets you transform conversation payloads, fan out to Slack channels, upsert CRM records, and add Redis-backed queues for spikes.

n8n Intercom vs Zendesk (Zendesk Alternative)

Zendesk is a full support suite with ticketing and SLA. n8n Intercom is not a ticketing system; it’s a lightweight event router for Intercom conversation events. Use n8n Intercom when you already have Slack/CRM and need cheap, reliable webhook processing.

n8n Intercom vs Freshdesk (Freshdesk Alternative)

Freshdesk includes omnichannel inbox and automation. n8n Intercom focuses only on Intercom conversation webhooks and downstream sync. It avoids per-agent pricing and keeps data in your VPS.

n8n Intercom vs ManyChat (ManyChat Alternative)

ManyChat targets marketing chat flows on Messenger/Instagram. n8n Intercom targets Intercom support conversations and internal ops (Slack/CRM). ManyChat is SaaS; n8n Intercom is self-hosted OSS.

How to use n8n Intercom (the OSS Customer Messaging Automation)?

Deploy the template on Railway. Intercom sends conversation.created, conversation.updated, conversation.rated webhooks to your n8n webhook URL. n8n workflows parse the JSON, filter by conversation state or tags, then send Slack messages or create/update CRM contacts. Queue mode (Redis + Postgres) ensures webhooks are acknowledged immediately even under burst load. Test with a sample Intercom payload before pointing production webhooks.

How to self host n8n Intercom on other VPS Services (n8n Intercom self hosting guide)

You can run the same stack on any VPS with Docker. Use n8nio/n8n:2.36.8, Postgres, and Redis Bull. Queue mode requires Redis and Postgres; SQLite will not work.

Clone the Repository

Run git clone and cd n8n-intercom.

Install Dependencies

Use the provided docker-compose.yml. No native dependencies beyond Docker and Docker Compose.

Configure Environment Variables

Set N8N_ENCRYPTION_KEY, DB_TYPE=postgresdb, DB_POSTGRESDB_*, EXECUTIONS_MODE=queue, QUEUE_BULL_REDIS_*, and N8N_HOST=0.0.0.0, N8N_PORT=5678.

Start the n8n Intercom Application

Run docker compose up -d. Access n8n at http://your-vps:5678. Create an Intercom webhook pointing to your n8n webhook path.

Official Pricing of n8n Intercom (n8n Intercom pricing)

The OSS n8n Intercom template has no license fee. You pay only your Railway or VPS infrastructure. n8n Cloud starts around $24/month for 2.5k executions; self-hosting on Railway typically costs $10–$25/month with Postgres + Redis.

n8n Intercom cloud vs self hosted comparison (Pricing, features, costs, and more)

n8n Cloud is managed and includes SSO, but the Community Edition self-hosted does not include SSO. For Intercom webhook routing, self-hosted queue mode is usually cheaper and gives data control.

Monthly cost of self hosting n8n Intercom on Railway

Railway stack with n8n, Postgres, and Redis Bull typically $10–$25/month depending on usage. Use the $5 GitHub trial credit to start.

System Requirements for Hosting n8n Intercom on a VPS

Minimum 1 vCPU, 1 GB RAM for low volume. For bursty Intercom conversation webhooks into Slack/CRM, use 2 vCPU, 2 GB RAM and Redis with persistence.

Frequently Asked Questions (FAQs)

Common questions about queue mode, Redis, encryption, workers, and SSO for n8n Intercom.

What is queue mode and why does n8n Intercom need Redis?

Queue mode uses Redis Bull to enqueue workflow executions. Intercom webhooks return 200 immediately, then workers process Slack/CRM actions asynchronously. Redis prevents lost jobs during traffic spikes.

Can I use the cheapest n8n without queue mode for this?

No, the cheapest n8n without queue mode uses SQLite and cannot queue. Intercom conversation webhooks can arrive in bursts; SQLite locks and drops executions. Use Redis + Postgres for reliability.

What happens if I lose N8N_ENCRYPTION_KEY?

You cannot decrypt saved credentials. Existing Intercom/Slack/CRM credentials become unusable. Store the key in Railway variables and back it up.

How do workers help under Intercom conversation webhooks into Slack/CRM load?

Workers pull queued jobs from Redis and run workflows in parallel. A burst of Intercom conversation.updated events won’t block webhook responses, and Slack/CRM rate limits are retried with backoff.

Does Community Edition include SSO?

No. Community Edition self-hosted n8n does not include SSO. n8n Cloud includes SSO; for self-hosted SSO you need an Enterprise license.

What Railway trial credit do I get?

New Railway accounts receive a $5 GitHub trial credit. This covers roughly the first month of a minimal n8n Intercom stack.