Gumroad to Beehiiv, subscribers and Sheets logged

New Gumroad sales should feel like progress. Instead, they often create a tiny backlog of “I’ll add them to the newsletter later” tasks that quietly turns into missed subscribers and messy records.

Newsletter operators notice it first, because list growth looks “off.” Marketing managers end up double-checking exports. And solo creators feel it as nagging admin that steals an hour at the worst time. This Gumroad Beehiiv automation fixes that by subscribing buyers instantly and logging every sale in Sheets.

You’ll see how the workflow moves a buyer from Gumroad into Beehiiv, writes a clean row to Google Sheets, and pings your Telegram channel so nothing slips through.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Gumroad to Beehiiv, subscribers and Sheets logged

Click to explore

flowchart LR

    subgraph sg0["Gumroad Sale Flow"]
        direction LR
        n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/gumroad.png' width='40' height='40' /></div><br/>Gumroad Sale Trigger"]
        n1@{ icon: "mdi:database", form: "rounded", label: "append row in CRM", pos: "b", h: 48 }
        n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>List publications"]
        n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Post subscription"]
        n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Notify in channel"]
        n5@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set ChatID", pos: "b", h: 48 }
        n5 --> n4
        n2 --> n3
        n3 --> n1
        n1 --> n5
        n0 --> n2
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n0 trigger
    class n1 database
    class n2,n3 api
    classDef customIcon fill:none,stroke:none
    class n0,n2,n3,n4 customIcon

The Problem: New buyers fall through the cracks

Gumroad makes it easy to sell, but it does not magically keep your newsletter and your sales log in sync. So you end up exporting buyers, cleaning columns, importing into Beehiiv, then opening a separate “CRM” spreadsheet to paste the same info again. It’s not hard work. It’s the kind of work that gets postponed until “later,” which is exactly how buyers miss your welcome sequence and your reporting becomes a guessing game. One forgotten import can skew a whole week of stats and follow-ups.

The friction compounds. Here’s where it breaks down in real life.

You tell yourself you’ll do the subscriber import at the end of the day, then three more sales come in and it’s suddenly a batch job.
Manual copy-paste creates small errors (a missing email, wrong product name), and those mistakes are hard to spot once they’re in Beehiiv.
Your Google Sheets “source of truth” drifts, so revenue reporting, affiliate notes, and customer history no longer match Gumroad.
You lose the instant signal that a sale happened, which means slower fulfillment, slower outreach, and slower momentum.

The Solution: Auto-subscribe buyers, log the sale, and get alerted

This workflow listens for a new sale event in Gumroad, then takes over the boring parts immediately. When a purchase comes in, n8n grabs your Beehiiv publication details (so the workflow knows exactly where to subscribe the buyer) and sends a “create subscription” request to Beehiiv using your API key. Next, it appends a clean row into Google Sheets, giving you a running, searchable sales-and-subscriber ledger that stays current without anyone touching it. Finally, it formats a quick Telegram message and posts it to your channel so you get a real-time heads-up. One sale in Gumroad turns into a subscriber, a spreadsheet record, and a notification, all in one pass.

The workflow starts with the Gumroad sale trigger. Then it uses HTTP requests to find your Beehiiv publication and create the subscriber. Google Sheets is updated right after, and Telegram confirms it happened.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

Detects every new Gumroad sale the moment it happens.
Finds your Beehiiv publication and creates a matching subscriber via API.
Appends buyer and sale details into Google Sheets automatically.
Sends a Telegram channel alert after the log is written.

Save about 1–2 hours a week once sales are steady.
No more “missed welcome email” moments, because subscribers are added right away.
Cleaner reporting, since Sheets stays aligned with sales events.
Less manual error from copy-paste and CSV wrangling.
Faster response time when a high-value buyer comes in.

Example: What This Looks Like

Say you get 5 Gumroad sales in a typical week. Manually, you might spend about 10 minutes per buyer to export, import into Beehiiv, and then log the sale in Google Sheets, which is close to an hour of admin. With this workflow, you spend maybe 10 minutes once to connect accounts and set your Telegram chat ID, then each sale is processed automatically in the background. You still review your list and your Sheet, but you’re not doing repetitive data entry anymore.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Gumroad to trigger on new sales events
Beehiiv to add buyers as newsletter subscribers
Google Sheets API credentials (get it from Google Cloud Console)

Skill level: Beginner. You’ll connect accounts, paste API keys, and test one sample sale.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A Gumroad sale kicks it off. The workflow uses a Gumroad sale trigger node to listen for new purchases tied to your Gumroad application and API key.

Beehiiv is identified and prepared. An HTTP request pulls your Beehiiv publications, which helps the workflow target the right publication before it creates a subscription.

The buyer becomes a subscriber, then a record. Another HTTP request posts the new Beehiiv subscription. Right after that, n8n appends a row in Google Sheets with the buyer info and sale details you choose to store.

You get a Telegram confirmation. A Set node assigns the proper chat ID or channel handle, and then the Telegram node posts a message so you can see sales flow in without opening Gumroad.

You can easily modify what data goes into Google Sheets and what the Telegram message says based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Gumroad Trigger

This workflow starts when a Gumroad sale event is received.

Add the Sale Event Listener node and set Resource to sale.
Credential Required: Connect your gumroadApi credentials in Sale Event Listener.
Verify the execution flow begins with Sale Event Listener → Retrieve Publications.

Step 2: Connect Beehiiv API Requests

These nodes fetch your Beehiiv publications and subscribe the buyer email from Gumroad.

In Retrieve Publications, set URL to https://api.beehiiv.com/v2/publications and Authentication to genericCredentialType with Generic Auth Type httpHeaderAuth.
Credential Required: Connect your httpHeaderAuth credentials in Retrieve Publications. The node also shows httpBearerAuth configured, so ensure the correct header-based credential is active.
In Create Subscription, set URL to =https://api.beehiiv.com/v2/publications/{{ $json.data[0].id }}/subscriptions, Method to POST, and enable Send Body.
Set the body parameter email to ={{ $('Sale Event Listener').item.json.email }}.
Credential Required: Connect your httpHeaderAuth credentials in Create Subscription.
Confirm the flow Retrieve Publications → Create Subscription → Append CRM Entry.

Step 3: Connect Google Sheets

Store sale details in your CRM spreadsheet.

Open Append CRM Entry and set Operation to append.
Select the Document with ID 1XYMstoZ4j3O5T-UYz21ky7P5bkUtzYXQGYCQTRVWCI4 and the Sheet Sheet1 (gid=0).
Map the columns using these expressions: date → ={{ $('Sale Event Listener').item.json.sale_timestamp }}, email → ={{ $('Sale Event Listener').item.json.email }}, country → ={{ $('Sale Event Listener').item.json.ip_country }}, product name → ={{ $('Sale Event Listener').item.json.product_name }}.
Credential Required: Connect your googleSheetsOAuth2Api credentials in Append CRM Entry.

Step 4: Configure Telegram Notifications

Set a chat ID and send a Telegram message for each new sale.

In Assign Chat ID, set telegramChatId to your actual Telegram chat ID, replacing [YOUR_ID].
In Telegram Channel Alert, set Chat ID to ={{ $json.telegramChatId }}.
Set Text to =🔔 New Gumroad sale! Product: {{ $('Sale Event Listener').item.json.product_name }} Email: {{ $('Sale Event Listener').item.json.email }} Country: {{ $('Sale Event Listener').item.json.ip_country }}.
Credential Required: Connect your telegramApi credentials in Telegram Channel Alert.
Confirm the flow Append CRM Entry → Assign Chat ID → Telegram Channel Alert.

⚠️ Common Pitfall: Leaving [YOUR_ID] unchanged in Assign Chat ID will prevent Telegram Channel Alert from delivering messages.

Step 5: Test and Activate Your Workflow

Run a manual test to confirm each node receives and passes data correctly.

Click Execute Workflow and trigger a test sale in Gumroad to fire Sale Event Listener.
Verify Retrieve Publications returns publication data and Create Subscription receives a valid id in the URL expression.
Check that Append CRM Entry adds a new row in the Gumroad sales CRM spreadsheet.
Confirm Telegram Channel Alert posts the formatted message to the chat ID.
Toggle the workflow Active to enable it for live sales events.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

Gumroad credentials can expire or the app token can be wrong. If things break, check the Gumroad application token in the Gumroad Sale Trigger node first.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
Beehiiv API calls can fail if you’re posting to the wrong publication or missing required fields. Re-run the “Retrieve Publications” request and confirm the publication ID matches what “Create Subscription” is using.

Frequently Asked Questions

How long does it take to set up this Gumroad Beehiiv automation?

About 30 minutes if your API keys are ready.

Do I need coding skills to automate Gumroad Beehiiv automation?

No. You’ll mostly paste API keys and test with a real sale.

Is n8n free to use for this Gumroad Beehiiv automation workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Beehiiv and Gumroad API usage (typically minimal for simple subscription and logging calls).

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this Gumroad Beehiiv automation workflow for tagging subscribers by product?

Yes, but you’ll do it in two places. First, capture the product name from the Gumroad sale trigger output and map it into the data you send to Beehiiv in the “Create Subscription” HTTP request. Then adjust the Google Sheets “Append CRM Entry” mapping so the product (and any tag you derive from it) is stored in its own column. Common tweaks include tagging by product tier, adding first/last name when available, and changing the Telegram message to include sale amount.

Why is my Gumroad connection failing in this workflow?

Usually it’s an invalid or expired Gumroad application token. Create or re-copy the access token from Gumroad (Settings → Advanced), then update it inside the Gumroad Sale Trigger node in n8n. If the trigger still doesn’t fire, confirm you’re testing with a real sale (not a draft product) and that the product is actually listed.

How many sales can this Gumroad Beehiiv automation handle?

A lot.

Is this Gumroad Beehiiv automation better than using Zapier or Make?

For this workflow, n8n is often the better fit if you care about reliability and control. You can fetch publications, branch on conditions, and log to Sheets without paying extra for every “advanced” step, and self-hosting removes the execution ceiling entirely. Zapier and Make can still work, frankly, especially for a simple two-step “sale → add subscriber” setup. The moment you want better logging, error handling, or custom messaging, n8n tends to feel less restrictive. Talk to an automation expert if you want help choosing.

Once this is running, new buyers become subscribers and clean records automatically. Your list stays accurate, your Sheet stays current, and you stop thinking about it.

Gumroad to Beehiiv, subscribers and Sheets logged

How This Automation Works

n8n Workflow Template: Gumroad to Beehiiv, subscribers and Sheets logged

The Problem: New buyers fall through the cracks