Integration · Sell and serve

Chili Piper and Meteor AI agents

Connect Chili Piper to a WhatsApp Met: run your Concierge routers, check your team's availability and book the meeting with the official MCP.

Book a demo See every integration

How does Chili Piper connect to Meteor?

With the Chili Piper ready connector, your Met uses the official Chili Piper MCP server on your account, authorized once with OAuth by an Admin user. When a prospect asks for a demo on WhatsApp, the Met can run the Concierge router you already set up, check the combined availability of your reps and book the meeting. It also returns meeting details, records a no show, starts the handoff of a prospect from the person who qualifies to the person who closes, and looks up users, teams and routing rules. OAuth has to be enabled for your account: if the sign in window does not appear, Chili Piper asks you to contact its support.

What it automates

What a Meteor Met does with Chili Piper

Book the demo inside the chat

The prospect asks for a demo on WhatsApp. Your Met runs the Concierge router you use on your form, checks the team's availability and books the meeting with the rep Chili Piper picked.

Hand the prospect to the closer

Once the Met has qualified the prospect in the conversation, it starts the handoff and books the meeting with the closing rep, as the person who qualifies would.

Answer when the meeting is

If the prospect asks about their meeting, the Met returns the meeting details and replies with what Chili Piper has on record.

Check why a case went to whom

From the internal chat, your team asks the Met for the Concierge log and the routing rules to understand which rep a prospect was assigned to and why.

18 tools

Everything your Met can ask Chili Piper for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`concierge_list_routers`	Lists the Concierge routers in your account, to pick which one to run.
`concierge_route_by_slug`	Runs a Concierge router from its slug, so Chili Piper makes the routing decision.
`concierge_schedule`	Books through Concierge. Chili Piper puts it under the same scheduling permission as routing by slug.
`concierge_logs`	Returns the Concierge log to inspect the routing decisions that were made.
`availability_slots`	Shows the combined availability of your reps.
`handoff_init`	Starts a handoff so the person who qualifies the prospect books the meeting for the person who closes.
`handoff_schedule`	Books the meeting of a handoff between the person who qualifies and the person who closes.
`meeting_list_put`	Lists meetings, to review no shows and the lifecycle of each meeting.
`meeting_get`	Returns the details of a meeting.
`meeting_cancel`	Cancels a meeting. Starts turned off.
`meeting_noshow`	Records a meeting no show. It uses the same modify meetings permission as cancelling.
`user_find`	Finds users in your Chili Piper account.
`user_read`	Reads the details of a Chili Piper user.
`team_list_put`	Lists the teams in your account.
`workspace_list`	Lists the workspaces in your Chili Piper account.
`workspace_list_users`	Lists the users of a workspace.
`rule_list`	Lists routing rules, to audit who gets each case.
`rule_get`	Returns the details of a routing rule.

The limits

What the Chili Piper integration does NOT do

We would rather say it here than have you find out during rollout.

It does not change your routing rules or your round robin queues with the default setup. The actions that create or modify rules and the one that adjusts distributions start turned off until the admin turns them on.
It does not replace your Chili Piper setup. Routers, rules and calendars are built in Chili Piper; the Met runs and checks what already exists.
It does not ask you for confirmation in the chat before booking. The admin chooses in Connections which actions stay on; cancelling meetings starts turned off.
It does not connect through OAuth without an Admin user. Chili Piper requires the Admin role for that path, and it also has to be enabled for your account.
It does not pay your Chili Piper plan. Usage runs on your account and plan; Meteor does not resell Chili Piper.

Before you start

What you need to connect Chili Piper

1

A Chili Piper account with Concierge set up

The account where your team already has routers, rules and rep calendars. The Met runs what is already built.
2

Connect Chili Piper in Met

In Met, open Connections → Chili Piper → Connect. A Chili Piper window opens so an Admin user signs in and authorizes Met. If the window does not appear, Chili Piper asks you to contact its support to enable OAuth on your account.
3

Decide which actions stay on

The Met workspace admin chooses which actions stay on. Cancelling meetings, creating or modifying rules and adjusting distributions start turned off.

Frequently asked questions

Questions about Chili Piper and Meteor

Because Chili Piper requires it to connect its MCP through OAuth: only Admins have the organization wide permissions the server needs to work across all its tools.

No. Chili Piper decides with the Concierge router and your routing rules. The Met runs the router and books with the result.

Only if the admin turns that action on, because cancelling meetings starts turned off. With it off, the Met lets your team know so they cancel it in Chili Piper.

You do, with your Chili Piper account and plan. Met does not charge for the calls your Met makes to Chili Piper.

Step by step