🔥 Feature Spotlight: Secure credential requests

Credential Requests: 3 new updates :locked_with_key:

Recently, we released the new Credential Requests feature that lets you securely request connections for your automations.

Since then, we’ve shipped 3 updates that make requesting credentials easier and more flexible.


:one: Credential Request Reauthorization

With Credential Request Reauthorization, you can now prompt anyone to refresh an expiring connection with a simple click. Make automatically checks whether a refresh is actually needed before sending the request, so you’re not spamming people with unnecessary notifications. The recipient gets a secure, direct link to reauthorize, and the status updates for everyone the moment it’s done. No manual follow-ups needed for connection reauthorization.

:backhand_index_pointing_right: Documentation and step-by-step guide


:two: New Credential Requests API

If you’re creating credential requests programmatically, the v2 API POST endpoint simplifies things significantly.

What changed:

  • Only appName and appModules are required. No more splitting into separate keys and connections fields

  • type, appVersion, and scope are now handled automatically. Less boilerplate, fewer mistakes

  • Wildcard support: use appModules: ["*"] to cover all modules of an app in one go

:warning: Heads up: v1 will be deprecated on June 10, 2026. If you’re still on v1, now’s the time to migrate.

:hammer_and_wrench: API Documentation


:three: New MCP tool: set up your own connections directly from your AI coding assistant

If you’re using Make’s MCP integration, there’s a new tool available: credential-requests_create-by-credentials.

This lets you generate connection requests to yourself (e.g., “connect Gmail to Make”) directly from your IDE, without ever leaving your AI coding environment. It’s a natural fit for AI-assisted scenario building. Ask your assistant to set up the credential request as part of the automation build itself.

A few things worth knowing:

  • Requesting credentials from yourself is available to all MCP users on all plans, including free (no feature enablement criteria required)

  • If you want to send credential requests to other people, the standard feature enablement criteria apply

:hammer_and_wrench: MCP Documentation
:backhand_index_pointing_right: Introduction to MCP


We’re continuing to improve this. What would you add? Tell us :backhand_index_pointing_down:

Happy automating! :purple_circle:

Valery from Make

2 Likes