Currently, a single Intercom app can only be configured with one webhook endpoint. This becomes a significant limitation for organizations that operate across multiple environments and regions.
In our case, we run live instances in both the US and EU regions, plus separate Staging and UAT environments — four environments in total, each needing its own webhook endpoint to receive and process Intercom conversation events (we feed conversation attributes back into our systems via webhook data).
Since only one webhook can be plugged into an app, the current workaround is to create four separate Intercom apps, one per environment/region. This is difficult to maintain: any configuration change has to be manually repeated across all four apps, which is time-consuming and error-prone, and increases the risk of inconsistent setups between environments.
This is a common pattern for SaaS products that maintain multiple environments (e.g., UAT, Production) across multiple regions (e.g., US, EU). Requiring a separate app per environment/region just to support multiple webhooks adds unnecessary operational overhead.
Requested functionality:
Support for multiple webhook endpoints within a single Intercom app, so that one app can route events to different endpoints (e.g., one per environment or region) without needing to duplicate the entire app setup.
We are currently blocked by this limitation and would appreciate knowing if this capability is already planned, or if not, that it be considered given how common this multi-region/multi-environment setup is for enterprise customers