Version2.0.0
Categoryproductivity
AuthAPI key
Tools11
Transportstdio
LicenceMIT
01
What it does
The app, in its own words.
Make.com automation — trigger scenarios via webhooks (no token needed) and manage scenarios via the account API: create, read, update, delete, clone, start, stop, list, run, and inspect blueprints.
02
Tools
11 tools the agent can call.
Every one is declared with typed parameters and returns structured results, so the host can render them instead of narrating them.
- clone-scenarioClone an existing Make.com scenario by id (requires MAKE_API_TOKEN in user secrets). Optionally set a new name or folder. Returns the cloned scenario summary.
- create-scenarioCreate a new Make.com scenario (requires MAKE_API_TOKEN in user secrets). The `blueprint` is provided as a JSON object and is serialized internally. Returns { scenarioId, name, teamId, folderId, isActive, region, url }. Some Make plans require a paid subscription to use this endpoint.
- delete-scenarioDelete a Make.com scenario by id (requires MAKE_API_TOKEN in user secrets). This action is irreversible. Returns { scenarioId, deleted, region }.
- get-scenarioGet a single Make.com scenario by id (requires MAKE_API_TOKEN in user secrets). Returns the scenario object as returned by Make.
- get-scenario-blueprintGet the blueprint of a Make.com scenario by id (requires MAKE_API_TOKEN in user secrets). Returns { scenarioId, blueprint } where blueprint is a parsed JSON object when possible.
- list-scenariosList Make.com scenarios for the configured account (requires MAKE_API_TOKEN in user secrets). Optionally filter by teamId and page with limit/offset. Returns { scenarios: [{ id, name, isActive, isPaused, teamId }], returned, total, offset, limit, hasMore, nextOffset, teamId, region }. When hasMore is true, call again with offset=nextOffset to fetch the next page.
- run-scenarioRun a Make.com scenario on demand by id (requires MAKE_API_TOKEN in user secrets). Pass optional `data` for the run inputs and `responsive: true` to wait for and return its outputs. Returns { scenarioId, executionId, status, responsive, outputs }.
- start-scenarioActivate (start) a Make.com scenario by id (requires MAKE_API_TOKEN in user secrets). Returns { scenarioId, isActive, region }.
- stop-scenarioPause (stop) a Make.com scenario by id (requires MAKE_API_TOKEN in user secrets). Returns { scenarioId, isActive, region }.
- trigger-webhookTrigger a Make.com scenario by POSTing a JSON payload to its webhook URL. No account token required — the user supplies the webhook URL (https://hook.<region>.make.com/<token>). Returns { delivered, statusCode, webhookHost, region, responseType, response }.
- update-scenarioUpdate an existing Make.com scenario by id (requires MAKE_API_TOKEN in user secrets). Supports updating name, blueprint (as a JSON object), scheduling, and folderId. Returns the updated scenario summary.
03
Auth and permissions
What it asks for.
Declared in the manifest, in advance. The app cannot reach anything it did not ask for here.
User secrets
MAKE_API_TOKENMAKE_REGION
Reading further
The manifest and the source for Make live in the monorepo, alongside the other apps.