You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Chatwoot integration: outgoing messages have trailing newlines on WhatsApp #2415
I was struggling with the 'trailing newlines' (empty spaces at the end of messages) when using Chatwoot with Evolution API v2.3.7. After several attempts with environment variables, I found a simple UX fix that solved the issue:
In Chatwoot Settings, disable the 'Send message with Ctrl + Enter' option and use only 'Enter' to send.
It seems that the TipTap editor in Chatwoot adds invisible paragraph tags or extra \n characters when the 'Ctrl + Enter' shortcut is active. By switching to 'Enter' only, the payload sent to the API is much cleaner, and the 'vacuum' in WhatsApp messages disappears completely.
Tested and working 100% on v2.3.7. Hope this saves someone some time!
I am still experiencing this issue on the latest Chatwoot v4.11.1 (Build 939471c).
I’ve conducted cross-platform testing to isolate the behavior, and it’s clearly a Chatwoot-side issue with how the editor handles the Ctrl + Enter shortcut compared to the standard Enter key.
Test Environment:
Chatwoot: v4.11.1 (Build 939471c)
API Gateways Tested: Evolution API (v2.3.7) AND WAHA GOWS (2026.3.2 CORE)
Channel: WhatsApp (API Channel)
The Findings:
With 'Send message with Ctrl + Enter' ENABLED: Every message sent results in a 'vacuum' (2-3 trailing newlines) on the recipient's WhatsApp. This happens regardless of whether I use Evolution API or WAHA, confirming the extra whitespace is being injected by Chatwoot into the outgoing payload.
With 'Send message with Ctrl + Enter' DISABLED: Messages sent using the standard Enter key are perfectly trimmed and arrive without any extra whitespace.
Conclusion:
The TipTap editor's Ctrl + Enter listener is likely failing to trim() the content or is adding an extra <p></p> block before dispatching the message. Many of us prefer to keep Ctrl + Enter enabled to prevent accidental sends, so a UX workaround isn't a permanent solution.
I was struggling with the 'trailing newlines' (empty spaces at the end of messages) when using Chatwoot with Evolution API v2.3.7. After several attempts with environment variables, I found a simple UX fix that solved the issue:
In Chatwoot Settings, disable the 'Send message with Ctrl + Enter' option and use only 'Enter' to send.
It seems that the TipTap editor in Chatwoot adds invisible paragraph tags or extra \n characters when the 'Ctrl + Enter' shortcut is active. By switching to 'Enter' only, the payload sent to the API is much cleaner, and the 'vacuum' in WhatsApp messages disappears completely.
Tested and working 100% on v2.3.7. Hope this saves someone some time!
Activity
thiagommkt commentedon Mar 3, 2026
Hi everyone,
I was struggling with the 'trailing newlines' (empty spaces at the end of messages) when using Chatwoot with Evolution API v2.3.7. After several attempts with environment variables, I found a simple UX fix that solved the issue:
In Chatwoot Settings, disable the 'Send message with Ctrl + Enter' option and use only 'Enter' to send.
It seems that the TipTap editor in Chatwoot adds invisible paragraph tags or extra \n characters when the 'Ctrl + Enter' shortcut is active. By switching to 'Enter' only, the payload sent to the API is much cleaner, and the 'vacuum' in WhatsApp messages disappears completely.
Tested and working 100% on v2.3.7. Hope this saves someone some time!
fredlisboa commentedon Mar 8, 2026
I am still experiencing this issue on the latest Chatwoot v4.11.1 (Build 939471c).
I’ve conducted cross-platform testing to isolate the behavior, and it’s clearly a Chatwoot-side issue with how the editor handles the
Ctrl + Entershortcut compared to the standardEnterkey.Test Environment:
The Findings:
Enterkey are perfectly trimmed and arrive without any extra whitespace.Conclusion:
The TipTap editor's
Ctrl + Enterlistener is likely failing totrim()the content or is adding an extra<p></p>block before dispatching the message. Many of us prefer to keepCtrl + Enterenabled to prevent accidental sends, so a UX workaround isn't a permanent solution.fix(chatwoot): force state sync, fix newlines, detect phone-sent mess…
dijamarketing commentedon May 15, 2026
This worked perfectly for me. Thank you!