We're currently leveraging the Chili Piper new meetings webhook to automate a critical sales process that previously required significant manual effort (hours daily for data export, filtering, and formatting for Eloqua). This automation has greatly improved efficiency.

However, the current webhook functionality sends all concierge meeting data. This necessitates an additional filtering step within our Power Automate flow to exclude data from concierges we don't need to consume via the webhook. This adds an unnecessary layer of processing on our end and potentially increases data transfer overhead for Chili Piper.

We request a modification to the Chili Piper webhook configuration that allows users to selectively choose which concierges send data via the webhook. This would be similar to the existing functionality for merging specific concierges in the reporting area, where users can explicitly select or deselect concierges.

Ideally, this would involve a configuration option within Chili Piper's webhook settings where users can:

Whitelist specific concierges: Only data from selected concierges would be sent via the webhook.

Blacklist specific concierges: Data from selected concierges would be excluded from the webhook.

Implementing this feature would provide mutual benefits:

Reduced Workload (Customer Side): Eliminates the need for manual filtering in Power Automate or other integration platforms, streamlining our automation workflows and reducing development/maintenance effort.

Reduced Workload (Chili Piper Side): Potentially reduces the volume of data transferred via webhooks, optimizing resource consumption for Chili Piper's infrastructure.

Improved Data Relevance: Ensures that only necessary and relevant data is received, leading to cleaner integrations and more efficient data processing.

We believe this enhancement would significantly improve the utility and efficiency of Chili Piper's webhook functionality for our organization and potentially for other users as well.