Enhancement: Add environment variable toggle to suppress connection drop spam in Chatwoot

[wahyuwidgetworks]

Problem / Context

Currently, Evolution API sends a 'Connection successfully established!' message to Chatwoot not only on a fresh QR code scan, but on every background websocket reconnection. While there is a 30-second throttle intended to stop infinite loops, it doesn't prevent legitimately spaced background disconnects (e.g. dropped connections from Meta) from polluting the customer's CRM inbox with spammy system messages.

Solution / Plan

Wrap the generic reconnection notification logic in src/api/integrations/chatbot/chatwoot/services/chatwoot.service.ts behind a new environment variable toggle CHATWOOT_MESSAGE_ON_RECONNECT.

• The default will remain true to maintain upstream compatibility.
• When set to false, the system will only send the connection success message to Chatwoot during an initial QR code pairing. All other silent websocket reconnects will be ignored to prevent inbox pollution.

See Prospek documentation docs/evolution/troubleshoot_connection_spam.md for the implementation plan details.

[blocksorg]

Mention Blocks like a regular teammate with your question or request:

@blocks can you add technical details to this issue?
@blocks make the following changes ...
@blocks create an issue from what was mentioned in the following comment ...
@blocks explain the following code ...
@blocks are there any security or performance concerns?

Run @blocks /help for more information.

Workspace settings | Disable this message