zone field) next to its API token; the zone plugin option overrides it for single-account setups. The token needs the scopes for the operations you call. Scenario runs and replays can trigger external actions and consume credits. The client does not retry failed requests automatically, including quota-related 429 responses. Buildtime variables are not available on Make’s free plan, which answers those calls with 403 (SC403).
What you get:
- 24 typed API operations
Setup
1
Install
2
Add the plugin
corsair.ts
multiTenancy: true, scope calls with corsair.withTenant(id). See Quick start for KEK + Hub keys, and Multi-tenancy for account isolation.3
Choose authentication
- API Key (Recommended)
Store the Make API key before the first call: More: API Key
pnpm corsair setup --plugin=make --tenant=acme api_key=<your-key> (leave out --tenant without multiTenancy), or pass it as key in the plugin options. With Hub, each tenant enters their own key on the connect page. See API key auth.Each connected account stores its Make zone (the zone field, for example eu1, the subdomain of the Make URL you sign in at) next to its API token: pnpm corsair setup --plugin=make --tenant=acme zone=eu1, or the connect page with Hub. Set the zone option only for a single-account setup; it overrides the stored value.4
Connect a tenant
Mint a connect link and send the tenant to it. Hub hosts the page and delivers the result to your app — see Connect / OAuth.
Example API calls
List scenarios for a teamWhat’s next
API reference
Every
make.api.* operation with input and output types.Connect / OAuth
createLink, Hub delivery, and tenant connect flows.
Use with agents
Expose this plugin’s operations as MCP tools.