Deploy and Host self hosted Evolution API Flowise (WhatsApp API with Flowise Chatbots) on Railway

This template runs Evolution API with Postgres and Redis so a WhatsApp number can hand messages to a Flowise chatflow.

About Hosting Evolution API Flowise open-source software on Railway (self hosted Evolution API with Flowise template)

This template runs the Evolution API gateway (evoapicloud/evolution-api:v2.3.7) on port 8080, backed by Postgres for instances, messages, and contacts, and Redis as the cache.

Railway handles TLS, the database connection strings, the volume, and restarts.

Why Deploy Evolution API Flowise, the Twilio alternative on Railway (Railway Free Trial)

Twilio is the managed route, with per-message fees on top of Meta's charges and custom webhook code to wire in Flowise.

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 Evolution API Flowise 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 Evolution API Flowise self hosting

Railway runs the three services this stack needs in one project, while a VPS leaves the wiring to you. The table compares the two approaches.

Provider	What You Get with Railway	What You Get with the Other Provider
DigitalOcean	Evolution API, Postgres, and Redis from one template, with DATABASE_URL and REDIS_URL wired in.	A droplet where you set up Docker Compose, the .env file, and the database by hand.
AWS	A managed deploy with the volume and public domain ready, and no IAM or VPC design first.	Full networking and scaling control, but you write the IAM and security group rules yourself.
Hetzner	Usage-based pricing on the same services, with a public /manager URL once the deploy finishes.	Low-cost servers, but you install Docker, manage the session volume, and keep it patched.

Choose based on how much infrastructure you want to own.

Common Use Cases for hosted Evolution API Flowise

Flowise RAG bot for WhatsApp FAQs: Point a retrieval chatflow at your product docs so the bot answers repetitive questions on the number customers already text. Flowise receives the contact's remoteJid and pushName automatically.
Keyword-triggered bots: Set triggerType to "keyword" with triggerOperator "startsWith" and triggerValue "order" so only matching messages start a session. Everything else stays with your team.
Human takeover by pausing a session: Call POST /flowise/changeStatus with status "paused" for a customer's remoteJid when they need a person. Set it back to "opened" after the handoff.
Multiple bots per instance: Create several Flowise bots on one WhatsApp instance, each with its own trigger, and use flowiseIdFallback for messages no trigger matches.
Delay and debounce for natural replies: Use delayMessage for simulated typing and debounceTime to merge a burst of short messages into one prompt. Replies feel human, and Flowise is not asked to answer half-sentences.

Dependencies for Evolution API Flowise Docker hosted on Railway

This template runs three services: the Evolution API container, Postgres, and Redis.

Deployment Dependencies for Managed Evolution API Flowise Service (WhatsApp API)

evolution-api: the evoapicloud/evolution-api:v2.3.7 image on port 8080, public, with a health check on / and a volume at /evolution/instances.
Postgres: DATABASE_CONNECTION_URI from Railway's DATABASE_URL.
Redis: CACHE_REDIS_URI from Railway's REDIS_URL, used as the cache.
Flowise endpoint: a reachable apiUrl with no trailing slash, such as http://flowise.site.com/v1, plus an apiKey if your chatflow needs one.

Implementation Details for Evolution API Flowise (Using Evolution API official docker image)

The template generates AUTHENTICATION_API_KEY, a 32 character global key sent in the apikey header on every request and used to log into the manager.

How does Evolution API Flowise compare against other ways to put an AI chatflow on WhatsApp

Evolution API Flowise vs Twilio with Flowise (Twilio Alternative)

Connection path: Evolution API links a WhatsApp instance straight to a Flowise chatflow through the /flowise routes, so apiUrl, apiKey, and triggerType go into one create call.
Cost model: Evolution API is free and you pay only for hosting, while Twilio adds a per-message fee on top of Meta's charges. Check both pricing pages for current numbers.
Where Twilio wins: Twilio offers the official WhatsApp Cloud API path with business verification and support, which matters for high-volume sending. Evolution API can run on Baileys, which is unofficial and carries ban risk for bulk messages.

Evolution API Flowise vs Botpress (Botpress Alternative)

Flow ownership: Your logic stays in the Flowise chatflow you already built, so you don't rebuild it in a second visual builder.
Session control: The changeStatus route moves a contact to paused or closed from your backend, which makes human takeover simple.
Where Botpress wins: Botpress ships its own flow builder, NLU tooling, and channel connectors, so it's the better pick if you don't already run Flowise.

Evolution API Flowise vs Typebot (Typebot Alternative)

Scope: Typebot is a visual builder for websites and messaging channels. Evolution API Flowise is a narrower WhatsApp gateway that hands messages to a Flowise chatflow.
Trigger logic: triggerType and triggerOperator decide which bot starts, which is simple but limited to what those operators express.
Where Typebot wins: If you want one editor that also covers websites, Typebot covers more surfaces.

Evolution API Flowise vs Chatwoot bots (Chatwoot Alternative)

Primary job: Chatwoot is a support inbox with bot replies, suited to shared agent queues. Evolution API Flowise focuses on the WhatsApp connection and the bot session.
Session handling: Expire and keepOpen control how long a session lasts per contact, and listeningFromMe decides whether your own outgoing messages affect the bot.
Where Chatwoot wins: Chatwoot already gives you agents, assignment, and history, which you would otherwise build on top of Evolution API.

How to use Evolution API Flowise (the OSS WhatsApp API gateway)?

Open your-domain/manager, log in with the global API key, and create an instance. Scan the QR code under WhatsApp Linked devices and wait for it to show connected.
In Flowise, open your chatflow's API panel and copy the prediction URL (without the trailing slash) and the API key.
POST to your-domain/flowise/create/your-instance with this body:

{
  "enabled": true,
  "apiUrl": "http://flowise.site.com/v1",
  "apiKey": "your-flowise-api-key",
  "triggerType": "keyword",
  "triggerOperator": "equals",
  "triggerValue": "hello"
}

Send a WhatsApp message matching your trigger to the connected number and confirm the chatflow replies.
For human takeover, POST to your-domain/flowise/changeStatus/your-instance with the contact's remoteJid and "status": "paused". The bot stops replying to that contact until you set it back.

How to self host Evolution API Flowise on other VPS Services (Evolution API self hosting guide)

Any VPS with Docker works here. You wire up the same three pieces Railway handles for you: the Evolution API container, Postgres, and Redis.

Clone the Repository

git clone https://github.com/EvolutionAPI/evolution-api.git
cd evolution-api

Install Dependencies

Docker Compose pulls the image and its dependencies, so you only need to confirm both are installed with docker compose version.

Configure Environment Variables

cp .env.example .env

Set AUTHENTICATION_API_KEY to a long random string, since every Flowise route uses it in the apikey header.

Start the Evolution API Flowise Application

docker compose up -d

Open https://your-domain/manager, log in with your global key, create an instance, and scan the QR code under Linked devices.

Official Pricing of Evolution API Flowise (Evolution API pricing)

Evolution API itself is free and open source, so there is no license fee to pay for the Flowise integration.

Evolution API Flowise cloud vs self hosted comparison (Pricing, features, costs, and more)

The fair comparison splits hosting from messaging. Evolution API is free, so your bill is the server plus whichever WhatsApp route you pick.

Monthly cost of self hosting Evolution API Flowise on Railway

Railway runs evolution-api, Postgres, and Redis as three services.

System Requirements for Hosting Evolution API Flowise on a VPS

A small VPS can run all three services, but it needs enough RAM for Node.js plus the database without swapping.

Frequently Asked Questions (FAQs)

Where does Flowise run in this setup?

Flowise runs wherever you already host it, not on the Railway template.

What's the difference between keyword and all triggers?

With triggerType "all", every incoming message starts the bot, which is noisy on a shared number.

How do I pause a bot for human takeover?

Call POST /flowise/changeStatus/your-instance with the contact's remoteJid and status "paused".

How long does a session last?

The expire field sets how many minutes pass before the session expires and restarts on the next message.

Can one instance run more than one Flowise bot?

Yes, each bot has its own apiUrl and trigger. How overlapping triggers are resolved isn't documented, so keep keyword values distinct.

Do media messages reach the chatflow?

Text is what the chatflow reads reliably.