Make integration

In short

List scenarios, run them on demand and read their logs. Connect it on the Integrations page; your app then calls Make through Sapilon without ever holding a Make credential.

Lets your app list the scenarios in your Make organisation, run one on demand with input data, and read its run history. It cannot edit or delete scenarios.

Connecting

On the Integrations page choose Connect on Make and fill in:

Zone — The part before .make.com in your Make address: eu1, eu2, us1 or us2.
API token — Make → your avatar → Profile → API access → Add token. Give it scenarios:read and scenarios:run.

Sapilon checks the key with the provider before it saves it, and stores it encrypted; it is never shown again.

What your app can do

Only these requests are available; anything else is refused.

GET /users/me
GET /organizations
GET /teams
GET /scenarios
GET /scenarios/*
POST /scenarios/*/run
GET /scenarios/*/logs

How the agent uses it

Use integrations.request('make', …); paths are relative to https://<zone>.make.com/api/v2.

GET /users/me, GET /organizations, GET /teams (query: { organizationId }).
GET /scenarios — needs query: { teamId } or { organizationId }. GET /scenarios/{id} — one, with its isActive and schedule.
POST /scenarios/{id}/run — run now. Example: { method: 'POST', path: '/scenarios/9312/run', body: { data: { orderId: 'A-17' }, responsive: true } }. With responsive: true the answer waits for the run (up to 40 s) and carries its outputs.
GET /scenarios/{id}/logs — past runs and their status.

The scenario must be active and its trigger set to “on demand” or a webhook to accept a run.