Guide intermediate

Make Ships CLI, API v2, and a Module Migrator in One April Release Window

Make's mid-April 2026 release notes add a terminal CLI for all users, a v2 API with extended usage tracking, and a Module Migrator that detects and upgrades deprecated modules. Here is what changed and how to use it.

Published May 1, 2026 by Pondero Editorial
Table of Contents
Pondero, operated by Hildebrandt AI LLC, earns a commission from some links on this page. This does not influence our editorial decisions. Read our affiliate disclosure

Make Ships CLI, API v2, and a Module Migrator in One April Release Window

In brief: Make rolled out three meaningful upgrades between April 15 and April 17, 2026. The Make CLI is now generally available, the Make API v2 adds credential requests and richer usage tracking, and the new Module Migrator finds deprecated modules in your scenarios and upgrades them in place.

What Changed

Make’s official release notes log three upgrades in a 72-hour window. On April 15, 2026, Make introduced the Module Migrator, a tool that scans existing scenarios for deprecated modules, applies upgrades automatically where it can, and surfaces warnings with manual-fix instructions for the rest. On April 17, 2026, Make shipped the Make API v2 with credential requests, extended usage tracking, and new filtering options for connections. The same day, Make made the Make CLI generally available so every user can hit Make resources from the terminal instead of clicking through the web app.

The CLI change is the biggest culture shift for power users. Before this release, scenario edits, deploys, and inspection required the visual builder. With the CLI, scripted workflows can list scenarios, push updates, run scenarios on demand, and pull logs the way a developer already works with git, wrangler, or vercel.

The Module Migrator is less flashy but solves a real operational pain. Make routinely deprecates app modules when vendors change auth flows or endpoint shapes. Until April 15, fixing a deprecation meant opening every scenario, finding the offending step, and rebuilding it by hand. The Migrator now does the detection step, performs the swap when the new module is a drop-in replacement, and tells you which scenarios still need a human edit.

Why It Matters

For ops teams that already treat Make as production infrastructure, the CLI + API v2 combination is the missing link for proper CI workflows. You can now version-control scenario definitions, gate deployments on a pull request review, and run scripted health checks against the API v2 usage endpoints. That is the basic shape of a deployment pipeline that Zapier and n8n users have asked for repeatedly, and Make is the first of the three to ship a first-party CLI.

For teams running 50 or more scenarios, the Module Migrator removes a tax that nobody enjoys paying. We have seen ops teams spend a half-day per quarter chasing deprecation warnings across legacy scenarios. Automating the detection and the easy upgrades cuts that work down to a triage queue of genuinely-broken cases.

The tradeoff: the CLI and API v2 reward teams that can write a small amount of glue code. If your team builds scenarios in the visual editor and never touches a terminal, the Module Migrator is the release that helps you today, and the CLI is a capability you can grow into later.

How to Use It

Make CLI. Install via the package manager flow Make documents in its release notes, authenticate with a Make API token, and start with read-only commands like listing scenarios and inspecting connections. Once those work, move to scripted deploys. The CLI uses the same auth model as the API, so anything you can do in the dashboard you can drive from the command line.

Make API v2. Update existing API integrations to point at the v2 endpoints if you want credential requests and the new connection filters. The v1 API still works, but new features ship to v2 first. The extended usage tracking is the most interesting addition for finance and ops teams who want per-scenario operation cost data instead of an aggregate org bill.

Module Migrator. Open the Module Migrator from the scenario editor and run a workspace scan. Review the auto-upgrade list before applying. Triage the manual-fix list against your scenario importance: production-critical scenarios first, archived test scenarios last. Make’s release notes include the specific instructions for the manual cases.

Pricing is unchanged. All three features are available across existing Make plans, with the usual API rate limits applying to v2 calls.

If you are evaluating Make against Zapier or n8n for a 2026 build, the CLI plus API v2 closes the developer-experience gap that has historically tilted technical teams toward n8n. The Module Migrator is the kind of platform-maintenance feature that signals Make is investing in long-term operability, not just new connectors.

This post is part of Pondero’s daily coverage of AI tool updates. See all guides →