Use Inbox Triage with Make

Add the connection

1. In a scenario, add a module and search for MCP Client. Choose Call a Tool.
2. Click Create a connection. Under MCP server, choose + new mcp server for a custom server rather than one of Make's pre-verified ones.
3. URL: https://getinboxtriage.com/mcp.
4. Choose your sign-in method (see below), then save the connection.
5. Pick a tool from the Tool name dropdown, for example show_inbox. Make fetches the tool's arguments and renders them as normal fields, so you can set filter to needs without writing any JSON.

Sign in with OAuth

If you would rather not paste a key, choose the OAuth option in the connection dialog. Make's redirect address is already accepted on our side. Sign in to Inbox Triage and choose Allow.

Or use an API key

Create a key in Settings, under Advanced (see API keys), then paste it into the connection's API Key / Access Token field. Make sends it as Authorization: Bearer <key>.

Your first scenario

A simple daily check: a scheduled scenario that calls MCP Client > Call a Tool with show_inbox and filter set to needs, then a second module (a Slack message, an email, or anything else Make can send to) that posts the result's sayToHuman line. For a step that lets an AI model pick the tool itself, use Execute an Action with AI instead: the same connection, a Tools list of which tools the AI may use, an AI provider (Make's own credits, OpenAI, or Claude), and a task description such as "Summarize unread mail from today."

What it will not do on its own

Make has no way to show Inbox Triage's in-chat approval prompt, so a connection through Make is always treated as unattended, whether it signs in with OAuth or an API key. Calling send_draft, confirm_mark_spam, or confirm_unsubscribe from Make never sends, reports spam, or unsubscribes by itself. Instead the tool's result carries an approveUrl link: the person opens it, signed in to Inbox Triage, and only their click there completes the action. Leave those tools, plus set_send_enabled and start_imap_secret_capture, out of any Execute an Action with AI module's tool list, since the link is all the module gets back either way.

Known issues

• The MCP Client app is in open beta. Make has not published a timeout or payload limit for it, so test your own scenario before relying on it for anything time sensitive.
• If a connection has trouble, Make's own documentation for its MCP server (the opposite direction from this) mentions adding /stateless, /stream, or /sse to a server's URL. That note is not confirmed to apply to the MCP Client app's connections. Try the plain address first, and only experiment with a suffix if the connection will not complete.

Can I connect two Gmail accounts through Make?

Yes. Connect both inboxes in Inbox Triage first, then one Make connection can reach both through the same tools. Name the inbox you want in each call, or leave it out to mean all of them.

Does Make need my Gmail password?

No. Make only ever gets an API key or an OAuth token for Inbox Triage. Your mail passwords, and Google or Microsoft sign-in tokens, stay with Inbox Triage and are never sent to Make.

Which tools should I let the AI use in an Execute an Action with AI step?

Reading, searching, and drafting tools are safe to include. Leave out send_draft, confirm_mark_spam, confirm_unsubscribe, set_send_enabled, and start_imap_secret_capture so an approval link, not a Make scenario, decides when those happen.

Do I need Make credits for the AI step?

Only for Execute an Action with AI, where you pick an AI provider: Make's own credits, your OpenAI key, or your Claude key. Call a Tool needs no AI provider at all, since you choose the tool yourself.

Why did my Make OAuth sign-in fail?

Check that you chose the OAuth option rather than pasting a key, and that you completed the Allow step on the Inbox Triage sign-in page. If it still fails, the API key path works the same tools without OAuth.