Feature Requests

The Chili Piper MCP server currently works with Claude but is not compatible with Gemini. For companies that have Gemini licensed org-wide but not Claude, the MCP scheduling integration is effectively unavailable. Extend MCP compatibility to Gemini so that reps using Gemini as their primary AI assistant can access Chili Piper scheduling tools the same way Claude users can today.

Webhooks today only fire when a meeting is scheduled. When a lead fills out a form, is shown a scheduler, but doesn't complete a booking, no webhook fires. External workflows that depend on knowing about non-booking events, such as triggering a follow-up sequence, have no signal to act on. Requested behavior: Add a webhook event that fires when a qualified lead is presented with a scheduler but does not complete a booking, including the lead's details and the router they were shown. Why it matters: Non-booking events are high-value signals for downstream automation. Without a webhook for this case, teams can't trigger follow-up flows automatically and have to rely on polling or manual intervention.

We use the edge API to see available sessions - after which we grab the meeting link. We would like the option to grab the single-use meeting link instead of the persisted one. Thank you!

When meetings are created programmatically or tracked externally, there's no API method to associate a booking link with the resulting meeting. Teams that need to attribute meetings to specific campaigns or sources based on which link was used can't get that data reliably. Requested behavior: Expose an API endpoint that allows a booking link to be associated with a specific meeting record, so the link source is captured and available for attribution reporting. Why it matters: Campaign attribution depends on knowing which link drove each meeting. Without API support for this association, teams running multi-channel campaigns can't close the loop between link and meeting outcome.

There is no API endpoint to retrieve full chat conversation history. Teams that want to analyze conversation data, feed it into an LLM, or integrate it with other tools have no programmatic way to access it. Chili Piper should expose an API endpoint that allows customers to pull complete chat conversation history, including message content, timestamps, and participant details. Conversation history is a valuable data asset. Without API access, teams can't run custom analysis, build integrations, or extract insights at scale.

When a meeting event can't be synced to Salesforce because the associated contact doesn't exist in the CRM yet, there's no log of that failure and no way to retry the sync after the contact is created. The event is simply lost. Provide an admin-accessible error log that shows events that failed to sync to Salesforce, including the reason for failure, and allow admins to manually trigger a sync for individual records after the underlying issue, such as a missing contact, has been resolved. Sync failures that leave no trace are invisible data gaps. Ops teams managing high-volume bookings need a way to catch and recover these events without relying on downstream CRM audits to discover what's missing.

The workspace name is included in the Zapier new meeting payload when a meeting is booked via a router, but is absent when a meeting is booked directly via a Meeting Type link. This inconsistency means teams building automations on top of Zapier or webhooks cannot reliably use workspace as a grouping or routing condition in their flows, since the field only exists for a subset of bookings. Chili Piper should include the workspace name in the meeting payload for all booking methods, including Meeting Type links, personal scheduling links, and any other entry point, not only router-booked meetings. Workspace is a fundamental organizational attribute of every meeting in Chili Piper. Omitting it from non-router payloads forces automation builders to handle inconsistent data structures and prevents workspace-based logic from working reliably across all booking flows.

Static scheduling links can't be scoped to a specific campaign or capped by use count. Teams sharing links in outbound sequences have no way to track which campaign drove a booking, and nothing prevents a prospect from reusing a link outside the intended window. A POST endpoint should allow developers to programmatically generate unique booking URLs with a configurable max_event_count and a specified owner or Meeting Type. Once the limit is reached, the link expires. This is a direct Calendly parity gap. Teams currently work around it with UTM parameters, which are unreliable, or avoid dynamic link generation entirely.

When a custom webhook fails due to an issue on the receiving end, such as an endpoint timeout or HTTP 500, Chili Piper provides no log of the failure and no way to resend the event. Admins discover failures only through downstream gaps, such as missing records or broken automation flows, and have no recovery path except manual workarounds or API intervention. For high-volume users, this means missed bookings and lost data with no built-in remedy. Chili Piper should provide a webhook delivery log that surfaces failed events with timestamps, payload details, and error codes, and allow admins to manually resend individual or bulk failed events directly from the admin dashboard. Resent events should include unique event IDs to support idempotency and prevent duplicate processing. Webhook delivery failures are a standard operational risk for any integration-heavy platform. Without visibility into failures and a way to recover from them, admins have no reliable way to ensure data integrity between Chili Piper and external systems. A delivery log with resend capability is a baseline reliability feature expected by enterprise teams running critical automations on top of webhook data.

Chili Piper's webhook for new meetings fires for all Concierge meeting data with no way to scope it to specific routers. Teams that only need data from certain Concierges are forced to add a filtering layer in their own automation platform, such as Power Automate or Zapier, to exclude irrelevant events before they can act on them. This adds unnecessary processing overhead on the customer side and increases data transfer volume on both ends. Chili Piper should allow admins to configure webhook subscriptions to include or exclude specific Concierges or routers, so only the relevant meeting events are sent to the endpoint. Webhook consumers shouldn't need to build their own filtering logic to compensate for missing configuration options in the source system. Scoped webhooks reduce noise, lower processing overhead for both parties, and make integrations simpler to build and maintain, particularly for teams running complex automation workflows against high-volume meeting data.