[Bug]: Chatwoot integration fails to parse templateMessage - "no body message found"

[FelipoArts]

Welcome!

• Yes, I have searched for similar issues on GitHub and found none.

What did you do?

I am using a Baileys instance integrated with Chatwoot on Evolution API v2.3.7. The issue occurs when the instance receives a message sent via the Official WhatsApp Business API (specifically through platforms like Odin Chat) that uses Hydrated Templates for transfers or bot interactions.

I monitored the Docker logs while reproducing the issue to capture how the ChatwootService handles these specific incoming payloads.

What did you expect?

I expected the Evolution API to recognize the templateMessage type, extract the text content from hydratedContentText, and forward it to Chatwoot as a standard message so the agent can see the customer's query.

What did you observe instead of what you expected?

The Evolution API receives the message from WhatsApp, but the ChatwootService fails to find the message body. It logs a warning [ChatwootService] [string] no body message found and drops the message. As a result, the message appears on the WhatsApp mobile app but never reaches the Chatwoot dashboard.

Screenshots/Videos

No response

Which version of the API are you using?

2.3.7

What is your environment?

Docker

Other environment specifications

No response

If applicable, paste the log output

// Incoming message structure captured in logs:
{
"message": {
"templateMessage": {
"hydratedTemplate": {
"hydratedContentText": "Olá [User], tudo bem?\nDarei continuidade ao seu atendimento.\n[Customer Message Content]...",
"templateId": "1621525192363457"
}
}
},
"messageType": "templateMessage",
"instanceId": "747bbf59-a0a0-4486-b368-135b2a0ff77b",
"source": "desktop"
}

// The specific error from Evolution API:
[Evolution API] v2.3.7 - WARN [ChatwootService] [string] no body message found

Additional Notes

No response