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

A customer submits the signup form in your Flutter app, Firestore gets a new leads document, and sales hears about it three days later. This template runs n8n in queue mode on Railway so Firestore writes land in Slack, your CRM, and a Google Sheet within seconds, and a slow enrichment API never stalls the next event.

About Hosting n8n Firebase open-source software on Railway (self hosted n8n template)

n8n is fair-code workflow automation. Its Google Cloud Firestore node can create, get, query, upsert, and delete documents, and a separate node covers the Realtime Database. There is no Firestore trigger node, and that's the first thing to plan around. Events arrive one of two ways: a Firebase Cloud Function on onDocumentWritten POSTs the change to an n8n Webhook, or a Schedule Trigger polls with a Firestore query.

Queue mode keeps the push path fast. The editor accepts the webhook and hands the execution to Redis; a worker does the Slack call, the CRM upsert, and the sheet append. Postgres stores workflows, credentials, and execution history.

Why Deploy n8n Firebase, the Zapier alternative on Railway (Railway Free Trial)

Zapier's Firebase / Firestore app watches collections by polling and bills each step as a task. One lead fanning out to Slack, HubSpot, and a sheet is several tasks, every time. n8n Community Edition has no per-execution fee; you pay for the containers. And when a document has nested maps and arrays, a Code node flattens them in five lines instead of a chain of formatter steps.

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

Your Cloud Function needs an HTTPS URL that stays up. Here's who keeps it up.

Provider	Setup time	Webhook endpoint	Typical cost	Tradeoff
DigitalOcean	1-2 hours	Your proxy and certs	$12-24/month	Full control, more failure modes
AWS	3-6 hours	ALB, ECS, RDS	$25-60/month	Overkill for a Firestore relay
Hetzner	1-2 hours	Manual Caddy or Nginx	$5-15/month	Cheapest, most ops work
Railway	Minutes	Public domain with TLS	$10-25/month	A bit more than a VPS, far less work

Railway's free trial covers a test write all the way to Slack.

Common Use Cases for hosted n8n Firebase

Lead capture: a new leads document is enriched, posted as a Slack card, and upserted into the CRM.
Order status fanout: shipped sends an email and a Slack note, failed opens a Zendesk ticket, and every change gets a sheet row.
Moderation queue: new posts documents go to a moderation API; flagged ones land in a Slack channel with an approve link.
Multi-tenant alerts: read tenantId from the document, look up that tenant's Slack channel, and post there.
Nightly exports: a scheduled query pulls yesterday's documents into Postgres or Google Sheets for reporting.
Support handoff: when a tickets document's priority changes to urgent, the on-call Slack channel gets the customer name, plan, and a console link.

Dependencies for n8n Firebase Docker hosted on Railway

This template ships n8n, an n8n worker, Postgres, and Redis already wired together on Railway's private network. You bring a Google service account for Firestore, a Slack credential, and a Firebase project on the Blaze plan if you want Cloud Functions to push events.

Deployment Dependencies for Managed n8n Firebase Service (Workflow Automation)

n8n editor (n8nio/n8n:2.36.8, port 5678): UI, API, and webhook receiver, with a volume at /home/node/.n8n.
n8n worker: same image, started with n8n worker.
Postgres with DB_TYPE=postgresdb. Queue mode does not support SQLite.
Redis for the Bull queue.
Key variables: EXECUTIONS_MODE=queue, WEBHOOK_URL, N8N_PROXY_HOPS=1, N8N_ENCRYPTION_KEY (shared by editor and worker), EXECUTIONS_DATA_PRUNE=true.

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

Create a Google service account with Firestore access and add it as an n8n credential. Add a Webhook node with header auth and copy its production URL. In your Cloud Function, send event.data.after.data() plus the document path to that URL with the shared header. In n8n, {{ $json.path }} and {{ $json.data.email }} are then available to every node.

The gotcha: Cloud Functions retry only if you enable retries, and a webhook that's down drops the event. Return quickly, let n8n queue the work, and run a nightly query that catches anything missed. Keep the service account scoped to Firestore, not project owner.

How does n8n Firebase compare against other Workflow Automation platforms

The difference is cost shape and where your data travels.

n8n Firebase vs Zapier (Zapier Alternative)

Zapier wins on time to first Zap and zero maintenance. But it polls for Firestore changes, every step bills as a task, and branching gets awkward. With branchy flows at volume, n8n's flat cost and Code node win.

n8n Firebase vs Make (Make Alternative)

Make's canvas is nice and operations are cheaper than Zapier tasks. It's also cloud-only, so Firestore data flows through their servers. n8n keeps the path inside your own Railway project.

n8n Firebase vs Power Automate (Power Automate Alternative)

Power Automate has no first-party Firestore connector, so you'd build a custom connector against the REST API. That's reasonable only if your company already lives in Microsoft 365. n8n has a native node.

n8n Firebase vs Activepieces (Activepieces Alternative)

Activepieces has an MIT-licensed core and a tidy builder. n8n has the larger node library, a longer queue-mode track record, and a Firestore node you don't have to write yourself.

How to use n8n Firebase (the OSS Workflow Automation)?

Deploy the template, open the n8n service's public URL, and create the owner account.
Add your Google service account credential and a Slack credential.
Build the starter: Webhook (header auth), Switch on the document's status, Slack message, Google Sheets append.
Deploy a Cloud Function on onDocumentWritten that POSTs to the production webhook URL.
Activate the workflow, write a test document, and watch the execution land.

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

Doable in an afternoon if you're comfortable with Compose and TLS.

Clone the Repository

Nothing to clone: write a docker-compose.yml with editor, worker, Postgres, and Redis, or start from n8n's queue-mode docs.

Install Dependencies

Install Docker Engine and the Compose plugin and pull n8nio/n8n:2.36.8. Point a domain at the VPS and put Caddy or Nginx in front, since Cloud Functions should call HTTPS.

Configure Environment Variables

In .env, set EXECUTIONS_MODE=queue, DB_TYPE=postgresdb, the DB_POSTGRESDB_* host, user, and password, QUEUE_BULL_REDIS_HOST=redis, WEBHOOK_URL=https://your-domain/, N8N_PROXY_HOPS=1, and N8N_ENCRYPTION_KEY from openssl rand -hex 32.

Start the n8n Firebase Application

Run docker compose up -d, check docker compose logs -f worker, then open the editor and import your workflow.

Official Pricing of n8n Firebase (n8n Firebase pricing)

n8n Community Edition is free to self-host under the Sustainable Use License, with no execution limits. n8n Cloud Starter is about $24/month for 2,500 executions. Firebase bills separately: Firestore reads and writes, plus Cloud Functions on Blaze.

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

n8n Cloud means no servers to patch, but executions are metered, and a busy collection eats a Starter plan fast. Self-hosting on Railway is a flat infrastructure bill, and you own upgrades and the encryption key.

Monthly cost of self hosting n8n Firebase on Railway

Railway bills by usage. Editor, one worker, Postgres, and Redis usually land around $10-25/month. More workers raise it; pruning executions keeps Postgres lean.

System Requirements for Hosting n8n Firebase on a VPS

Plan on 2 vCPU and 4 GB RAM for all four services, plus 20 GB disk with pruning on. Add about 512 MB per extra worker.

Frequently Asked Questions (FAQs)

Does n8n have a Firestore trigger?

No. The Google Cloud Firestore node runs operations like get, query, and upsert. For events, have a Cloud Function POST to a Webhook node, or poll on a schedule.

Do I need the Blaze plan?

Only for the Cloud Function push path, since Cloud Functions require Blaze. Polling with a scheduled query works on Spark, at the cost of latency.

How do I stop duplicate alerts?

Cloud Function retries can deliver the same event twice. Pass the function's event ID and check it against a small Postgres table before posting to Slack.

What happens if I lose N8N_ENCRYPTION_KEY?

Every stored credential, including the service account key, becomes unreadable with no recovery. Keep it in a password manager.

Can I add more workers?

Yes. Each worker runs the same image with n8n worker and shares Postgres and Redis. Add replicas on Railway when the queue backs up.

Do I need queue mode for a few Firestore events a day?

No. The cheapest n8n without queue mode is a single container and cheaper. Queue mode earns its keep when bursts or slow APIs would otherwise block webhooks.