Webhook messages started arriving today with @lid only (no phone number), breaking replies in Evolution API + n8n #2326
Description
Welcome!
- Yes, I have searched for similar issues on GitHub and found none.
What did you do?
We configured Evolution API webhooks to forward incoming WhatsApp messages to n8n, where an automated agent processes the message and sends a reply back using the same identifier (remoteJid) received in the webhook payload.
What did you expect?
We expected all incoming webhook payloads to include a resolvable WhatsApp JID containing the phone number (e.g. @s.whatsapp.net) or, when using LID (@lid), to always receive an alternative phone-based identifier (such as remoteJidAlt) so replies could be sent reliably.
What did you observe instead of what you expected?
Starting today, some webhook events arrive with only a @lid identifier, without any phone-based JID or alternative field. Because the phone number is not present, it becomes impossible to determine the correct destination to send a reply, causing automated responses to fail.
Screenshots/Videos
No response
Which version of the API are you using?
Evolution API: (please confirm exact version — issue started today)
n8n: Self-hosted
What is your environment?
Windows
Other environment specifications
No response
If applicable, paste the log output
No response
Additional Notes
No response