Problemas com whatsapp para responder clientes

Built with n8n
1

Fiz um workflow, para atender um escritório de advocacia, porém não estou conseguindo fazer com o que whatsapp responda as mensagens, mesmo que nas execuções esteja dando o

1 Like
2

Hi @Henrique_Pena

Take note this is an English forum, so do use a translator before you post.

I will do it for you this time

Can you share your n8n setup (docker or npn setup, n8n version etc).

What is your workflow?

4

Adding to Benjamin’s checklist — a few more specific things that cause exactly this symptom (execution looks fine, WhatsApp receives nothing):

If you’re using Evolution API:

  • The HTTP Request node needs operation: "send-text" set explicitly in the body or as a path parameter. Without it the node runs and returns 200 but sends nothing. Easy to miss when cloning or setting up for the first time.
  • Check the instance status in your Evolution Manager dashboard. If the QR code expired or the phone disconnected, the API will accept requests without error but silently drop them. Re-scan the QR to reconnect.
  • The remoteJid field must be in the format 5511999999999@s.whatsapp.net (country code + number, no spaces or dashes, with the suffix). Group chats use @g.us instead.

If you’re using WhatsApp Cloud API (Meta):

  • Your n8n workflow must subscribe to the messages webhook field in Meta App Dashboard → WhatsApp → Configuration. Without that subscription, Meta won’t push inbound messages to you.
  • Make sure you’re not filtering out is_echo: true events before your send node runs — but also make sure you ARE filtering them somewhere, otherwise the bot responds to its own messages and loops.

General n8n:

  • If any node before your WhatsApp send has Continue on Fail enabled, an upstream error won’t stop execution — the workflow appears successful but the send node never received valid input. Check the individual node outputs in the execution log to see what actually reached the send step.

What API are you using (Evolution API, Cloud API, or a third-party provider)?