Use Inbox Triage with n8n
https://getinboxtriage.com/mcp with HTTP Streamable transport, and
authenticate with Bearer or OAuth2.Add the node
- Add a Schedule Trigger node, or start the workflow manually while testing.
- Add an MCP Client node for a plain, fixed tool call with no AI model involved.
- MCP Endpoint URL:
https://getinboxtriage.com/mcp. - Server Transport: HTTP Streamable.
- Choose your authentication (see below).
- Tool: pick
show_inboxfrom the list n8n fetches from the server. Input Mode: JSON, with{"filter": "needs"}as the input.
For a workflow where an AI model decides which tool to call, use an AI Agent node instead, and add
an MCP Client Tool sub-node under its Tools with the same endpoint, transport, and authentication.
Set Tools to Include to All Except, and exclude send_draft,
confirm_mark_spam, confirm_unsubscribe, set_send_enabled, and
start_imap_secret_capture.
Sign in with OAuth
Choose Authentication: MCP OAuth2, create a new MCP credential, and leave Use dynamic client registration turned on with the Authorize and Token URL fields blank: n8n discovers them from the server on its own (dynamic client registration needs n8n 1.119.0 or later). Sign in to Inbox Triage and choose Allow. n8n's callback path is already accepted on our side, and n8n refreshes the token on its own after it expires.
Or use an API key
Create a key in Settings, under Advanced (see API keys). Choose Authentication: Bearer Auth, create a new credential, and paste the key as the token.
Your first workflow
Import the ready-made template. In n8n, open Workflows, then Import from URL, and paste this address:
https://getinboxtriage.com/docs/templates/n8n-inbox-triage.json
Or download the file and use Import from File.
It runs every morning at 7:00; change the time in the Schedule Trigger node. It has a Schedule Trigger, an MCP Client node calling
show_inbox with filter: needs, and a placeholder Set node for the result. Open the MCP
Client node and add your own Bearer Auth credential; if the Tool field shows an error, reselect
show_inbox from the Tool list, since n8n needs a live connection to fetch it. Replace the Set node
with a Slack node, or anything else, to post the result's sayToHuman line somewhere you will see
it.
We shipped this as a plain MCP Client node rather than an AI Agent with an MCP Client Tool, since a fixed daily check does not need a language model deciding which tool to call, and it needs no extra AI provider credential.
What it will not do on its own
n8n has no way to show Inbox Triage's in-chat approval prompt, so a connection through n8n is always treated as
unattended, whether it signs in with OAuth2 or Bearer Auth. Calling send_draft,
confirm_mark_spam, or confirm_unsubscribe from n8n never sends, reports spam, or
unsubscribes on its own. The tool's result carries an approvalUrl link instead: only the signed-in
person's click on that page, on getinboxtriage.com, completes the action. Map approvalUrl into your
Slack or email node so the person gets the link. Inbox Triage also sends it as a push notification or email. When
they open it they may be asked to sign in again or use a passkey before choosing Send.
Known issues
- If calls time out, update n8n. Tell us at help@getinboxtriage.com with your n8n version if it keeps happening.
- If OAuth2 sign-in fails, check that the redirect address on your credential screen matches what n8n shows you, or use Bearer Auth with an API key.
- If choosing Allow shows Confirm your email address first, open the link we emailed you, or send a new one from Settings, then sign in again.
Can I connect two Gmail accounts through n8n?
Yes. Connect both inboxes in Inbox Triage first. One n8n MCP Client or MCP Client Tool node can reach both, since the inbox is picked inside each tool call, not by the connection itself.
Does n8n need my Gmail password?
No. n8n only ever gets a bearer key or an OAuth2 token for Inbox Triage. Your mail passwords and provider sign-in tokens stay with Inbox Triage.
Which tools should I exclude from an AI Agent?
Exclude send_draft, confirm_mark_spam, confirm_unsubscribe, set_send_enabled, and start_imap_secret_capture from the MCP Client Tool sub-node so an approval link, not the agent, decides when those happen.
HTTP Streamable keeps timing out for me. What do I do?
Update n8n first. If it still happens, email us with your n8n version.
Do I need the AI Agent node at all?
No. The plain MCP Client node calls one named tool with fixed arguments and needs no language model, which is enough for a scheduled check like the template.
Try it with your own inboxes. Free for 7 days with up to 3 inboxes. No card needed.
Start free trialStill stuck? Email help@getinboxtriage.com.