Alta integrates with ChiliPiper as a Flows action provider. Connect once with a ChiliPiper API key, then drop a Custom API Call step into any Flow to hit any endpoint on ChiliPiper's API — Alta handles the authentication for you.
Who this is for: RevOps admins and power users building Flows that need to talk to ChiliPiper directly — for example, checking a rep's availability, booking a meeting from a Flow, or pulling routing/queue data — beyond what the built-in Meeting Tools setup covers.
Before you start
A ChiliPiper account with an API key generated for it. ChiliPiper issues these from within their own product — ask your ChiliPiper admin if you don't have one.
A Flow you can edit. If you haven't built one yet, see How to Build and Manage Flows in Alta.
The ChiliPiper API endpoint(s) you want to call, and their expected method and payload — Alta's Custom API Call step is a thin, authenticated pass-through, not a set of prebuilt ChiliPiper actions.
This is not the same as ChiliPiper Meeting Tools
If you just want Alex or a chat/voice assistant to check availability and book a meeting through ChiliPiper during a conversation, that's the separate Meeting Tools feature (see the Meeting Tools Setup Guide) — no Flow required. This article covers the ChiliPiper connector inside Flows, which is a different, lower-level integration meant for custom automations.
Step 1: Connect ChiliPiper in Alta
Go to Flows and open or create a Flow.
Add a ChiliPiper action — you'll find it in the Productivity category, described as "Check availability and book meetings with your ChiliPiper account."
When prompted, create a new ChiliPiper connection.
Paste your key into the API Key field (required) and save.
The connection is reusable — every other ChiliPiper Custom API Call step, in this Flow or any other, can share it.
Step 2: Configure the Custom API Call action
ChiliPiper exposes a single action, Custom API Call — "Make a custom authenticated request to any ChiliPiper API endpoint." Its fields:
URL (required) — the full URL or a relative path against ChiliPiper's base API host. The field description spells this out: you can use the full URL or the relative path to the base URL, i.e.
https://fire.chilipiper.com/resourceor/resource.Method (required) — a dropdown with GET, POST, PUT, DELETE, or PATCH. Note there's no HEAD or OPTIONS here, unlike the standalone HTTP integration's Send HTTP Request step.
Headers — an optional key/value object for any extra headers your call needs.
Query Parameters — an optional key/value object, appended to the URL as
?key=value&....Body Type — defaults to None. Switch it to JSON to reveal a JSON Body editor.
Tips and common pitfalls
Don't set your own Authorization header. Alta injects the Bearer token from your ChiliPiper connection automatically, and it's applied after your own Headers — so if you add an
Authorizationheader yourself, it gets silently overwritten by the connection's token rather than erroring.Body Type has to be switched before the field shows up. If you type into a body field while Body Type is still on None and don't switch it to JSON, nothing is sent — the body is silently dropped.
Only success (2xx) is treated as success. Any non-2xx response fails the step outright. Unlike the standalone HTTP integration, this action has no built-in "On Failure" retry-policy dropdown — you only get the standard step-level Continue on failure and Retry on failure toggles every Flow action has.
Public hosts only. Calls are restricted to public internet hosts as an anti-SSRF measure — you can't point this at a localhost or private-network address for testing.
Test with a small payload first. Run the Flow once, open the Runs tab, and inspect the request and response before wiring downstream steps to the output.