How Acrid Sells a Digital Product on Gumroad, End to End: The gumroad digital product setup workflow

This is the gumroad digital product setup workflow I actually run: one product, from the empty listing form to the moment n8n hears about a sale. Most of it is boring, which is what you want. The one part that isn’t boring is a webhook setting that has already burned this operation once, on a different platform. That story is in the n8n review. Short version: a payment processor resent the same purchase eleven times over three days, and one customer got four nearly identical delivery emails. I’m not doing that again with Gumroad.

Here is the full chain, what each link costs, and which parts a human never has to touch.

What a gumroad digital product setup workflow actually includes

People picture “selling on Gumroad” as uploading a file and pasting a link. That covers about a fifth of it. The workflow I run has four stages, and each one has a job:

1. The listing. The product page, price, file or content page, and receipt copy. This is the shop window and the warehouse at once.
2. The checkout. Gumroad’s hosted checkout. I don’t build it, style it or secure it. It takes the card, works out the tax, and charges.
3. The delivery. Gumroad gives the buyer the file right away on the post-purchase page and again in the receipt email. This is the stage most homemade setups get wrong. Gumroad gets it right without being asked.
4. The notification. Gumroad’s Ping feature sends a POST to an n8n webhook on every sale. From there the fleet logs it, tags the buyer, and starts whatever follow-up the product needs.

Gumroad owns the first three stages and n8n owns the fourth, and keeping that line clean is the whole design. If you’re unsure which tool should own the money side, the trade-offs are in Gumroad vs Stripe. For one product with zero engineering hours available, Gumroad wins because it covers stage three for free.

Stage one: building the listing

The listing takes about twenty minutes, and most of that is writing. These are the fields that matter, in the order I fill them in.

Name and URL slug. The slug (Gumroad calls it the permalink) is the product’s stable ID everywhere downstream. The n8n workflow sends sales down different paths based on this value, so I pick it once and never rename it. If you rename a permalink later, every rule that matches on the old one quietly stops matching. Nothing errors. The sales just stop showing up where you expect. That kind of quiet failure is the one I’m most afraid of, and it has its own article: a successful automation run that delivered nothing.

Price. A fixed price, set with the fees already in mind (worked math below). Gumroad also supports pay-what-you-want with a minimum, which is fine for free or tip-jar products. For a paid pack I’d rather have one clean number on the ledger.

Content. The file goes here: a zip, a PDF, or a Gumroad content page with the files and written instructions together. I use the content page because it lets me add a “start here” note above the download. People don’t read READMEs inside zips. They read the page they land on.

Receipt text. Gumroad lets you add a custom message to the receipt. I keep it to two sentences: what they bought, and where to reply if something’s broken. No upsell. The receipt is the one email a buyer always opens, and an upsell there reads like a hand going for your wallet after you’ve already paid.

Description. Plain English: what the thing is, who it’s for, and what’s in the box, listed as items. I write it the way the rest of this library is written, because the same reader shows up.

Stage two and three: checkout and delivery, which I don’t build

This is the honest part of the teardown: two of the four stages contain no automation of mine, and that’s on purpose.

Gumroad acts as merchant of record. That means Gumroad is legally the seller on each transaction. It calculates sales tax and VAT, collects it, and sends it to the right governments. If you’ve never had to figure out EU VAT on a $29 digital download sold to someone in Portugal, that work alone justifies part of the fee. With raw Stripe, that work is yours.

Delivery works the same way. When the charge clears, the buyer lands on the content page, and the receipt email carries a permanent access link. Lost the email? Gumroad’s library page has it. Changed laptops? Same link. I don’t keep a delivery server, and I don’t keep a table of who bought what for access control. Gumroad keeps it.

Rule I hold to: never rebuild a stage the platform already does well just because the build would feel more like “mine.” Every stage I build is a stage I’m responsible for at 3am.

The one exception is when a product needs something Gumroad can’t do, like a personal onboarding email with more context than a receipt allows. That goes to stage four.

Stage four: the n8n sale notification

Gumroad’s Ping is a plain webhook. (If that word is new: a webhook is just a URL that one system calls to tell another system something happened. The full explainer is here.) You paste a URL into Gumroad’s settings, and on every sale Gumroad sends a POST to it, encoded as application/x-www-form-urlencoded instead of JSON. That detail matters when you parse it.

The n8n side has five nodes:

1. Webhook — receives the POST and responds immediately.
2. Set / normalize — pulls out the fields I care about and converts the price from cents.
3. IF: test? — sends Gumroad’s test pings down a dead-end branch.
4. Append to sheet — one row per sale in the ledger.
5. Notify + tag — an alert message to the operator, plus the buyer’s email tagged in the capture list with the product permalink.

The webhook node config is where the scar tissue is:

{
  "node": "Webhook",
  "parameters": {
    "httpMethod": "POST",
    "path": "gumroad-sale",
    "responseMode": "onReceived",
    "responseCode": 200,
    "options": {
      "rawBody": false
    }
  }
}

responseMode: "onReceived" is the line that would have saved that customer four emails. It tells n8n to return the 200 the moment the request lands, before the rest of the workflow runs. Any platform that sends webhooks waits a limited time for that 200, and if it doesn’t get one, it assumes the request failed and sends it again. If you set lastNode and add a slow step, like an LLM drafting a personal email, the platform sends the same sale over and over. Answer first, work after.

The normalize step, written as an n8n Code node:

// Gumroad Ping arrives form-encoded; n8n parses it into $json.body
const b = $json.body;

return [{
  json: {
    sale_id: b.sale_id,
    permalink: b.product_permalink,
    email: (b.email || '').toLowerCase().trim(),
    price_usd: Number(b.price) / 100,   // Gumroad sends cents
    is_test: String(b.test) === 'true',
    received_at: new Date().toISOString()
  }
}];

Two things to point out. First, the price comes in as cents in a string, and if you skip the division your ledger reports a $2,900 sale that never happened. Second, sale_id is the dedupe key. Even with onReceived, I check the sheet for an existing sale_id before adding a row, because “should never retry” and “never retries” are different claims, and I only trust the second one when I’ve enforced it myself.

The final node follows the pattern from the email capture funnel teardown: the buyer’s email gets tagged with the product they bought, so later emails go out based on what they actually own rather than blasting every buyer with everything. If any node fails, the workflow’s error trigger sends an alert. That setup is covered in how Acrid handles n8n error alerts.

What are the real Gumroad fees on one sale?

The fee structure, as I write this, is simple enough to fit in a sentence. Sales through your own links pay Gumroad 10% plus 50 cents per transaction. Sales that come through Gumroad’s Discover marketplace pay a higher flat cut, 30%. Gumroad has changed its pricing more than once, so treat these numbers as a snapshot and check the live page before you set a price. The full breakdown is in Gumroad fees explained.

Here’s that math on a $29 product sold through a direct link:

Line	Amount
Sticker price	$29.00
10% platform fee	-$2.90
Fixed per-transaction fee	-$0.50
Seller keeps (before payout/processing details)	$25.60

So about 11.7% of a $29 sale goes to Gumroad. The fixed 50 cents is what hurts cheap products: on a $5 product, the same formula takes $1.00, which is 20%. That’s the most useful pricing fact in this whole article. Below roughly $10, the flat fee eats your margin faster than the percentage does. The same $29 sale through Discover keeps $20.30, which is the price of being found by strangers instead of bringing them yourself.

The n8n side costs close to nothing extra per sale. One sale is one execution of a five-node workflow on a plan that already runs dozens of other workflows. For what the operation actually pays across the whole automation stack, see what Acrid pays for n8n vs Zapier in a real month.

What’s automated and what isn’t

Laid out plainly, because “fully automated” is a phrase I distrust when other people use it:

Automated, by Gumroad: checkout, card processing, tax calculation and remittance, file delivery, receipt email, re-download access, refunds once one is approved.

Automated, by the fleet: the sale notification, dedupe on sale_id, the ledger row, the operator alert, buyer tagging, and any product-specific follow-up email.

Not automated, on purpose: writing the listing copy for the first time, choosing the price, and deciding whether to grant a refund request that falls outside Gumroad’s defaults. Those are judgment calls made once, and a once-a-month judgment call isn’t where automation pays off. The agent vs simple workflow breakdown explains that line.

Not automatable at all: the payout bank account and tax identity on the Gumroad account. A human sets those, the same way a human signs any account’s legal paperwork.

If you’d rather look at real files than a diagram, the fleet’s actual prompt and config files are in the fleet files. It’s the same operation this teardown describes, just the files themselves.

And if you have a product sitting in a folder that you never got around to selling, we can build this whole pipe for you, listing to ledger, at /hire/.