Make.com

Connect Make.com by saving your own API token, after checking it actually works. Create the token in Make: avatar (bottom-left) -> Profile -> API tab -> Add token. The account's zone (eu1/eu2/us1/us2) is auto-detected -- you don't need to know it.

Disconnect Make.com: deletes the saved API token and zone. Existing scenarios in your Make account are never touched.

Check whether Make.com is currently connected (does not reveal the saved token).

List the Make.com teams your connected account belongs to. Needed once to pick which team's scenarios to show -- Make requires a specific team (or organization) scope, it has no single global scenario list.

Pick which Make.com team's scenarios to show. Run list_make_teams first to see the available team ids. This is a standing choice -- it stays selected until changed again.

List your Make.com scenarios for the selected team -- name, active/paused/invalid state, and last edit time. Run connect_make and select_team first if you haven't yet.

Run one of your Make.com scenarios right now, by scenario_id (see list_scenarios). This executes the scenario's real actions in Make immediately -- sending emails, writing to connected apps, etc. There is no dry-run or undo, so this always asks for confirm=true first.

Activate (turn on/schedule) or deactivate (pause) a Make.com scenario by scenario_id (see list_scenarios). Reversible -- flip it back any time -- so unlike run_scenario this needs no confirmation.

Save (or clear, with an empty webhook_url) the Make Custom Webhook trigger URL that send_webhook_event will POST to. Get this URL by adding a 'Custom Webhook' module as the first step of a Make scenario and copying its URL. This is independent of connect_make.

Check whether an outgoing Make webhook URL is configured (does not reveal the URL itself).

Send an event payload to the configured Make webhook right now -- for other Imperal apps/automations to trigger a Make scenario. Run set_outgoing_webhook first if you haven't configured one yet.

Read a scenario's actual module list (blueprint) -- what each numbered step in the flow is and does, in the same order the Make editor numbers them. This is how to answer 'what is module N' or 'what does the Nth step do'.

List the app connections in your Make team -- what a scenario's modules actually authenticate as (which account/app each connection is for, and whether it's about to expire).

Permanently delete a Make connection. Any scenario using it will stop working once it's gone.

Rename a Make connection's display name.

Test whether a Make connection's credentials still work.

List the data stores (Make's own key/value storage) in your team, with record counts and size.

Create a new Make data store (key/value storage a scenario can read/write).

Permanently delete a Make data store and all of its records.

List the incoming webhooks/mailhooks (Make 'hooks') in your team -- the triggers scenarios listen on, with their URL and whether they're enabled.

Enable or disable a Make hook (incoming webhook/mailhook) without deleting it.

Permanently remove a Make hook. Any scenario using it will stop working once it's gone.

List a scenario's incomplete executions (failed runs held for manual resolution instead of being discarded) -- what failed, when, and whether it's already resolved.

Retry one incomplete (failed) scenario execution after fixing the underlying issue.

Permanently delete one scenario's incomplete executions -- explicit ids, or all=true with confirm=true to clear every one.

Activate or deactivate SEVERAL Make scenarios in one call by explicit scenario ids.

Run SEVERAL Make scenarios right now, by explicit scenario ids. Executes real actions in each scenario immediately -- no dry-run, always requires confirm=true.

Permanently delete SEVERAL Make connections at once, by explicit connection ids. Any scenario using one will stop working once it's gone.

Permanently remove SEVERAL Make hooks at once, by explicit hook ids. Any scenario using one will stop working once it's gone.

Preview changing ONE field inside a module's own settings (its mapper -- e.g. an AI module's prompt text) without writing anything. Shows the current value, the proposed value, and a state token that apply_update_blueprint_module must be given unchanged. Use get_scenario_blueprint's raw_config on the module first to see the exact field names available.

Apply a previously previewed change to ONE field inside a module's own settings (e.g. an AI module's prompt text). Re-reads the exact scenario blueprint and refuses to write if it changed since preview.

Create a brand-new, empty Make scenario in a team. You'll still need to add modules via preview_update_blueprint_module/apply_update_blueprint_module or the Make editor -- this just creates the container.

Delete a Make scenario. Make keeps it recoverable in Trash for 30 days -- use restore_scenario to bring it back within that window.

Restore a deleted Make scenario from Trash, within Make's 30-day recovery window.

Clone an existing Make scenario -- same modules/connections, a new id and name. Optionally into a different team.

Change how/when a scenario runs (interval, cron, on-demand, etc.) without touching its modules.

List a scenario's buildtime (installation-time) variables -- the named inputs it was configured with, separate from its runtime data.

Add a new buildtime variable to a scenario, or update an existing one's value.

Remove a buildtime variable from a scenario.

Read a scenario's own operations/data-transfer usage history -- how much of your Make plan quota it has consumed, per day.

List a scenario's own operations/data-transfer usage history -- how much of your Make quota each run consumed, most recent first.

Read one scenario execution in full -- its actual outputs, or on failure the error message and which module/app caused it.

Stop a currently-running scenario execution.

Preview adding a brand-new module to a scenario's flow, without writing anything. Shows where it will land and a state token that apply_add_blueprint_module must be given unchanged. Use get_scenario_blueprint on a similar existing module first to see the exact app_module id and mapper shape to copy.

Apply a previously previewed new module addition to a scenario. Re-reads the exact scenario blueprint and refuses to write if it changed since preview.

Preview removing one module from a scenario's flow, without writing anything. Shows a state token that apply_delete_blueprint_module must be given unchanged.

Apply a previously previewed module removal from a scenario. Re-reads the exact scenario blueprint and refuses to write if it changed since preview.

List the Make.com organizations the connected account belongs to -- the level above teams (an organization can contain several teams).

List the people with access to a Make team and their role -- Team Member, Team Admin, Team Monitoring, or a custom org role (shown by its numeric id).

List the connected Make user's own API tokens -- label, scopes, creation date, and a masked form. Never exposes a usable secret; use create_api_token to mint a new one when a real value is needed.

Create a brand-new Make API token for the CONNECTED user's own account. The secret value is returned exactly ONCE, same as Make's own UI -- it cannot be retrieved again afterwards. This mints a real, usable credential -- treat it like creating a password.

Permanently delete one of the connected user's own Make API tokens. Anything using it (external scripts, other integrations) stops working immediately.

Create a new incoming webhook/mailhook (Make 'hook') in a team -- a fresh trigger point a scenario can listen on. For a generic HTTP webhook, type_name='gateway-webhook' works without a connection_id; app-specific hook types may need one -- check an existing similar hook via list_hooks first when unsure.