Gmail automation starts with filters, scheduled send and templates, and goes further with Google Apps Script, Zapier or a custom workflow; Outlook has the same ladder with rules, Quick Steps and Power Automate. Those tools sort mail well. They do not read a customer's request, decide what it needs and write the answer, which is where most inbox hours actually go.
This page covers what each layer does, where it stops, and how Benian builds AI triage for a shared inbox: classify each message, pull out the order number or job address, draft a reply and file the work in your CRM. A person approves every client reply before it goes. This is not about cold email.
If your inbox problem is a few newsletters a day, you do not need us. Set up filters and stop there. If three people spend their mornings reading the same requests and retyping them into other systems, keep reading.
What a shared inbox costs before automation
Reading is the slow part
A filter can label mail from a known sender. It cannot tell a quote request from a complaint when both come from new addresses, so someone opens every one.
The same data is typed twice
A customer emails an order number and a site address. Someone copies both into the CRM by hand, and one typo becomes a wrong delivery.
Nobody owns the thread
In a shared mailbox two people answer the same message, or each assumes the other did. You find out when the customer calls.
Follow ups depend on memory
A quote goes out and nobody checks back. Flags help one person but do not show a manager which promised replies are overdue.
Urgent mail waits behind routine mail
A cancellation sits under a pile of supplier invoices because the inbox is sorted by time, not by consequence.
Native rules and filters in Gmail and Outlook
Gmail filters match on sender, recipient, subject, words and attachments, then label, archive, star, forward or delete. Outlook rules work the same way, and Quick Steps bundle several clicks into one. Both come with the account and need no upkeep.
Use them first: route supplier invoices to a label, move system notifications out of the main view, forward a key account's mail to its owner. The limit is that they match words, not meaning. A filter on the word urgent catches marketing mail and misses the customer who writes that the unit stopped working this morning.
- Good for: known senders, fixed subject formats, notifications.
- Weak for: new senders, mixed requests, anything that needs judgment.
- Watch for: Outlook rules marked client only, which run only while the desktop app is open.
Scheduled emails and automated email reminders in Outlook and Gmail
Both tools can schedule a message to send later, and both let you flag or snooze a message so it comes back at a set time. For automated email reminders in Outlook, the simple version is a flag with a reminder date or a calendar entry. That works for one person and one thread.
Team reminders need a list. The workflow reads a sheet or CRM of open quotes or invoices on a schedule and sends a reminder when a date passes with no reply. The stop condition matters most: it must check for a reply or payment first, or it chases a customer who already answered. We build that check before the send.
Power Automate for Outlook and Apps Script for Gmail
Power Automate is Microsoft's workflow tool, and Outlook is its most common trigger. A flow can start when a new email arrives in a mailbox or folder, save attachments to SharePoint or OneDrive, add a row to Excel, post to Teams and send an email from a user or shared mailbox. Connector licensing varies by plan and some connectors are premium, so confirm what your subscription covers before you design around them.
Google Apps Script is JavaScript that runs inside Google Workspace. It can search Gmail, apply labels, create drafts and write to Sheets on a timer, which suits a Google Workspace workflow that stays inside Google. It has daily quotas and limited built-in alerting, so an old script nobody monitors can fail without anyone noticing.
Zapier for Gmail and Outlook connects the inbox to thousands of other apps with no code and charges by tasks run. It is the fastest way to start, and per task billing grows with volume. n8n does the same job, can be self hosted, and is what Benian builds on, inside an account you own.
AI triage: classify, extract, draft and route
This is the layer the other gmail automation tools do not cover. A language model reads each new message and answers fixed questions: what type of request is this, which customer or job does it refer to, how urgent is it, and what fields does it contain. The workflow then acts on those answers in your systems.
A typical service business build: a quote request becomes a CRM deal with the address filled in and a draft reply asking for the missing details. A reschedule request becomes a task for the scheduler. A supplier invoice is labeled and its total and due date go to a sheet, with no reply drafted. Anything the model cannot classify with confidence goes to a review folder.
- Classify into the five to ten categories your team already uses.
- Extract only fields a downstream system needs, and validate formats such as order numbers.
- Draft from your approved wording and your own data, never from the model's guesses about prices or dates.
- Route by category so each thread has one named owner.
Keeping a person in the loop before anything sends
Can AI draft replies in Gmail without sending them? Yes. Both the Gmail API and Microsoft Graph can create a draft in the thread, so the reply waits in the inbox for someone to read, edit and send. That is how we build client replies by default. We do not build automatic replies to clients.
Fully automatic sending is reasonable only for narrow internal messages, such as an acknowledgment that a support ticket number was created or a notification to your own team. For anything a customer reads, the person who sends it owns it. Measure how often drafts go out unchanged; if a category is edited heavily, the draft wording or the data behind it needs fixing.
Security, permissions and an audit trail for inbox automation
Inbox access is broad access. Give the workflow the narrowest permission that works: read and draft on one shared mailbox, not send rights on everyone's mail. Google Workspace and Microsoft 365 administrators can restrict which third party apps connect, and we work inside that policy.
Treat every incoming email as untrusted input. A message can contain text written to instruct an AI model, so the model's output only fills fields and drafts; it cannot trigger payments, deletions or forwards outside the rules you agreed. Every run logs what came in, how it was classified, what was written where and who approved the reply, so you can answer the question of why the system did something.
What to measure and when to start smaller
Before a build, count a normal week: messages by type, time to first reply and how many are retyped elsewhere. After it, track the same numbers plus the share sent to review and the share of drafts sent unchanged. If you cannot count volume, tally two weeks in a sheet first; the problem is often one category, not the whole inbox.
Start smaller when a single filter or one Power Automate flow solves the main pain, when volume is a few dozen messages a week, or when your team has not agreed who owns which request type. Automation copies a process. If the process is unclear, the automation makes the confusion faster.
Gmail and Outlook automation options compared
| Option | Best for | Understands message meaning | Cost model |
|---|---|---|---|
| Gmail filters, Outlook rules | Known senders and fixed formats | No, matches words and addresses | Included with the account |
| Google Apps Script | Logic inside Google Workspace | Only if you add an AI call | Included, within daily quotas |
| Power Automate | Microsoft 365 teams | Only with an AI step | Licensing, some connectors extra |
| Zapier | Fast no code connections | Only with an AI step | Per task run |
| Custom n8n workflow | Shared inboxes feeding several systems | Yes, with AI triage and review | Build quoted to scope, then your own usage |
How Benian builds an inbox workflow
- Sample the inbox. We read real messages with your team, on access you can revoke, and agree categories, fields and owners.
- Agree the rules. Scope names what runs on its own, what becomes a draft, what goes to review and who approves each category.
- Build in your accounts. The workflow runs in your own n8n account, connected with credentials your business holds.
- Test on past mail. We replay past messages through the classifier, compare its answers with what your team did, and fix the misses.
- Run in draft mode, then hand over. Early weeks produce only drafts and labels. You then receive the workflow files, an operating guide and a walkthrough.