Skip to main content

Book meetings with Chili Piper using Fin for Sales

Let Fin schedule meetings with leads automatically using Chili Piper Concierge routing.

Written by Beth-Ann Sher

Fin for Sales can qualify inbound leads and book meetings on their behalf using Chili Piper Concierge. When Fin identifies a sales-ready lead, it routes them to the right rep and surfaces a scheduling experience directly in the Messenger, or via a link in email and SMS.

Before you begin

Make sure you have:

  • Chili Piper admin role - only a Chili Piper admin can generate the API key required for setup.

  • An active Concierge router - you need at least one Concierge router of type "web form" configured in your Chili Piper workspace.


Step 1: Generate a Chili Piper API key

  1. Log in to the Chili Piper Admin Center.

  2. Navigate to API Access Tokens under Credentials.

  3. Click Generate Token.

  4. Give your token a name (for example, "Fin integration").

  5. Enable the following permissions:

    • API: All permissions

    • Concierge: All permissions

    • Logs: All permissions

    • Tenant: Read

    • Webhook: Create, Read, Remove

  6. Copy the token immediately as it may not be visible again and you’ll need this in the next step.


Step 2: Connect Chili Piper in Intercom

To connect Chili Piper:

  1. Click + Add Calendar and select Chili Piper.

  2. Paste the API key you generated in step 1.

  3. Click Connect.

Your key will be validated to check it has all the required permissions. If any are missing, you'll see a checklist highlighting the gaps. Fix the key in Chili Piper and try again before completing the connection.

Once connected, a green confirmation banner appears and Intercom automatically registers a booking webhook with Chili Piper.

Note:

  • The connected Chili Piper API key must hold all required permissions (routing, logs read, and webhook management). Setup validates this, but if the key is later changed in Chili Piper you'll need to update it in your Intercom workspace too.

  • The logs.read permission is required to record meeting bookings that happen on non-Messenger channels such as email and SMS.


Step 3: Select a router

  1. From the Select a calendar dropdown, choose Chili Piper.

  2. Select a router from the list.

This only shows compatible routers which must be type "web form" with a calendar displayed on at least one route. Routers that don't meet the requirements are greyed out at the bottom of the list. Hover over a greyed-out router to see why it can't be selected.

Note: By default, the router looks for rep availability within a 60-day window.


Step 4: Map your data fields

After selecting a router, map Intercom data to your Chili Piper form fields so leads are routed correctly.

The lead's email address is automatically mapped. You can also map two additional fields:

Intercom field

What it provides

geoip.country_code

2-letter country code (for example, US, GB)

geoip.region

Geographic region (EMEA, NAMER, LATAM, APAC)

Make sure these match the field names defined in your Chili Piper web form trigger.


Manage your Chili Piper integration

Once connected, your integration appears in Fin AI Agent > Sales > Train > Integrations under "Calendars for booking meetings".

Click the ••• menu next to the integration to:

  • Update access token: replace the API key if it expires or is regenerated in Chili Piper.

  • Remove integration: disconnects Chili Piper, deregisters the booking webhook, and removes the stored configuration.


How the booking experience works for leads

Once Fin determines a lead is sales-ready, it routes them through Chili Piper Concierge to the right rep. The experience depends on the channel:

  • Messenger (web): the lead sees an inline calendar widget and picks a time.

  • Email or SMS: Fin generates and shares a Chili Piper Concierge scheduling link.

In both cases, Chili Piper applies your routing rules (territory, region, or round-robin) to assign the meeting to the right rep.

All bookings appear in Fin for Sales meeting-booking reports, including those made via scheduling links on non-Messenger channels. The booking date and time are also written to a Contact custom data attribute.


💡Tip

Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts


Did this answer your question?