Will the email actually sound like me, or does every buyer get the same template?

Each email is written fresh for the specific product the buyer purchased. The agent reads that product's description and writes a short, friendly message that references what it is and one next step to use it, so a buyer of a course gets a different note than a buyer of a template or membership.

What happens on refunded or test sales?

Nothing goes to Mailchimp. Test purchases and refunded sales still trigger the workflow, but the agent skips the audience upsert and the tag step so your list and welcome sequences stay clean. You can also skip the email on tests if you prefer.

Do I need a paid Mailchimp plan?

Any Mailchimp plan that supports audience tags will work. The workflow adds or updates the buyer in the audience you choose and applies a tag; your existing automations do the rest.

Does this replace Gumroad's built-in receipt email?

No. Gumroad still sends its normal receipt with download and license info. This adds a separate personal thank-you from your Gmail address, so buyers get both.

Can I use different tags for different products?

Yes, that's the point. Each Gumroad product maps to its own Mailchimp tag, so a buyer of Product A joins one sequence and a buyer of Product B joins another. You control the mapping.

Personal Gumroad thank-you email plus Mailchimp tagging on every sale

Trigger: a Gumroad webhook on the sale resource subscription. Each incoming payload represents one new sale and includes at least the sale id, buyer email, buyer name, product id, product name, price, order number, variants, custom fields, and the test and refunded flags.

When a sale fires, do the following, in this order:

1. Look up the full sale on Gumroad using Get Sale with the sale id from the webhook. Use this as the source of truth for buyer email, buyer name, amount, order number, and the test / refunded flags — do not trust the webhook payload alone.

2. Pull the product catalog on Gumroad with List Products so you have the full product record on hand: long description, product type (course, template, membership, ebook, license, physical, etc.), preview or download URL, and any custom fields. Match the sale to the correct product row by product id.

3. Draft a warm, personalized thank-you email from me to the buyer. It must: address them by first name when available, name the exact product they bought, reference in one short sentence what that product is or does (pulled from the product description), and include one specific next step that actually helps them use it — where to log in for a membership, how to start the first module of a course, what to open first with a template, and so on. Keep it short (aim for 4 to 8 sentences), friendly, and non-templated so it reads like the creator wrote it. No marketing polish, no em dashes, no generic 'thanks for your purchase' openings. Vary the phrasing by product type. Sign off from me.

4. Send that email from my connected Gmail using Send a Message. To: the buyer's email from the Get Sale result. Subject: something specific to the product they bought, not a generic 'order confirmation'.

5. If the sale is a test purchase or refunded, stop here. Do not touch Mailchimp. In the run summary, note that Mailchimp was skipped because the sale was a test/refund.

6. Otherwise, upsert the buyer into my Mailchimp audience using Add or Update Member (Upsert) with status_if_new set to subscribed and merge fields populated with the first and last name from the sale.

7. Then apply a product-specific tag to that member using Add or Remove Member Tags with status active. Use a stable, slug-style tag name derived from the product name (for example, gumroad-purchase:starter-course) so my downstream Mailchimp automations can key off it. One tag per product; if a buyer already has the tag from a prior purchase, that's fine — re-applying is a no-op.

Return a short run summary: the buyer, the product, the subject line used, and whether Mailchimp was updated or skipped (and why).

What it does

Fires the instant Gumroad records a new sale, so buyers hear from you while their purchase is still on-screen.
Writes a warm, non-templated thank-you email that names the exact product the buyer just paid for and points them to a specific next step to use it.
Sends the email from your own Gmail address so it lands from a real person instead of a no-reply receipt.
Adds or updates the buyer in your Mailchimp audience and applies a product-specific tag, so your existing welcome sequence for that product takes over automatically.
Skips the Mailchimp step entirely on test purchases and refunded sales so your list stays clean.

What you’ll need

A Gumroad account you can add a webhook to
A Gmail login you're happy to send thank-you emails from
A Mailchimp audience with tags already set up for the welcome sequences you want each product to trigger

How to customize it

Tone and length of the thank-you email (formal, casual, or playful) and the sign-off name
Which Mailchimp tag each product should map to, so different products can kick off different drip sequences
Whether the email includes a specific next-step link (log-in URL, first lesson, template starter file) or a small thank-you discount

Use cases

Onboarding Automation
Email Automation

Send Gumroad buyers a personal thank-you and tag them in Mailchimp

Integrations

Type

Categories

What it does

What you’ll need

How to customize it

Use cases

FAQs

Related prompts