Developer & CI · wired today
Drive Make (Integromat) with governed agents
Build, review and release state is where agents earn their keep. The Make (Integromat) connector is one of 205 executable connectors and gives agents 10 read-only tools, with the credential held in the vault and every call receipted.
What agents can run against Make (Integromat)
| Tool | What it does |
|---|---|
get_me | Get the Make user the stored API token belongs to (name, email, locale, last login, 2FA status) |
list_organizations | List the Make organizations the token's user belongs to, with their zone, plan and scenario counts |
list_teams | List the teams inside one Make organization |
list_scenarios | List the scenarios in the team the stored credential is scoped to, with their active/paused state and next scheduled run |
get_scenario | Get one Make scenario by ID, including its scheduling, validity and last edit |
list_scenario_logs | List recent execution logs for one Make scenario (status, duration, operations, data transfer) |
list_connections | List the app connections available to the team the stored credential is scoped to, with their account labels and expiry |
list_data_stores | List the data stores in the team the stored credential is scoped to, with record counts and size usage |
list_hooks | List the webhooks (hooks) in the team the stored credential is scoped to, with queue depth and enabled state. The hook's callable URL is deliberately not returned |
list_incomplete_executions | List incomplete executions (the dead letter queue) for one Make scenario, with the failure reason and retry attempts |
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Make (Integromat) connector needs
You provide API token, team ID from your Make (Integromat) account; Quox sends it as an API key sent as a header. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Make (Integromat)'s own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Make (Integromat) API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
Make (Integromat) integration FAQ
What can Quox agents do with Make (Integromat)?
Agents can run 10 read-only tools against Make (Integromat): get me, list organizations, list teams, list scenarios, get scenario and more. Every call is receipted in the evidence trail.
What does the Make (Integromat) integration need?
You provide API token, team ID from your Make (Integromat) account; Quox sends it as an API key sent as a header. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Make (Integromat) credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Make (Integromat) connector?
This connector was blind shape-proven against the real Make (Integromat) API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.