How I Automated My Entire Gumroad Business with n8n (And What I Learned)

#n8n #automation #gumroad #productivity

How I Automated My Entire Gumroad Business with n8n (And What I Learned)

Last year I was spending about 90 minutes every day on things that weren't actually building my business.

Welcome emails. Review request follow-ups. Copying sale notifications into a spreadsheet. Writing a social post every time I hit a milestone. Answering the same three support questions over and over. Manually checking if a refund had come in so I could update my numbers.

I sell digital products on Gumroad — n8n workflow templates, mostly, which is a little on the nose in retrospect — and the product side was humming. The operations side was eating me alive. I'm a builder. I want to be writing workflows and making useful things, not copy-pasting order confirmation emails.

So I did what any automation-obsessed person would do: I sat down one weekend and mapped out every repetitive thing I was doing after a sale, after a refund, after a review came in. Then I automated all of it in n8n.

Here's what I built and how it works.

The Setup

Everything runs on a self-hosted n8n instance (you can use n8n Cloud too — all of these work there). The core integration is Gumroad's webhook system, which fires events for sale, refund, dispute, and cancellation. From there, each workflow handles its own slice of the business.

I'm not going to pretend this is plug-and-play. You'll need to set up credentials, configure a few node fields for your products, and understand what you're looking at. But if you've ever built a workflow in n8n, none of this will feel foreign.

Workflow 1: The Welcome Email Sequence

Gumroad sends a receipt. That's it. Buyers get a PDF download link and a transaction ID, and that's the entire relationship until they either love you or forget you exist.

The first workflow I built listens for the sale webhook, extracts the buyer's email and product name, waits 10 minutes (so the Gumroad receipt lands first), and then sends a plain-text welcome email from my own domain.

The email does three things:

Confirms what they bought and where to find it
Sets expectations ("here's the best way to use this")
Opens a real conversation ("reply to this email if you get stuck")

That last part alone cut my negative reviews roughly in half. People were leaving 3-star reviews because they didn't know how to import a workflow. Now they email me first, I help them, and they leave 5-star reviews.

The n8n setup: Webhook Trigger → Wait (10 min) → Gmail (or any SMTP node) → Google Sheets (log the send). The conditional logic checks product ID so different products get different emails.

Workflow 2: The Review Request

Ask for reviews and you'll get reviews. Not ask and you won't. This is the entire theory behind the second workflow.

Seven days after a sale, n8n sends a short, honest email asking if the buyer found the product useful and, if so, whether they'd be willing to leave a Gumroad review. The email includes a direct link to the review page.

The implementation uses n8n's Schedule trigger combined with a Google Sheets lookup — when a sale comes in, it's logged with a review_request_sent: false flag and a sale_date. Every morning the schedule trigger runs, finds rows where review_request_sent is false and sale_date is 7+ days ago, and fires off the email sequence.

This is slightly more complex than the welcome email because you need to handle edge cases: refunded orders shouldn't get review requests, and you don't want to email someone twice. The workflow checks both before sending.

Result: my review count went from 6 to 31 in about two months without me touching anything.

Workflow 3: Sales Milestone Notifications

This one is less about operations and more about staying motivated and keeping your audience in the loop.

The workflow tracks cumulative sales in a Google Sheet. Every time a sale webhook fires, it increments a counter. When the counter hits a milestone (10 sales, 25 sales, 50 sales, 100 sales — you configure these), it fires off a few things simultaneously:

A Slack message to a private channel I use as a business log
A drafted tweet via the Twitter API that I can review and post
An email to my list (via Mailchimp or ConvertKit, your choice) with a short update

The tweet drafting is the clever part. The workflow uses an OpenAI node to generate a short milestone post based on a template I wrote. Something like: "Just hit [X] sales on [product]. Here's the one thing I keep hearing from buyers: [testimonial snippet]." I review it before posting — I'm not fully automated on social — but having a draft appear in my drafts folder is 80% of the battle.

Workflow 4: The Post-Purchase Support Triage

Most support emails from digital product buyers fall into one of four categories:

"I can't find my download"
"How do I install/use this?"
"Can I get a refund?"
Everything else

The fourth workflow integrates with Gmail, watches for emails containing keywords from known buyers (cross-referenced against the Google Sheets sales log), and routes them based on content.

Category 1 emails get an automated reply with the Gumroad download link retrieval instructions. Category 2 emails get tagged with a label and a draft reply with my standard onboarding guide. Category 3 gets flagged for my manual review. Everything else hits my inbox normally.

The NLP here is basic — keyword matching, not AI classification — but it handles about 70% of incoming support without me doing anything. The OpenAI integration can make this smarter if you want, but I've found the simple version works well enough and is easier to debug.

What the Other 6 Workflows Cover

Beyond these four, I also built workflows for:

Refund tracking — logs refunds, removes buyers from email sequences, updates revenue dashboards
Abandoned cart follow-up — uses Gumroad's offer ping events to catch people who started checkout
Weekly revenue digest — a Sunday morning summary email to myself with key metrics
New review alert — pings me in Slack when a new Gumroad review comes in so I can respond quickly
Content repurposing — turns a new product description into a set of social posts and an email draft
Affiliate payout tracker — monitors affiliate performance and flags top performers for outreach

All ten are structured the same way: clear triggers, readable node names, and comments explaining why each step exists. I hate opening a workflow someone else built and having no idea what's happening.

A Few Things I'd Do Differently

If I were building these again from scratch:

Start with the welcome email, not the milestone tracker. The welcome email has the highest ROI of anything here. Do that one first, prove the value, then build the rest.

Don't over-automate social. I tried fully automating tweets for a while. The engagement was terrible and it felt hollow. The draft-and-review approach is the right balance.

Keep a "workflow broken" alert. Each workflow has an error handler that pings me in Slack if something fails. This saved me twice when Gumroad webhook signatures changed.

Getting the Workflows

I packaged all ten of these as ready-to-import n8n JSON files — the actual workflow exports, not pseudocode or screenshots. Each one comes with a setup guide covering the credentials you'll need and the fields to customize.

If you want to skip the weekend of building and just import working workflows into your n8n instance, I put them together in a bundle: 10 n8n Workflows for Gumroad Sellers ($27).

But honestly, everything above is enough to get started on your own if you'd rather build it yourself. That's the point of writing this out.

If you build something from this or have questions about specific nodes or logic, drop it in the comments. I check in most days and this is the kind of conversation I actually enjoy.

— Randy, Corbett Revenue Ops