Hello everyone! I have set up an integration between WhatsApp and Evolution CRM with webhooks connected to automation tools. The system works perfectly when I send outgoing messages through Evolution CRM. However, I’m facing an issue where incoming replies from WhatsApp users are not being captured by the webhook endpoint.
The webhook only receives data when messages are triggered manually from the server side. Incoming user responses seem to get lost somewhere in the process and don’t appear in my CRM system at all.
I’m wondering if this could be related to webhook configuration issues, cross-origin problems, or maybe the API endpoint setup is incorrect. Has anyone experienced similar problems with Evolution CRM webhook integrations?
Had the same problem with Evolution CRM integration. It’s usually the webhook URL settings in your WhatsApp Business API config. Messages going out use one channel, but replies come back through a different path that needs separate setup. Check that your callback URL in WhatsApp points to the right endpoint that Evolution CRM expects. I had to make sure the incoming message URL was different from the outgoing one. Also verify your endpoint accepts POST requests and isn’t blocked by firewalls. Since manual triggers work fine, it’s definitely a config issue, not the webhook itself.
Sounds like a webhook auth or message filtering problem. Evolution CRM needs different headers for incoming WhatsApp messages vs outgoing ones. Check if your webhook endpoint is validating the signature hash WhatsApp sends with each message. I had this exact issue - outbound worked perfectly but inbound messages got silently dropped because the webhook rejected them due to auth failures. Also make sure your Evolution CRM has the right permissions for receiving WhatsApp webhook events, not just sending. Incoming and outgoing message formats can be different too, so your endpoint needs to parse both types correctly.
your webhook isn’t handling bidirectional communication right. evolution CRM makes you enable ‘incoming message events’ separately from outgoing ones in the API settings. also check that your webhook secret/token matches on both ends - that’s what got me last time.