Automating your email inbox means moving mail into the right place, extracting what you need from it, and triggering the follow-up work — without you reading every message to decide. Most of it is achievable with rules alone, for free, in about an hour.
What follows is the order to build it in: native rules first because they cost nothing, then a workflow platform for anything that has to leave your inbox and do something, then AI triage last and only where rules genuinely run out. Doing it in that order is what keeps the bill at $0–9 instead of $50.
Key takeaways
- Start with native filters in Gmail or Outlook. They’re free, instant, and handle roughly 70% of inbox chaos on their own.
- Use a workflow platform only when mail must trigger work elsewhere — create a task, add a CRM row, save an attachment.
- AI triage is for unpredictable wording, not for volume. If you can list the senders and keywords, a rule is cheaper and more reliable.
- Attachment handling is where naive setups break — file size limits and duplicate names cause most silent failures.
- Never auto-send replies to customers. Auto-draft and approve. The one time it’s wrong is expensive.
What Can You Actually Automate in an Inbox?
Four distinct jobs, and they need different tools. Confusing them is why people reach for a $20 plan to solve something a free filter handles.
| Job | Example | Right tool | Cost |
|---|---|---|---|
| Sorting and labelling | Receipts to a Receipts label, newsletters out of the inbox | Native Gmail/Outlook rules | Free |
| Triggering outside work | New enquiry → CRM row + Slack alert | Make, Zapier or n8n | $0–9/mo |
| Extracting data | Pull invoice number and total from a PDF | Workflow platform + parser | $9–20/mo |
| Judging intent | Is this angry? Is it a sales enquiry or support? | AI step inside a workflow | Variable usage |
How Do You Set Up Native Email Rules First?
Spend twenty minutes on filters before you open any automation platform. Native rules run instantly, never consume a task or credit, and never break because an API changed — and they solve the majority of inbox noise.
The four filters worth building on day one:
- Receipts and invoices out of the inbox. Match on sender domains plus subject keywords, apply a label, skip the inbox. You’ll find them when you need them; you don’t need to see them arrive.
- Newsletters to a reading label. Filter on the list-unsubscribe header if your client supports it, which catches almost everything without naming senders individually.
- Internal team mail to its own label. Match your own domain.
- Anything from a paying customer starred and inboxed. This is the important one — build a filter that protects attention, not just one that removes noise.
The ordering trap: in Gmail, filters all run and can conflict — a message can be archived by one rule and starred by another. Build the protective rules and test them after adding the noise-removal ones.
When Should You Use a Workflow Platform?
The moment an email needs to cause something outside your inbox. Filters can label and archive; they cannot create a CRM record, save an attachment to Drive, or post to Slack with the sender’s details parsed out.
Here’s the canonical build — a new enquiry arriving by email and becoming a tracked lead:
| Step | What it does | Why it’s here |
|---|---|---|
| 1. Trigger: new email matching label | Fires when your filter tags a message | Let the free filter do the matching, not the paid platform |
| 2. Parse sender name and address | Splits the from-field into usable fields | CRM needs structured data, not a blob |
| 3. Search CRM for existing contact | Checks before creating | Skip this and you’ll build duplicates |
| 4. Create or update contact | One record per person | Branch on step 3’s result |
| 5. Post alert with a reply link | Tells a human, immediately | Speed of reply is the thing that converts |
| 6. Error path → notify | Tells you when it breaks | Without this, failure is silent |
Note step 1. Triggering off a label your native filter applied — rather than off “any new email” plus platform-side filtering — means the platform only sees mail that already matters. On per-step billing that difference is most of your bill.
What Does This Cost to Run?
It depends entirely on which platform you pick, because they meter completely different things. The workflow above is one trigger plus five steps, so the spread is wide.
| Platform | Billing unit | Cost of 200 enquiries/mo | Plan needed |
|---|---|---|---|
| Make | One module run | ~1,200 credits | Core $9/mo (10,000 included) |
| n8n Cloud | One whole workflow run | 200 executions | Starter €20/mo (2,500 included) |
| Zapier | One action step | ~1,000 tasks | Professional, above the 750 tier |
Make Core at $9 is the obvious pick for this shape of work at this volume. Full arithmetic is in the Make credit breakdown, and the Zapier pricing explainer covers why a six-step workflow burns tasks fast.
Where Does AI Triage Actually Help?
Only where the wording is unpredictable. If you can list the senders, domains or keywords that identify a message type, a free rule beats an AI step on cost, speed and reliability. AI earns its place when the same intent arrives phrased forty different ways.
| Task | Rule or AI? | Why |
|---|---|---|
| Route mail from a known domain | Rule | Fully specifiable, free, instant |
| Label anything containing “invoice” | Rule | Keyword match is exact |
| Separate sales enquiries from support | AI | Same words, different intent |
| Detect an unhappy customer | AI | Tone isn’t a keyword |
| Summarise a long thread | AI | Genuinely a reading task |
| Draft a first-pass reply | AI, human sends | Never auto-send to a customer |
The last row is a hard rule. An AI-drafted reply that a person reviews is a genuine time saving. An AI-sent reply that misreads a complaint costs you the customer, and you find out from a review rather than from a log. More on that boundary in AI agents for business.
How Do You Automate a Shared Team Inbox?
Differently from a personal one, and the difference is ownership. A personal inbox needs sorting; a shared inbox needs someone to be accountable for each message, or everything gets read by three people and answered by none.
So the automation has one extra job: assignment. On arrival, route the message to a named person based on something deterministic — the form it came from, a keyword, or simple round-robin — and record who owns it. Then alert that person specifically rather than the whole channel.
| Shared-inbox rule | Why it matters |
|---|---|
| Assign an owner on arrival | Unowned mail is unanswered mail |
| Alert the owner, not the channel | Broadcast alerts get muted within a week |
| Escalate on no reply after N hours | Catches the messages an owner missed |
| One thread, one owner | Two people replying is worse than none |
The escalation rule is the one worth building even if you skip the rest. A message assigned and then forgotten looks identical to a message handled — until the customer follows up annoyed.
What Breaks, and How Do You Prevent It?
Four failure modes account for nearly every broken inbox automation, and all four are preventable at build time.
| Failure | Symptom | Fix at build time |
|---|---|---|
| Duplicate records | Same person three times in the CRM | Search-before-create step |
| Attachment limits | Large files silently dropped | Check size, route big files to a link instead |
| Filename collisions | Files overwriting each other in Drive | Prefix with date and sender |
| Expired authentication | Everything stops, no alert | Error path notifying a human |
Test all four deliberately before you trust the workflow. Send yourself an email from an address already in the CRM, one with a 30 MB attachment, and two with identically named files. Fix what breaks. This takes fifteen minutes and saves a month of confusion.
Frequently Asked Questions
How do I automate my email inbox for free?
Native filters in Gmail or Outlook, which cost nothing and handle sorting, labelling and archiving. Build four: receipts out of the inbox, newsletters to a reading label, internal mail labelled, and customer mail starred and protected. That’s about twenty minutes of work.
Do I need Zapier to automate email?
Only if an email needs to trigger something outside your inbox — a CRM record, a task, a saved attachment. For sorting and labelling alone, native rules are better: free, instant, and they never break because an API changed.
What does email automation cost?
$0 for native rules. For workflows that trigger outside work, roughly $9/month on Make Core, €20 on n8n Starter, or above $19.99 on Zapier Professional depending on step count. Around 200 enquiries a month fits comfortably in Make’s entry plan.
Should AI reply to my emails automatically?
No. Have it draft and a human send. An AI reply that misreads a complaint costs you the customer, and you find out from a review rather than a log. Drafting saves most of the time anyway.
Why does my email automation create duplicate contacts?
Because it has no search-before-create step. Add a step that looks up the sender’s email in your CRM first, then branch: update if found, create if not. This is the single most common inbox automation bug.
Can I automate email attachments?
Yes, but handle two things explicitly: file size limits, which cause silent drops on large attachments, and filename collisions, which cause files to overwrite each other. Prefix saved filenames with the date and sender.
The Bottom Line
Build it in cost order. Twenty minutes of native filters removes most of the noise for free. A six-step workflow on a $9 plan turns enquiries into tracked leads with an instant alert. An AI step, added last, handles the messages whose wording you could never have predicted.
The two steps people skip — search-before-create and an error notification — are the two that decide whether this is an asset in six months or a silent liability. Add both, deliberately break the workflow once to check the alert fires, then leave it alone.
If you’ve never built a workflow, the beginner’s guide covers the mechanics. To work out whether this is the right automation to build first, run the ROI formula.
Want one practical automation you can set up in 15 minutes, delivered twice a month? Join the free AI automation newsletter.
Sources
- Make — Pricing plans
- Make Help Centre — Operations and how they are counted
- Zapier — Pricing plans
- n8n — Pricing plans
- SBE Council — 2026 Small Business Tech Use Survey
All sources retrieved 26 July 2026. Cost figures are worked arithmetic from each platform’s documented billing unit.
