Platform, Integrations & Extensibility

The customer requests the ability to stream data from Chili Piper to Lightdash, indicating a need for enhanced data integration capabilities for further analysis.

Customers are requesting the ability to verify and use subdomains for custom email domain verification, as the current system only supports root domains. This feature would allow for greater flexibility and alignment with organizational branding.

It seems silly to not be able to delete a field mapping if one was applied in error. Right now you have to delete the entire data field to get rid of the mapping.

There's no way to export the list of assignees in a distribution along with their weighting configurations. Managers who need to share or audit weights, especially distributions with 20+ assignees where the UI becomes difficult to read, have to do it manually. Allow admins to export the active assignee list for any distribution queue as a CSV that includes each rep's name, their assigned weight, and their current active/inactive status. Distribution weighting directly affects lead distribution fairness. Without an exportable view, auditing weights for large queues is slow and error-prone, and sharing queue configuration with stakeholders requires screenshots or manual data entry.

Organizations where Salesforce usernames use one email domain while calendar accounts use a different domain cannot be automatically mapped in Chili Piper. When a user's Salesforce record uses one domain and their calendar login uses another, Chili Piper treats them as separate identities. This breaks automatic user mapping, prevents workspace settings from carrying over, and causes users to create duplicate profiles under their calendar domain that have no connection to their CRM record. Chili Piper should support configuring global domain mapping rules in the integration settings, so that a source domain is always translated to a target domain when matching users across systems. For example, user@domain.com in Salesforce would automatically map to user@email.com in the calendar connection. Organizations that have rebranded, merged, or maintain separate email domains for their CRM and calendar environments have no scalable way to resolve this today. Without global domain mapping, every affected user requires manual workarounds, and any misconfiguration results in broken workspace assignments, lost settings, and duplicate profiles.