Make (Integromat) — operate scenarios by REST API and MCP

Drive a live Make.com account from code or an agent: create scenarios from a blueprint, activate/run/stop/clone/delete them, and manage the connections, hooks, data stores, and teams around them. This skill owns the operate half — the API v2 calls and the MCP wiring. It does not design the flow; what a scenario should do (trigger, routes, mapping, dedup, error handler) lives in automation-flows, and the Make-vs-n8n-vs-Zapier billing call lives in automation-strategy. Bring the design here, and this skill turns it into API payloads and MCP tool calls.

Reality up top (verify at author time — Make ships fast):

• REST API v2 is GA. Base URL is zoned: https://{zone}.make.com/api/v2.
• The Make MCP server is GA and free on every plan — you only pay the scenario credits a run consumes. Cloud MCP has two tool tiers: run tools (all plans) and management tools (paid).