Skip to content

Guide

Evolution API Typebot bot not replying on WhatsApp

Your WhatsApp instance is connected in Evolution API, your Typebot flow is built, you send a test message and nothing comes back. Most of the time the issue is neither WhatsApp nor Docker networking: the message stops at one of five checkpoints inside the integration between Evolution API v2.3.7 and Typebot v3.19.1.

On this page
  1. 1. TYPEBOT_ENABLED is still false
  2. 2. The URL points to the Builder or ends with a slash
  3. 3. TYPEBOT_API_VERSION is set to old on Typebot v3
  4. 4. Unpublished draft or flow title instead of publicId
  5. 5. Paused session, keyword mismatch or testing from your own number
  6. Two-minute checklist

The diagram below traces a message from WhatsApp to Typebot Viewer and shows the five places where replies stop:

Message verification flow between WhatsApp, Evolution API and Typebot Viewer showing the five checkpoints where the bot stops replying

1. TYPEBOT_ENABLED is still false

Evolution API's .env.example ships with TYPEBOT_ENABLED=false. In BaseChatbotController, when that flag is off, every /typebot/* call returns 400 Bad Request (Typebot is disabled), and incoming WhatsApp messages skip Typebot completely.

Check the live container environment:

bash
sudo docker compose exec evolution-api env | grep TYPEBOT

If TYPEBOT_ENABLED is not true, update .env or docker-compose.yml and recreate the container:

yaml
services:
  evolution-api:
    environment:
      TYPEBOT_ENABLED: "true"
      TYPEBOT_API_VERSION: latest
bash
sudo docker compose up -d evolution-api

docker compose restart does not reload changed environment definitions from docker-compose.yml; use up -d so Docker recreates the container.

2. The URL points to the Builder or ends with a slash

Evolution API's TypebotService builds the request URL directly from the url saved on the bot:

text
${url}/api/v1/typebots/${typebot}/startChat

Two mistakes break that call immediately:

  • Using the Builder URL (builder.example.com) instead of the Viewer (bot.example.com). The Builder is only the editor. startChat and continueChat live on typebot-viewer.
  • Leaving a trailing slash (https://bot.example.com/). Concatenation produces https://bot.example.com//api/v1/..., which returns 404.

When Typebot and Evolution API share one Docker Compose stack, set url to http://typebot-viewer:3000 (no trailing slash). Across separate servers, use the Viewer's public URL without a trailing slash (https://bot.example.com).

Test the Viewer directly with curl to rule out proxy or TLS issues:

bash
curl -i -X POST https://bot.example.com/api/v1/typebots/your-public-id/startChat \
  -H "Content-Type: application/json" \
  -d '{}'

HTTP 200 with a sessionId proves the Viewer URL and flow exist. HTTP 404 points to a wrong host, a trailing slash or an unpublished flow.

3. TYPEBOT_API_VERSION is set to old on Typebot v3

In Evolution API v2.3.7 (typebot.service.ts), TYPEBOT_API_VERSION controls which API path gets called:

TYPEBOT_API_VERSION value Endpoint called by Evolution API Compatibility
latest /api/v1/typebots/<id>/startChat and /api/v1/sessions/<id>/continueChat Current Typebot (v2.18+ and v3.x)
old /api/v1/sendMessage Legacy Typebot versions

Running TYPEBOT_API_VERSION=old against Typebot 3.x hits a retired route, and the failure only shows up in sudo docker compose logs evolution-api. Set TYPEBOT_API_VERSION=latest and recreate the container.

4. Unpublished draft or flow title instead of publicId

Evolution API's typebot field does not take the human-readable flow title from the dashboard (such as "Main Support"). It expects the public ID — the slug shown in Typebot's Share tab right after the Viewer domain.

An unpublished draft also returns 404 from startChat. Click Publish in Typebot Builder, then inspect what Evolution API stored:

bash
curl -fsS https://api.example.com/typebot/find/support \
  -H "apikey: $EVOLUTION_API_KEY"

Verify that url, typebot and enabled match the values that worked in your direct curl test from step 2.

5. Paused session, keyword mismatch or testing from your own number

Even when the API wiring is right, four normal rules can keep the bot quiet:

  • Testing from the paired WhatsApp account while listeningFromMe is false: Evolution API ignores messages sent by the account itself. Test from a second phone number.
  • A human replied earlier while stopBotFromMe is true: that contact's session switches to paused, so the bot stops replying until the session expires or is reset.
  • Keyword trigger (triggerType: "keyword"): any message that does not match triggerOperator and triggerValue will not open a session.
  • Testing in a group chat while ignoreJids includes "@g.us": group chats are skipped on purpose.

List active sessions using the bot id returned by /typebot/find/<instance>:

bash
curl -fsS https://api.example.com/typebot/fetchSessions/BOT_ID/support \
  -H "apikey: $EVOLUTION_API_KEY"

If your test number is stuck in paused or closed, clear that contact's session via /typebot/changeStatus/<instance>:

bash
curl -fsS -X POST https://api.example.com/typebot/changeStatus/support \
  -H "apikey: $EVOLUTION_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"remoteJid":"[email protected]","status":"delete"}'

Two-minute checklist

Symptom Where to check Fix
/typebot/* returns Typebot is disabled docker compose exec evolution-api env Set TYPEBOT_ENABLED=true and recreate
404 calling startChat url field in /typebot/find/<instance> Point to the Viewer with no trailing slash
Errors on /api/v1/sendMessage in logs TYPEBOT_API_VERSION Switch to latest and recreate
404 even on the Viewer URL Share tab and Publish button in Typebot Publish the flow and use its publicId
Only one phone number gets no reply /typebot/fetchSessions/<botId>/<instance> Call changeStatus with status: "delete"

The full Docker Compose setup with Typebot 3.19, Evolution API v2.3.7 and Caddy on one server is in Typebot and Evolution API on the same VPS for WhatsApp. If you still need a server for the stack, see VPS for Evolution API.