How to Automate Email Triage With Make

Make turns Gmail into a triage machine. Build a scenario that watches your inbox, classifies each email, labels it, and logs it — with costs controlled.

By Galactic News Editorial · Published 2026-11-08T22:24:20+00:00 · Updated 2026-11-08T22:24:20+00:00

How to Automate Email Triage With Make

Make is a visual automation platform. You build scenarios, which are workflows made of connected modules. One module watches Gmail. The next one classifies the email. The next one labels it. The whole chain runs on its own, on a schedule you choose.

This guide shows how to automate email triage with Make step by step. You will build a Gmail triage scenario, add classification, route mail by priority, and keep the cost under control. No code is needed. Plan for about an hour of setup and testing.

How Make Works for Email Triage

A Make scenario has a trigger and a chain of modules. The trigger starts the run. For email triage, the trigger is usually the Gmail "Watch emails" module. It checks the inbox on a schedule. When it finds new mail, the scenario runs.

Each module that runs counts as one operation, now called a credit. Make bills by credits. A five-module scenario that runs 200 times uses about 1,000 credits. Filters and routers cost nothing. That detail matters when you design the flow. Put filters early so later modules only run on mail that qualifies.

Make also has AI modules. You can send an email to OpenAI, Claude, or Gemini for classification. The AI returns a label such as urgent, billing, or newsletter. Make then routes the email based on that label. The AI call itself costs credits based on tokens, so keep the prompt short and the email text trimmed.

How to Automate Email Triage With Make: The Build

Build the scenario in this order. Test after each module before you add the next one.

1. Create a Make account and open Scenarios. The free plan gives 1,000 credits a month and 2 active scenarios. That is enough to build and test your first triage flow.
2. Add the Gmail trigger module. Choose the Gmail app, then "Watch emails". Connect your Google account. Set the folder to Inbox and pick a polling interval. On the free plan, the shortest interval is 15 minutes.
3. Add a filter right after the trigger. Filter out mail you never need to triage. Exclude newsletters and receipts by sender or subject. Filters cost no credits. They save credits downstream.
4. Add a router for priority. A router splits the flow into branches. One branch handles urgent mail. One handles normal mail. One handles low priority mail. Routers cost no credits either.
5. Add an AI classification module. Send the subject and a trimmed body to your chosen AI model. Ask for one word back: urgent, reply, newsletter, or archive. Keep the prompt fixed. A fixed prompt gives steady results.
6. Add the Gmail label module. Use the "Add a label" action. Map the AI result to the label. Create the labels in Gmail first so the names match exactly.
7. Add a logging module. Write each triaged email to a Google Sheet. Log the date, sender, subject, and label. This sheet is your audit trail. Check it daily for the first week.
8. Add a notification for urgent mail only. Send urgent items to Slack or email. Do not notify on every email. Notifications on everything train you to ignore them.
9. Run the scenario by hand. Use the "Run once" button. Send yourself test emails in each category. Check the labels, the sheet, and the Slack message.
10. Schedule it and watch the first day. Turn the scenario on. Check the execution log for errors. Fix the most common error first, then the next.

Designing Triage Categories That Hold Up

Four categories cover most inboxes. Urgent means a customer or boss needs action today. Reply means a real person asked a direct question. Newsletter means bulk mail you read later. Archive means receipts and confirmations you keep but never read.

Write one rule per category in the AI prompt. Keep each rule to one sentence. Test the prompt on twenty real emails before you trust it. If the AI mislabels more than two of them, rewrite the rules. Short, concrete rules beat long, clever ones.

Trim the email body before you send it to the AI. The first few hundred characters usually hold the point. Trimming cuts token cost. It also keeps the AI focused on the ask, not the footer or the signature block.

What Make Email Triage Costs

Make has a free plan at $0 a month. It gives 1,000 credits a month, 2 active scenarios, and a 15-minute minimum interval. Paid plans start at $9 a month for Core on annual billing, with 10,000 credits. Pro costs $16 a month on annual billing. Teams costs $29 a month on annual billing. Monthly billing costs more. Prices vary by country, so check the pricing page for your region.

Count credits before you build. A triage scenario with a trigger, a filter, an AI step, a label step, and a sheet step uses about 4 credits per email. At 200 emails a month, that is about 800 credits. That fits the free plan. At 1,000 emails a month, it needs about 4,000 credits. That needs a paid plan. Do your own count with your real volume.

Watch out for polling costs. A trigger that checks Gmail every minute burns credits on empty checks. On the free plan, the 15-minute interval limits this. On paid plans, prefer a longer interval or a webhook trigger where the app supports it. A webhook fires only when mail arrives.

Make vs Zapier vs n8n for Triage

Make, Zapier, and n8n all do email triage. They bill differently. Make bills per module run. Zapier bills per task. n8n bills per full workflow run. A long workflow costs the same as a short one on n8n. It costs more on Make and Zapier.

Make is the middle ground. It is more visual than n8n and cheaper at volume than Zapier for multi-step flows. If your triage flow has five or more steps, Make usually costs less than Zapier. If it has fifteen steps, n8n may cost less still.

Common Mistakes to Avoid

The first mistake is a trigger that is too broad. Watching the whole inbox means the AI reads every newsletter. Narrow the trigger with a Gmail search query. Exclude lists and receipts first.

The second mistake is auto-replying on day one. Let the scenario label and draft only. Send nothing automatically until a week of correct labels proves the rules work. A wrong auto-reply is worse than a slow reply.

The third mistake is no error handling. Add an error handler to the AI module. When the AI call fails, route the email to a manual review label. That way no email vanishes silently when a service is down.

The fourth mistake is forgetting the credit cap. When credits run out, scenarios stop. Make notifies you at 75 percent and 90 percent usage. Watch those alerts. A stopped triage flow means mail piles up unseen.

The Bottom Line

Make is a solid choice for email triage when you want visual branching and honest pricing. Build one scenario with a Gmail trigger, an early filter, an AI classifier, and a label step. Log every result to a sheet. Test with real mail before you schedule it. Count your credits against your real email volume, and pick the plan that fits the count. A simple triage scenario you trust beats a complex one you have to babysit.