Make.com Release Notes | FEB'26
What do the FEB’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/filter-copying-smarter-app-search-and-scenario-sorting
Copying filters between modules should speed up and standardize complex branching/error-handling, reducing copy/paste mistakes. Smarter app search and scenario sorting improve builder productivity, especially with shared libraries. Biggest value comes when you scale scenario complexity; still validate pasted filters and keep naming/versioning governance so changes don’t silently diverge.
https://help.make.com/deprecated-openai-model-automatically-replaced
Your existing OpenAI-based scenarios should keep running automatically, with any selected deprecated ChatGPT 4o latest model transparently migrated to gpt-4o-2024-08-06. Expect small output differences, so review critical pipelines (lead qualification, customer responses, scoring) for regression and update prompts/thresholds if needed.
https://help.make.com/claude-opus-46-now-available-in-make
Claude Opus 4.6 availability in Make.com enables higher-capability AI steps (long-context document/code processing and more autonomous, tool-using reasoning) for multi-step workflows. You can improve large-asset enrichment, policy/Q&A, and complex routing, but agentic behavior increases governance needs: add human approvals, timeouts, logging, and cost controls to avoid unpredictable outcomes.
https://help.make.com/gemini-31-pro-preview-model-now-available-in-make
Gemini 3.1 Pro preview in Make improves agentic, multi-step reasoning: faster responses, lower credit usage, and better tool-use reliability. For your automations, it’s a chance to upgrade AI steps (lead scoring, enrichment, drafting, orchestration). Watch model drift, cost/throughput changes, and re-test governance prompts, tool permissions, and 2FA/security controls before scaling.
https://help.make.com/introducing-credential-requests
Credential requests can let you onboard clients/partners into your Make org as guests to supply and manage specific connection credentials via a single secure link, avoiding password sharing and speeding authorization. Useful for scalable RevOps/implementation flows, but adds governance work: limit scopes, audit requests, and test revocation behavior before relying on it for critical scenarios.
https://help.make.com/introducing-two-factor-authentication-enforcement
You can now centrally enforce 2FA for Make-native email/password users, which meaningfully reduces account takeover risk and improves governance. Plan for operational impact: SSO/SAML users aren’t covered, so enforce MFA in your IdP instead. Verify existing access methods and test for admin/break-glass workflows.