Gmail automation for landscaping businesses (without an engineer)

Gmail is a surprisingly good inbox for a small landscaping business. It’s free, it works on your phone, and it has the two features that actually matter for automation: labels and a rich API.

Here’s the whole architecture you need. No code.

The four building blocks

1. A dedicated label — leads/new. Everything a lead-triage workflow touches gets this label. Nothing else does.
2. A filter — to:jobs@yourcompany.com OR from:(contactform@) OR subject:(quote OR estimate OR cleanup). Auto-applies leads/new to new inbound mail that looks like a lead.
3. An n8n workflow — polls Gmail for messages with leads/new every 2 minutes, classifies them, writes to a CRM, drafts a reply.
4. A Drafts folder — where the drafted replies land so you can scan them before sending.

That’s it. No new inbox. No CRM you have to log into. The work lives where you already live: in Gmail.

Why labels beat folders

Gmail labels are tags, not containers — one email can have multiple labels. This matters because you want to be able to filter on “leads that need a follow-up” without moving the email out of the main inbox view. The setup we recommend:

• leads/new — newly arrived, not yet classified.
• leads/hot — classified hot. You probably want to see these first.
• leads/warm — classified warm, follow-up due in 24h.
• leads/drafted — the workflow wrote a draft. Your cue to review and send.
• leads/sent — you replied.

The workflow moves the labels. You glance at the sidebar in the morning and you already know where to look.

The OAuth piece nobody explains

When you connect Gmail to n8n, you’ll be asked to set up an OAuth2 credential. The first time you do this it feels like a maze. The short version:

1. Go to console.cloud.google.com, make a project.
2. Enable the Gmail API.
3. Create OAuth credentials, type “Web application.”
4. Authorized redirect URI: whatever n8n tells you. Copy-paste exactly.
5. Scopes: gmail.modify (for labels and drafts). That’s it. You do NOT need gmail.send if you’re drafting only.

Take the extra five minutes to set scopes correctly. An n8n workflow with gmail.modify can’t accidentally send email. That’s a meaningful safety rail.

The common mistakes

Polling too often. Every 30 seconds chews through Gmail API quota and adds nothing — you’re not responding in 30 seconds anyway. 2 minutes is fine.

No label segregation. If the workflow runs on your entire inbox, one weird newsletter will get classified as a lead and you’ll start drafting replies to MailChimp. Label first, classify second.

Auto-sending before you trust it. The whole point of drafting to Drafts is you read the first 50, correct the prompt when it’s wrong, and only then start trusting auto-send. People who skip this step blow up a customer relationship in week one.

The short version

If you don’t want to build this from scratch: Inbox Autopilot for Landscapers ships a Gmail + Google Sheets workflow (and a Gmail + Airtable workflow) with the classifier, the drafter, the labels, and the install doc. Under 30 minutes from download to first draft.