Scheduling & Booking · Integration
Chili Piper
Add Chili Piper to your product for your customers, and give your AI agents governed access to it.
Embed a Chili Piper integration so your customers can book and route meetings from inside your product, working their own meetings, queues, and routing configuration. Each customer connects their own account, so routing follows their rules and their reps rather than anything hard-coded by you, and queue and field mapping is configuration per tenant. fastn handles per-customer authorisation and API upkeep, so a new booking setup does not need a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers book meetings from inside your product, routed by their own Chili Piper rules.
Read scheduled meetings and their owners so bookings appear against the right record in your app.
Read queues and routing configuration so users can see who a lead will land with.
Trigger your product when a meeting is booked, reassigned, or cancelled.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks which rep a lead would route to before promising a follow-up.
An agent books or reschedules a meeting within governed permissions, with the action audited.
An agent reacts to a new booking and prepares a brief for the meeting owner.
Example prompt
List meetings booked this week that were later reassigned and show the original and current owner.
Set up Chili Piper in 4 steps
- 01Open the Chili Piper connector from your fastn dashboard.
- 02Have each customer authenticate their Chili Piper account with OAuth or an API key.
- 03Map the queues, meeting types, and fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Chili Piper integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Chili Piper integration without building it. Your customers connect their own Chili Piper account inside your product and work their bookings, events and availability there, with no per-customer code on your side.
- Handle the part that actually costs time: availability is only true at the moment you read it, so a stale free/busy picture becomes a double booking somebody has to apologise for. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Chili Piper update is not your on-call problem.
- One integration serves your product and your agents. The same governed Chili Piper connection powers in-product features and gives AI agents scoped, audited access, so you let people book and reschedule without leaving your product without wiring it twice.
Used by these teams
Compare with
CalendlyWorks well with
Salesforce
HubSpotOften used alongside
Tools the same teams tend to run next to Chili Piper, across other categories.
Slack
Microsoft Teams
Twilio
AircallChili Piper integration FAQ
How do I add a Chili Piper integration to my product?
Enable the Chili Piper connector in your fastn dashboard, then let each customer authenticate their own Chili Piper account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Chili Piper client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Chili Piper account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Chili Piper account and only ever sees their own bookings, events and availability. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Chili Piper integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent checks which rep a lead would route to before promising a follow-up.
Who maintains the Chili Piper integration?
fastn does. When Chili Piper changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create, reschedule or cancel bookings in Chili Piper automatically?
Yes, in each customer's own account. Your product reads live availability, places a booking, moves it or cancels it, and reacts when someone books or cancels on the other side.
Does it respect each team's own availability rules in Chili Piper?
Yes. Working hours, buffers, lead times, resource capacity and routing rules are configured per customer and mapped rather than hard-coded, so an unusual setup works without code from you.
What can I build with the Chili Piper integration?
A common starting point: book meetings from inside your product, routed by their own Chili Piper rules. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Chili Piper integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Chili Piper does not change your per-connector cost. You can start free with 3 connected accounts.
Add Chili Piper to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.