devlikeapro
Feature Request: Separate Group ACK Events
Feature Request: Separate Group ACK Events
Overview
We propose implementing separate webhook events for group message acknowledgments (group.ack) to complement the existing message.ack event. This enhancement will provide better organization and filtering capabilities for webhook consumers, especially when dealing with group conversations.
Problem Statement
Currently, WAHA emits all message acknowledgments (both direct messages and group messages) through a single message.ack event. This creates several challenges:
-
Mixed Event Types: Webhook consumers receive both direct message and group message ACKs in the same event stream, making it difficult to filter and process them separately.
-
Complex Filtering: Applications need to implement additional logic to distinguish between direct message ACKs and group message ACKs based on the payload structure.
-
Event Organization: Group-specific logic and direct message logic are mixed together, reducing code clarity and maintainability.
-
Webhook Efficiency: Consumers interested only in group events or only in direct message events must process all ACK events and filter them client-side.
Proposed Solution
New Event: group.ack
Create a dedicated group.ack event that specifically handles acknowledgments for group messages, while keeping the existing message.ack event for direct messages.
Key Benefits
-
Clear Separation: Group ACKs and direct message ACKs are handled by separate events, improving code organization.
-
Better Filtering: Webhook consumers can subscribe to specific event types based on their needs.
-
Improved Performance: Applications can process only the events they need without additional filtering.
-
Enhanced Maintainability: Group-specific logic is isolated, making the codebase easier to maintain and extend.
-
Backward Compatibility: The existing
message.ackevent remains unchanged, ensuring no breaking changes.
We can achieve it easily when we add a new webhook filter basically https://github.com/devlikeapro/waha/issues/830
Refactoring ACK events to improve message segregation and reduce noise under high-load scenarios. Currently, all ACKs — including group-related ones — are emitted through the message.ack event, causing significant overhead when the groups feature is enabled. The proposal is to keep message.ack only for contact (1:1) message acknowledgments and introduce a new group.ack event dedicated solely to ACK notifications from groups. This separation will enable better event filtering, lower processing latency, and improved predictability when handling ACK callbacks.
