<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Randy Corbett</title>
    <description>The latest articles on DEV Community by Randy Corbett (@corbettrevops).</description>
    <link>https://dev.to/corbettrevops</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3926408%2F1db3895e-31a3-4176-935f-281912458842.png</url>
      <title>DEV Community: Randy Corbett</title>
      <link>https://dev.to/corbettrevops</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/corbettrevops"/>
    <language>en</language>
    <item>
      <title>I Built a 7 n8n Workflow Bundle That Automates My Entire Gumroad Business — Here's What's Inside</title>
      <dc:creator>Randy Corbett</dc:creator>
      <pubDate>Tue, 12 May 2026 22:06:12 +0000</pubDate>
      <link>https://dev.to/corbettrevops/i-built-a-7-n8n-workflow-bundle-that-automates-my-entire-gumroad-business-heres-whats-inside-2d05</link>
      <guid>https://dev.to/corbettrevops/i-built-a-7-n8n-workflow-bundle-that-automates-my-entire-gumroad-business-heres-whats-inside-2d05</guid>
      <description>&lt;h1&gt;
  
  
  I Built a $47 n8n Workflow Bundle That Automates My Entire Gumroad Business — Here's What's Inside
&lt;/h1&gt;

&lt;p&gt;Every Gumroad seller knows the cycle.&lt;/p&gt;

&lt;p&gt;Sale comes in. You scramble to send a thank-you email. Three days later, you remember you meant to follow up and ask for a review — but you forgot, or it felt awkward, or you were heads-down building the next thing. Meanwhile, you wrote a new article and then manually copied pieces of it to Twitter and updated your product listing by hand.&lt;/p&gt;

&lt;p&gt;Multiply that by every sale, every week. It adds up fast.&lt;/p&gt;

&lt;p&gt;I got tired of it. So I spent three weeks building 10 n8n workflows that handle all of it automatically. The result is a $47 bundle I now run my entire Gumroad seller operation on. Here's exactly what's inside.&lt;/p&gt;




&lt;h2&gt;
  
  
  What the Bundle Does
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Workflow 1: Instant Sale Notification + Buyer Tagging
&lt;/h3&gt;

&lt;p&gt;Every Gumroad purchase fires a webhook that triggers this workflow. It does two things: sends me a clean Slack notification with the buyer's name, email, and product — and tags them in Kit so the right follow-up sequence kicks off automatically. No more checking Gumroad every hour. No more manual segment juggling.&lt;/p&gt;

&lt;h3&gt;
  
  
  Workflow 2: Welcome Email Trigger
&lt;/h3&gt;

&lt;p&gt;New subscribers hit your Kit form and this workflow starts their onboarding sequence without you lifting a finger. It checks what they opted in for, routes them to the right sequence, and logs them to a tracking sheet. Clean segmentation from day one.&lt;/p&gt;

&lt;h3&gt;
  
  
  Workflow 3: Purchase Confirmation + Delivery
&lt;/h3&gt;

&lt;p&gt;Replaces the generic Gumroad receipt with a personalized email that actually sounds like a human wrote it. Includes the download link, a quick-start tip, and a direct reply-to so buyers can ask questions. Deliverability and experience both go up.&lt;/p&gt;

&lt;h3&gt;
  
  
  Workflow 4: Failed Payment Recovery
&lt;/h3&gt;

&lt;p&gt;When a payment fails (it happens more than you'd think), this workflow waits 24 hours and sends a personal-sounding recovery email. Simple, timely, recovers sales you'd otherwise lose silently.&lt;/p&gt;

&lt;h3&gt;
  
  
  Workflow 5: Auto Review Request
&lt;/h3&gt;

&lt;p&gt;Three days after purchase, buyers get an email asking for feedback. The timing is deliberate — they've had time to actually use the product. I'm seeing 40%+ open rates on this sequence because it goes out at the right moment, not immediately after checkout when they haven't even opened the file yet.&lt;/p&gt;

&lt;h3&gt;
  
  
  Workflow 6: Buyer Upsell Sequence
&lt;/h3&gt;

&lt;p&gt;Bought the $9 intro guide? Seven days later this workflow checks their purchase history and sends a targeted pitch for the $47 bundle — only if they haven't already bought it. No awkward blasts to existing customers. Surgical upsell logic.&lt;/p&gt;

&lt;h3&gt;
  
  
  Workflow 7: Refund Handler
&lt;/h3&gt;

&lt;p&gt;Processes refund events from Gumroad, removes buyer tags in Kit, updates your records, and optionally sends a brief follow-up asking what went wrong. Turns refunds into feedback instead of just losses.&lt;/p&gt;

&lt;h3&gt;
  
  
  Workflow 8: Content Repurposing Engine
&lt;/h3&gt;

&lt;p&gt;This one's my favorite. Publish a new Dev.to article and this workflow auto-drafts a Twitter thread from the key points, plus generates a short update for your Gumroad product listing. One piece of content becomes three distribution touchpoints. It's not perfect every time — I review before posting — but it saves 80% of the manual work.&lt;/p&gt;

&lt;h3&gt;
  
  
  Workflow 9: Weekly Revenue Summary
&lt;/h3&gt;

&lt;p&gt;Every Sunday morning I get a clean Slack digest: total sales, top products, new subscribers, open rate on last week's broadcast. Everything in one place without touching a dashboard.&lt;/p&gt;

&lt;h3&gt;
  
  
  Workflow 10: Product Launch Sequence Trigger
&lt;/h3&gt;

&lt;p&gt;When you want to run a launch — new product, limited-time discount, anything — this workflow fires a three-email sequence over three days. Customizable per product. Handles the timing and segmentation so you're not manually scheduling sends.&lt;/p&gt;




&lt;h2&gt;
  
  
  Who This Is For
&lt;/h2&gt;

&lt;p&gt;If you're selling digital products on Gumroad and doing any of the following manually, this bundle removes all of it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Tagging buyers in your email platform&lt;/li&gt;
&lt;li&gt;Writing follow-up emails days after purchase&lt;/li&gt;
&lt;li&gt;Sending review requests (or forgetting to)&lt;/li&gt;
&lt;li&gt;Repurposing content across channels by hand&lt;/li&gt;
&lt;li&gt;Building and scheduling launch sequences&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You need basic n8n comfort — know how to import a workflow, set credentials, and activate nodes. These are documented and import-ready. Not plug-and-play with zero effort, but close.&lt;/p&gt;




&lt;h2&gt;
  
  
  What You Get
&lt;/h2&gt;

&lt;p&gt;10 n8n workflows in &lt;code&gt;.json&lt;/code&gt; format, ready to import. Each one includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Inline documentation explaining what each node does&lt;/li&gt;
&lt;li&gt;Required credentials list (Gumroad API key, Kit API key, Slack webhook — all free)&lt;/li&gt;
&lt;li&gt;Notes on what to customize for your setup&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Get It
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Full bundle ($47):&lt;/strong&gt; &lt;a href="https://corbettrevops.gumroad.com/l/ndiadx" rel="noopener noreferrer"&gt;corbettrevops.gumroad.com/l/ndiadx&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Want to test the water first? The &lt;strong&gt;intro guide ($9)&lt;/strong&gt; walks through the core architecture and includes Workflows 1, 3, and 5 as a starting set: &lt;a href="https://corbettrevops.gumroad.com/l/ayivw" rel="noopener noreferrer"&gt;corbettrevops.gumroad.com/l/ayivw&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you build on top of these or have questions about adapting them to your setup, reply to the purchase confirmation email. I read them.&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>automation</category>
      <category>gumroad</category>
      <category>nocode</category>
    </item>
    <item>
      <title>How I Automated My Entire Gumroad Business with n8n (And What I Learned)</title>
      <dc:creator>Randy Corbett</dc:creator>
      <pubDate>Tue, 12 May 2026 19:42:47 +0000</pubDate>
      <link>https://dev.to/corbettrevops/how-i-automated-my-entire-gumroad-business-with-n8n-and-what-i-learned-33am</link>
      <guid>https://dev.to/corbettrevops/how-i-automated-my-entire-gumroad-business-with-n8n-and-what-i-learned-33am</guid>
      <description>&lt;h1&gt;
  
  
  How I Automated My Entire Gumroad Business with n8n (And What I Learned)
&lt;/h1&gt;

&lt;p&gt;Last year I was spending about 90 minutes every day on things that weren't actually building my business.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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 &lt;em&gt;operations&lt;/em&gt; 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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;Here's what I built and how it works.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Setup
&lt;/h2&gt;

&lt;p&gt;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 &lt;code&gt;sale&lt;/code&gt;, &lt;code&gt;refund&lt;/code&gt;, &lt;code&gt;dispute&lt;/code&gt;, and &lt;code&gt;cancellation&lt;/code&gt;. From there, each workflow handles its own slice of the business.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;




&lt;h2&gt;
  
  
  Workflow 1: The Welcome Email Sequence
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;The first workflow I built listens for the &lt;code&gt;sale&lt;/code&gt; 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.&lt;/p&gt;

&lt;p&gt;The email does three things:&lt;/p&gt;

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

&lt;p&gt;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.&lt;/p&gt;

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




&lt;h2&gt;
  
  
  Workflow 2: The Review Request
&lt;/h2&gt;

&lt;p&gt;Ask for reviews and you'll get reviews. Not ask and you won't. This is the entire theory behind the second workflow.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

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

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;Result: my review count went from 6 to 31 in about two months without me touching anything.&lt;/p&gt;




&lt;h2&gt;
  
  
  Workflow 3: Sales Milestone Notifications
&lt;/h2&gt;

&lt;p&gt;This one is less about operations and more about staying motivated and keeping your audience in the loop.&lt;/p&gt;

&lt;p&gt;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:&lt;/p&gt;

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

&lt;p&gt;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.&lt;/p&gt;




&lt;h2&gt;
  
  
  Workflow 4: The Post-Purchase Support Triage
&lt;/h2&gt;

&lt;p&gt;Most support emails from digital product buyers fall into one of four categories:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;"I can't find my download"&lt;/li&gt;
&lt;li&gt;"How do I install/use this?"&lt;/li&gt;
&lt;li&gt;"Can I get a refund?"&lt;/li&gt;
&lt;li&gt;Everything else&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;




&lt;h2&gt;
  
  
  What the Other 6 Workflows Cover
&lt;/h2&gt;

&lt;p&gt;Beyond these four, I also built workflows for:&lt;/p&gt;

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

&lt;p&gt;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.&lt;/p&gt;




&lt;h2&gt;
  
  
  A Few Things I'd Do Differently
&lt;/h2&gt;

&lt;p&gt;If I were building these again from scratch:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Start with the welcome email, not the milestone tracker.&lt;/strong&gt; The welcome email has the highest ROI of anything here. Do that one first, prove the value, then build the rest.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Don't over-automate social.&lt;/strong&gt; 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.&lt;/p&gt;

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




&lt;h2&gt;
  
  
  Getting the Workflows
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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: &lt;a href="https://corbettrevops.gumroad.com/l/ndiadx" rel="noopener noreferrer"&gt;&lt;strong&gt;10 n8n Workflows for Gumroad Sellers&lt;/strong&gt;&lt;/a&gt; ($27).&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;




&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;— Randy, &lt;a href="https://corbettrevops.gumroad.com" rel="noopener noreferrer"&gt;Corbett Revenue Ops&lt;/a&gt;&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>automation</category>
      <category>gumroad</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
