fix(chatwoot): prevent duplicate messages from template automation echoes #9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Automated greeting messages sent by Chatwoot (via "template" message type) were not being linked to their Chatwoot Message ID in the Evolution API database. When WhatsApp echoed the sent message back via webhook, Evolution API treated it as a new incoming message because it couldn't find the original ID, resulting in duplicate messages in the Chatwoot conversation.
Solution
Updated the
receiveWebhookhandler fortemplatemessages to callupdateChatwootMessageIdafter sending the message. This ensures the message is stored in the database, allowing the deduplication logic to correctly identify the echo.Type of Change