[ISSUE-REVERT]: Enhance Webhook Registration Process to Support Event-Based Subscriptions #495
Description
Currently, the webhook functionality in Revert requires specifying a t_id for each webhook registration, which implies that webhooks must be set up individually for each tenant. This approach necessitates a significant amount of development and maintenance effort, especially for applications that utilize Revert as a central hub for connecting with various integrations and require webhook functionality for common events across multiple tenants.
The suggested enhancement is to shift from a tenant-specific webhook registration model to an event-based subscription model. In this model, developers can register a webhook for specific event types (e.g., deal updates in HubSpot) without specifying tenant IDs during the registration process. The webhook system would then notify the registered endpoint for any event of that type, including the tenant ID (t_id) in the webhook payload, thereby allowing the receiving system to differentiate between tenants.
Benefits:
- Reduced Development and Maintenance Effort: Developers would no longer need to register and manage webhooks for each tenant individually, simplifying the integration process.
- Increased Flexibility and Scalability: This approach allows for more flexible and scalable webhook management, accommodating common use cases where the same event type is relevant across multiple tenants.
- Improved User Experience: By lowering the barrier to implementing and managing webhooks, developers can more easily leverage Revert's capabilities, enhancing the overall utility and user-friendliness of the platform.