The n8n Email Automation Stack for Serial Entrepreneurs

The client runs multiple businesses. When we started, his inbox was a bottleneck for every one of them. Nothing filtered what came in. Some emails caught his attention right away; others sat until they turned into problems. There was no triage layer and no routing, so his team couldn't handle much of anything without looping him in.

The explicit goal we set was to take 20 hours off his weekly workload, and email was the biggest single target. We mapped out roughly 50 automations to build. Not 50 complex workflows, mostly small, specific decisions. Does this email go to Asana? Does it route to a Slack channel? Does it trigger an NDA? Does it need a response template? Fifty of those small calls, repeated every day across several inboxes, add up to a lot of hours.

The architecture

The stack has two layers. n8n handles execution. Google Sheets holds the rules.

n8n is a self-hosted automation tool, comparable to Zapier or Make but a lot more flexible and much cheaper at the ceiling. Usage runs around $20 a month. The developer retainer to maintain it costs more than the tool itself, but that's true of any automation platform. The software is cheap. The configuration is what takes the time.

The Google Sheets layer is what makes this hold up in day-to-day use. Every routing rule, every threshold, every list of approved senders lives in a spreadsheet that any team member can open and edit. A non-technical admin can add a new routing rule by adding a row. They can disable an automation by changing a cell. They never need to touch n8n directly.

This separation matters more than it sounds. I've seen automation systems where the rules are hardcoded into the workflows themselves. That approach creates a system where every change, however small, requires someone who can open the workflow editor and knows what they're doing. In practice, that means changes don't happen. The rules calcify. The automation that was built for the business six months ago keeps running for the business as it was six months ago.

When the rules live in a spreadsheet, the system stays current because it's easy to update. That's the whole argument.

What got built first

We prioritized by hours saved per automation, not by complexity.

The first set covered billing email triage. The client was handling invoices and payment emails himself, and each one needed a decision: is this legitimate, does it need action, who should handle it. Now the automation routes these into an Asana task with the details pre-filled, and the client's team picks it up from there.

The second set covered deal flow. He's actively acquiring businesses, and inbound deal emails from brokers kept getting buried. The automation now creates a pipeline entry whenever an email matches the broker pattern, with a date stamp so the pipeline doesn't go stale. Stale deal pipelines look like abandoned ones to investors, so this single automation fixed a problem that was quietly shaping how the whole acquisition effort came across.

The third set covered routing. Emails meant for a particular department, vendor, or team member now get relayed automatically with the right people CC'd, and the client stops seeing the ones that aren't his.

NDA triggers came next. When a specific inquiry type comes in, the automation sends the standard NDA template without the client's involvement.

What "done" looks like

The target was 20 hours a week removed from the client's plate. Email triage alone accounts for an estimated 5 to 10 of those hours. That estimate is based on volume multiplied by handling time per email type, not a precise measurement, but it's directionally right.

Done doesn't mean fully automated. Some categories will always need human judgment. We were never trying to automate everything, just the categories where the decision is always the same, so a person's attention is free for the ones where it isn't.

The test for a working automation system is whether it can survive a team member leaving. With hardcoded rules, when the person who built the system leaves, the organization inherits a black box. Nobody wants to touch it. It slowly breaks as the business changes. With rules in a spreadsheet, the system is transparent enough that someone new can understand it in an afternoon and maintain it from day one.

That's what we built toward. The automations themselves are ordinary. What makes them last is keeping the rules somewhere anyone on the team can edit.