Gmail sorting, Sheets extraction and auto-replies with n8n, Zapier or Make

Most of these requests come down to three jobs: label and route incoming Gmail, pull structured data out of emails or attachments into Google Sheets, and send a reply when a rule matches. All three can be built in n8n, Zapier or Make, or as a small script. The real work is deciding the rules and handling messy input.

What it looks like in practice

• Gmail sorting. A new message arrives. The flow checks the sender, subject and body against your rules, applies a label, and optionally forwards it or notifies a person. Invoices go to one label, enquiries to another, newsletters get archived.
• Sheets extraction. An enquiry email contains a name, phone number, product and quantity written in free text. The flow pulls those into columns, adds the email link, and flags rows where a field could not be read.
• Auto-replies. A short acknowledgement goes out when a new lead arrives, with your hours and what happens next. Replies are sent once per thread so nobody is emailed twice.

Where these break

• Emails are not consistent. Fields are missing, phrased differently or sit inside PDFs. I extract with rules first and use an AI step only where rules cannot cope, and I mark low-confidence rows for a human to check.
• Auto-replies loop if two systems answer each other, so I add a check for automated senders and a once-per-thread guard.
• Logins expire and quotas run out. Each flow gets an error alert so you hear about it.
• Gmail and Sheets have usage limits. Confirm current limits in Google’s documentation if your volume is high.

n8n self-hosted, hosted tools, or custom code

• Zapier or Make suit short flows with a low volume, when you want to click through changes yourself. Cost scales with the number of tasks or operations, so a busy inbox can get pricey.
• n8n self-hosted suits many steps, higher volume or data you want on your own server. The trade-off is that someone has to run, update and back it up. Check the n8n licence terms for your use case before committing.
• Custom code suits cases with branching logic, heavy parsing, or a need for tests and version control. It costs more to build but removes per-task fees and tool limits.

For a cost comparison in more depth, see the related post.

What I need from you

• Examples of 20 to 30 real emails, including the awkward ones.
• Your rules in plain words: what goes where, and what must never be auto-sent.
• Google account access via sign-in, and the Sheet it should write to.
• Who gets the failure alerts.

I hand over a short document with the flow, where credentials live and how to pause it.