Is your feature request related to a problem? Please describe.
Currently, Waha API update messages are being displayed to end users (instances) within Chatwoot. This creates confusion, as these notifications are technical in nature and not relevant to end users. As a result, it introduces noise in the communication flow and may lead to misunderstandings or unnecessary concerns from operators using the platform.
Describe the solution you'd like
Waha API update messages should not be visible to end users in Chatwoot. These notifications should be restricted to system administrators only.
As a suggested implementation, an environment variable (ENV) could be introduced to define which instance is considered the admin. Only this designated instance would receive technical messages, while all other instances would continue operating without exposure to such notifications.
Describe alternatives you've considered
One alternative would be to allow global disabling of these messages via configuration. However, this would also remove visibility for administrators who may rely on this information. Another option would be implementing message-type filtering within Chatwoot, though this would add configuration complexity.
Additional context
This change would help clearly separate operational communication from technical notifications, improving the end-user experience and reducing unnecessary noise in the support workflow.
Is your feature request related to a problem? Please describe.
Currently, Waha API update messages are being displayed to end users (instances) within Chatwoot. This creates confusion, as these notifications are technical in nature and not relevant to end users. As a result, it introduces noise in the communication flow and may lead to misunderstandings or unnecessary concerns from operators using the platform.
Describe the solution you'd like
Waha API update messages should not be visible to end users in Chatwoot. These notifications should be restricted to system administrators only.
As a suggested implementation, an environment variable (ENV) could be introduced to define which instance is considered the admin. Only this designated instance would receive technical messages, while all other instances would continue operating without exposure to such notifications.
Describe alternatives you've considered
One alternative would be to allow global disabling of these messages via configuration. However, this would also remove visibility for administrators who may rely on this information. Another option would be implementing message-type filtering within Chatwoot, though this would add configuration complexity.
Additional context
This change would help clearly separate operational communication from technical notifications, improving the end-user experience and reducing unnecessary noise in the support workflow.