Welcome!
What did you do?
I created a WhatsApp instance connected to Evolution API and integrated it with n8n using webhook events.
Incoming messages are received correctly through the messages.upsert webhook event, but the sender information is being returned as @lid instead of a valid WhatsApp JID (@s.whatsapp.net).
Example received:
"remoteJid": "69385314111689@lid"
When trying to reply using:
POST /message/sendText/:instance
the API returns:
{
"exists": false,
"jid": "69385314111689@lid"
}
I already tested multiple Evolution API versions, recreated instances and sessions, and applied the recommended environment variables found in related GitHub issues.
What did you expect?
I expected Evolution API to return a valid WhatsApp JID format like:
"5511999999999@s.whatsapp.net"
or automatically resolve the @lid into a valid sendable WhatsApp number/JID.
I expected the /message/sendText/:instance endpoint to successfully send replies back to users.
What did you observe instead of what you expected?
Instead of receiving a valid WhatsApp JID, the webhook returns @lid identifiers.
Because of this, outgoing messages fail with HTTP 400 errors when using the sendText endpoint.
Example error:
{
"status": 400,
"error": "Bad Request",
"response": {
"message": [
{
"exists": false,
"jid": "69385314111689@lid"
}
]
}
}
Incoming messages work correctly, but replies cannot be delivered.
Screenshots/Videos
No response
Which version of the API are you using?
Currently using:
v2.1.1
Tested versions:
v2.3.7
v2.2.3
v2.1.1
What is your environment?
Windows
Other environment specifications
EasyPanel
Docker image: atendai/evolution-api:v2.1.1
PostgreSQL
n8n Self Hosted (v2.20.9)
Ubuntu VPS
WhatsApp Multi-Device enabled
Webhook integration enabled
Local Cache enabled
Redis disabled
If applicable, paste the log output
No response
Additional Notes
No response
Welcome!
What did you do?
I created a WhatsApp instance connected to Evolution API and integrated it with n8n using webhook events.
Incoming messages are received correctly through the messages.upsert webhook event, but the sender information is being returned as @lid instead of a valid WhatsApp JID (@s.whatsapp.net).
Example received:
"remoteJid": "69385314111689@lid"
When trying to reply using:
POST /message/sendText/:instance
the API returns:
{
"exists": false,
"jid": "69385314111689@lid"
}
I already tested multiple Evolution API versions, recreated instances and sessions, and applied the recommended environment variables found in related GitHub issues.
What did you expect?
I expected Evolution API to return a valid WhatsApp JID format like:
"5511999999999@s.whatsapp.net"
or automatically resolve the @lid into a valid sendable WhatsApp number/JID.
I expected the /message/sendText/:instance endpoint to successfully send replies back to users.
What did you observe instead of what you expected?
Instead of receiving a valid WhatsApp JID, the webhook returns @lid identifiers.
Because of this, outgoing messages fail with HTTP 400 errors when using the sendText endpoint.
Example error:
{
"status": 400,
"error": "Bad Request",
"response": {
"message": [
{
"exists": false,
"jid": "69385314111689@lid"
}
]
}
}
Incoming messages work correctly, but replies cannot be delivered.
Screenshots/Videos
No response
Which version of the API are you using?
Currently using:
v2.1.1
Tested versions:
v2.3.7
v2.2.3
v2.1.1
What is your environment?
Windows
Other environment specifications
EasyPanel
Docker image: atendai/evolution-api:v2.1.1
PostgreSQL
n8n Self Hosted (v2.20.9)
Ubuntu VPS
WhatsApp Multi-Device enabled
Webhook integration enabled
Local Cache enabled
Redis disabled
If applicable, paste the log output
No response
Additional Notes
No response