← Back to library

Catch the emails your AI inbox assistant never processed

Huzaifa, who shares n8n workflows on the Build Then Break channel, let a Gemini email assistant handle a company mailbox for ten days. All runs showed success, yet 15 of the 64 incoming messages were never processed. The gaps came from trigger and sign-in settings; the fix adds a separate daily sweep for unlabeled mail. We generalize the fix.

  • OutcomeRun your AI email triage workflow as usual, label every message it handles, and add a second, independent workflow that once a day searches the inbox for recent mail without that label and sends you the list, alongside retries on the model steps and a production-status sign-in so the trigger does not silently expire.
  • SetupUnder an hour
  • LevelIntermediate
  • CreditHuzaifa_Aamish
View original
Works with
n8nGeminiCustom agent

Published Nov 7, 2026Updated Nov 7, 2026AI dry run on sample input: passed Nov 7, 2026Source verified Nov 8, 2026

When should you use it?

  • An automation sorts or drafts replies for a shared or business inbox
  • Your workflow history shows only successful runs and you have never checked for mail it skipped
  • The inbox is also read on phones or by other people

Not for: Personal inboxes where a missed newsletter costs nothing; Systems that already reconcile every received message against a processed list; Workflows that send replies automatically without a person reviewing drafts; fix that first

What do you need, and what do you get?

You need

  • The existing email triage workflow and the label it applies
  • Permission to search the mailbox on a schedule
  • A place to receive the daily list, such as email or chat

You get

  • A daily message listing recent emails the assistant did not touch
  • Retry settings on every model step
  • A sign-in that does not expire after a test period

How does it work, step by step?

  1. Label what you processMake the main workflow add one consistent label to each email once it has been sorted or drafted.
  2. Add retriesSet the model steps to retry a few times with a short pause, so one temporary outage does not drop a message.
  3. Fix the sign-inMove the Google OAuth app out of testing mode so access tokens stop lapsing after a week.
  4. Build the sweepCreate a separate scheduled workflow that searches for mail from the last day without the label and sends you the results.
  5. Read it for a weekCheck every item on the daily list and trace why it was missed before you trust the setup.

The prompt

Our own prompt, inspired by Huzaifa_Aamish and written to work in n8n, Gemini and Custom agent. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt4 variables
Review this email automation for silent gaps: {workflow_description}.
List every way a message could arrive and never be processed, covering the trigger filters, polling limits, downtime, model errors without retries and expiring sign-ins.
For each gap, give the setting to change.
Then write the search query for a separate daily check that finds messages from the last {hours} hours in {mailbox} that lack the label {processed_label}, and describe what the daily report should contain.

Inspired by Huzaifa_Aamish: n8n Community: an AI assistant ran a business inbox for 10 days and missed 15 of 64 emails. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • A trigger that only reads unread mail misses anything you open on another device first.
  • Polling caps per run can leave a backlog during busy hours. Raise the limit or poll more often.
  • Keep the sweep in a separate workflow; then a failure in the main one cannot stop it.
  • Green execution logs show that runs finished, not that every email was handled.

Our take

The headline number is the lesson: every run reported success, and almost a quarter of the inbox was still ignored. That gap between a green log and a finished job is the most common way AI automations disappoint small businesses, and it rarely has anything to do with the model. Here the culprits were ordinary settings, from an unread-only trigger to an expiring sign-in, which is exactly why they went unnoticed. We like the shape of the fix more than any single setting. A separate, boring check that asks what was not handled will catch causes nobody has thought of yet, and keeping it independent means it survives when the main workflow breaks. The same idea applies to invoice capture, form intake and support queues: count what arrived, count what was processed, and look at the difference every day. In our dry run with a fictional dental office inbox, the sweep listed three unlabeled emails, including one opened on a phone before the trigger ran.

Where the time goes back: A two-minute daily list replaces the unpleasant discovery, weeks later, that a customer email was never answered, and it shows exactly which setting to fix.

FAQ

Why did the assistant miss so many emails?
The post names five causes: the trigger only saw unread mail, polling never looks back after downtime, a low cap on emails per poll, no retry after a model error, and a sign-in that expired after seven days in testing mode.
Does it send emails automatically?
No. The assistant in the post only creates drafts, and the sweep only reports. Nothing is sent without a person.
Can I use this outside n8n?
Yes. Any automation platform that can label mail and run a scheduled search can add the same independent check.

Source and credit

Inspired by Huzaifa_Aamish. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
n8n Community: an AI assistant ran a business inbox for 10 days and missed 15 of 64 emails
Creator
Huzaifa_Aamish
Published on
n8n Community
Original date
Nov 6, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
n8n
AI dry run
Nov 7, 2026: passed. Dry-run tested by our AI test agent on sample input. Found all three seeded misses, gave a fix per gap, sweep kept separate and report-only.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Nov 8, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Log every agent action as ok, failed or unknown

Give each write an agent makes one structured log line with its attempt ID, request key, an outcome of ok, failed or unknown, and what the agent did next, then keep one saved query for the combination that should never happen, an unknown outcome the agent confirmed to the customer, so a repeat of the incident shows up in minutes.

Credit: ccch713

Under an hour
Operations & AdminWorkflow✓ AI dry run

Pin your agent's write path with one contract test

Build a single fast test workflow that sends the same request key to your agent's booking or order write twice against a stand-in backend, then confirms from an append-only log that exactly one write happened, that the repeat ends as a deliberate skip, and that a forced timeout still lands as unknown and reaches a person, so refactors cannot quietly bring back duplicate writes.

Credit: ccch713

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Gate after-hours dental phone triage and booking

Calls are answered and booked against the real schedule, emergencies reach the dentist, and reminders and recalls run without front-desk time.

Credit: u/anassy1 on r/AiAutomations

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Set To, Cc and Bcc rules for your assistant's own mailbox

Give an AI assistant its own address and a written rule for each way it can appear on a message: when it is the direct recipient it prepares an unsent draft for you, when it is copied it may give a short reply as itself with no promises, and when it is blind copied it only records the message, with dates going to the calendar and dateless requests to the task list.

Credit: u/carlosrudriguez

Under an hour
Operations & AdminWorkflow✓ AI dry run

Confirm tables on WhatsApp against a live book

Guests book a table by chatting on WhatsApp, staff see bookings on a table plan, and reminders go out automatically.

Credit: u/begylewis on r/micro_saas

An afternoon+