Skip to main content
Use Make through Corsair: one client, typed API calls. Each Make organization lives in one zone (eu1, eu2, us1, us2, celonis-eu1, celonis-us1), so each connected account stores its zone (the 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
With multiTenancy: true, scope calls with corsair.withTenant(id). See Quick start for KEK + Hub keys, and Multi-tenancy for account isolation.
3

Choose authentication

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 team
Rename a scenario
See the full list on the API page.

What’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.