Log every Gumroad sale to Google Sheets and Slack
The moment a Gumroad sale comes in, drop a full row into your revenue ledger and ping the team channel with the summary.
Gumroad
Google Sheets
Slack BotSalesFinanceData SyncNotifications & AlertsWhenever Gumroad fires a sale webhook (the sale resource_subscription), append a new row to my Google Sheets sales ledger using Append Values, and post a short Slack notification summarising the sale.
Trigger: Gumroad webhook, sale resource. The full sale payload is available on the incoming event, so no extra Gumroad reads are required. Get Sale is available if any field needs enrichment.
Filter first: if the payload indicates the sale was refunded (any refunded flag or refund timestamp) OR is a test purchase (test flag), stop the workflow without writing anything. Only real, non-refunded sales should make it past this step.
Step 1: Google Sheets Append Values on my sales ledger spreadsheet. Append a single new row with these columns in order: sale timestamp (ISO8601 from the payload), buyer email, product name, variant (blank if no variant), price in dollars (convert from cents, formatted like 19.00), currency (uppercase, e.g. USD), quantity, and referrer. Use USER_ENTERED so the timestamp and numbers keep their native types in the sheet.
Step 2: Slackbot Send a Message to the sales alerts channel. Keep the copy short and scannable, one line is fine: product name, price in dollars with currency, and buyer email. Example: "New sale: Indie Handbook — $19.00 USD — buyer@example.com".
This is deterministic fan-out, no AI drafting or judgement calls. Every field is known upfront from the webhook payload. If either step fails, surface the error but do not retry the other step blindly — the sheet is the source of truth for the ledger.
What does this prompt do?
- Fires the instant a new Gumroad sale is completed, using Gumroad's sale webhook
- Appends a new row to your Google Sheets ledger with the sale timestamp, buyer email, product name, variant, price in dollars, currency, quantity, and referrer
- Posts a short Slack message summarising the sale (product, price, buyer email) to the channel your team actually checks
- Skips refunded sales and test purchases so the ledger and the notifications stay accurate
What do I need to use this?
- A Gumroad account that is actively taking sales
- A Google Sheet with a header row ready for the sale columns
- A Slack workspace and the channel where you want sale pings to land
How can I customize it?
- Change the Slack channel or route different products to different channels
- Swap the spreadsheet or tab you write to, or add extra columns (order ID, discount code, tax)
- Adjust the Slack summary wording, or include the variant and quantity in the ping
FAQs
How fast does the sheet and Slack update after a sale?
Will refunded orders or test purchases show up in the ledger?
Is the price logged in dollars or cents?
Can I add or remove columns later?
Does this replace Gumroad's own analytics?
Related templates
When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.
Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.
Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.
Every weekday at 7am, sign in to the tender portals you track, filter new notices against your bid criteria, and open a deal for the ones worth chasing.
Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.
Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.
Stop copy-pasting Gumroad sales into a spreadsheet.
Wire your sales ledger and your Slack channel up once and let every future sale log itself.