MAR'26
What do the MAR’26 Make.com updates really mean for your team?
We break down what matters, what to act on, and where it impacts your operations.
https://help.make.com/credential-requests-reauthorization-2fa-enforcement-logs
You’ll get faster credential lifecycle management: reauthorization of expired OAuth connections can now be requested from the existing credential request (no more creating a fresh request every time). For governance, 2FA enforcement changes are now logged in org audit logs, improving accountability for admins/owners. Operationally this reduces downtime risk during integrations and strengthens security controls visibility, but you’ll still need tight admin processes to ensure reauth and 2FA changes don’t happen without proper approvals.
https://help.make.com/new-version-of-api-endpoint-for-credential-requests-expanded-scenario-usage-tracking-enhanced-connection-filtering-and-app-updates
You need to migrate any API-based credential request automation to /api/v2/credential requests/requests/v2 before June 10, 2026 since v1 will be deprecated and v2 reduces required parameters, which may break brittle request-building code. Expanded scenario usage tracking beyond connections improves governance and impact analysis. Enhanced “my connections” filtering helps admin hygiene. App changes (Gemini/Claude date-time prompts, Make AI web search token-based credits) improve context accuracy and cost transparency, but require you to re-check prompts, budgets, and monitoring.
https://help.make.com/new-mms-options-app-updates
You’re getting modest integration hardening plus governance options. MMS now lets you create child organizations and adjust credit allocations, which can improve cost control and delegated administration for large automation portfolios. Several app changes reduce fragility: Anthropic model availability, Zendesk new OAuth refresh-token connection (legacy expires 2026-04-30), Typeform requires API region selection, and Fathom’s limit field bug fix prevents 401/404 surprises. Zoho region support removes connection friction. Biggest operational risk is connector changes breaking existing setups—plan migrations and validate in non-prod.
https://help.make.com/meet-the-new-make-ai-agents-app
You now get a dedicated “AI Agents” app tightly embedded in the scenario builder, with run/test/debug plus step-by-step reasoning, real-time tool invocation visibility, and optional AI-assisted tool-field population. For B2B ops this can speed agent development and reduce tab-hopping, making governance and troubleshooting easier. Public share links may improve reuse, but treat reasoning/audit outputs as operationally sensitive. In open beta, expect changes in reliability, pricing, and pricing/provider behavior—plan testing and controls before scaling.
https://help.make.com/pipedrive-api-v1-to-v2-transition-by-july-31-2026
You’ve got a time-bound breaking change: all Pipedrive API v1 modules/deprecated webhooks will stop working July 31, 2026, and you can’t create new scenarios with them. You must migrate to API v2 equivalents and switch token-based connections to Pipedrive OAuth for new compatibility. Some subscription-related modules have no direct v2 replacement, so you’ll need functional workarounds with other modules/filters. Audit scenarios now, prioritize high-volume/mission-critical flows, and test end-to-end to avoid sudden revenue/CRM data gaps.
https://help.make.com/introducing-scenario-recovery
Scenario recovery adds an automatic blueprint backup during scenario editing, so a crash, timeout, or lost connection no longer forces your team to rebuild unsaved changes. That reduces downtime and frustration, especially for large, complex automations. It’s helpful for productivity, but it’s not true autosave: after recovery you must still manually save, and the temporary blueprint can be overwritten. Build governance around review/save discipline and versioning.
https://help.make.com/openai-gpt-54-and-gpt-53-models-now-available-in-make
You can now use OpenAI GPT-5.4 and GPT-5.3 in Make for faster, cheaper, more accurate AI steps with expanded context and improved tool handling—useful for higher-volume lead scoring, enrichment, drafting, and AI-assisted routing. Practically, you’ll want to test output quality vs cost/latency, update prompt patterns for larger context, and tighten governance (validation, fallbacks, human-in-the-loop) since tool handling can change behavior. Also monitor upcoming model deprecations to avoid breakage.
https://help.make.com/make-grid-workspace-navigation-and-interaction-updates
More control over the Make Grid workspace matters mainly for teams maintaining complex automations: you can reorganize assets/folders/teams for clearer governance, see teammates in real time to reduce handoff friction, and open dependencies (Sheets/Docs/Slides) directly from the grid to speed troubleshooting and reviews. Consistent pan/zoom and right-click/pinch navigation helps everyday usability. Risk: layout changes can disrupt conventions and complicate onboarding unless you standardize folder structure and access rules.
https://help.make.com/mondaycom-app-v1-to-v2-transition-by-may-1-2026
Your monday.com integrations in Make must be migrated from app v1 to v2 by May 1, 2026 or workflows may fail. You’ll likely need to remap fields and replace references: discontinued fields (border, var name, done colors, labels position/color mapping, v2 hide footer) and a timestamp change (use updated at instead of timestamp). This is operationally significant because it can silently break CRM/lead handoffs triggered by monday events; prioritize scenario audits, automated swapping, and thorough testing.
https://help.make.com/introducing-mcp-toolboxes
Granular MCP toolboxes let you package specific AI tool scenarios (e.g., CRM update, lead enrichment, ticket actions) with selective access and shared authorization keys. For B2B automation, that’s a governance win: fewer “AI can do everything” risks, clearer audit trails of which tool runs, and easier separation between internal vs client-facing workflows. It also simplifies scaling via a single MCP server and per-toolbox URLs. Watch for maintainability: you’ll need disciplined toolbox naming, versioning, and key lifecycle management to prevent tool sprawl and unexpected access.
https://help.make.com/openai-gpt-54-nano-and-mini-now-available-in-make
You now have faster, cheaper GPT-5.4 mini and nano options inside Make, which can materially reduce cost and latency for high-volume, multi-step workflows like extraction, classification, routing, triage, and intent detection. Practically, use mini/nano for subtasks and keep larger models for orchestration when quality matters. Watch for output variance and governance drift in automated decisions; add validation, confidence thresholds, and human review on edge cases to keep data quality consistent at scale.
https://help.make.com/new-feature-if-else-and-merge
If-else and merge modules in beta let you choose exactly one conditional path and then reconnect to a single downstream flow, avoiding duplicated modules. For RevOps you’ll reduce scenario bloat and inconsistency in lead/quote/service handoffs, while improving maintainability. It’s a distinct alternative to routers (which still execute multiple branches). Use it for mutually exclusive logic; keep an eye on governance/testing to ensure only one branch truly triggers. Credit usage won’t change, since no credits are used.
https://help.make.com/openai-model-deprecations-on-march-26-2026
OpenAI model deprecations on March 26, 2026 won’t break your Make.com scenarios, because requests tied to removed GPT-4-* variants should automatically be routed to GPT-4.1. That’s good for uptime, but expect small output changes that can affect downstream logic, lead scoring, routing rules, and human review workflows. You likely still need governance: identify any OpenAI modules using the soon-deprecated models, run regression checks on critical automations, and update documentation/tests to avoid silent behavior drift.
https://help.make.com/2026
v2 for credential-request APIs plus expanded scenario usage tracking and better connection filtering matters because it strengthens governance and operating control as you scale integrations across teams/vendors. You’ll likely need to validate credential reauthorization flows, update any custom logic relying on the older endpoint, and tighten auditability (especially around 2FA enforcement). The new filters help reduce “wrong connection” incidents. Net value is high for enterprise reliability; only minor value if you run few scenarios with stable credentials.
https://help.make.com/make-now-a-built-in-connector-on-anthropic-claude
You can now connect Make to Anthropic Claude via a built-in connector (Make MCP) without managing URLs/tokens manually, and Claude can trigger/select scenarios during chat. For RevOps, this can speed up prototyping and reduce onboarding friction, especially for controlled “assistive” workflows. Operationally, tighten governance: constrain which scenarios Claude can run, enforce least-privilege scopes, and add logging/approvals where actions impact CRM, lead routing, or ticketing. Value is highest for internal agent workflows; risk is uncontrolled scenario execution if permissions aren’t tightly scoped.
https://help.make.com/scenario-builder-improvements-new-app-and-ai-model-updates
You get a faster workflow for building and organizing scenarios (direct move to folders without a save/exit cycle), which helps RevOps teams iterate safely during production changes. The consolidated encryption/security guide improves governance and repeatability for teams standardizing crypto and data-handling patterns. New HTTP “resolve URL” reduces redirect-handling bugs. The Google Cloud Storage Transfer app broadens operational automation. AI model updates auto-migrating Gemini 3 Pro preview reduce breakage, but you should validate outputs and chunking/transcription behavior for data quality and cost before scaling.