Resources · n8n integration

Gumroad n8n integrationAutomate Gumroad with n8n.

Gumroad raises the event, n8n takes it from there. The Gumroad n8n integration is a trigger node: choose the resource that fires, activate the workflow, and each event reaches n8n in seconds over a webhook. Everything else on the Gumroad API stays reachable with HTTP Request.

Try the Gumroad integration on n8n

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Gumroad n8n integration actually do?

Gumroad is an online platform that lets creators sell products directly to consumers. In n8n, the pairing comes down to one node, the Gumroad Trigger, version 1, which handles Gumroad events via webhooks. A webhook is simply a URL that Gumroad calls the moment something happens, so nothing has to be checked on a timer. The n8n catalog lists no Gumroad action node, so the trigger opens the workflow and HTTP Request covers the calls you want to make back to the Gumroad API.

The first workflow most people build is a running log. The trigger fires, the workflow keeps the values worth keeping, and a row lands in Google Sheets. Pulling a value out of the event takes one expression, {{ $json.field }}, where field is the key of the incoming event you want. An expression is just that placeholder syntax n8n resolves at run time with the data of the item it received.

The second one is louder. Same trigger, different destination: a message posted to a Slack channel so the people who care see the event without opening Gumroad. Since delivery is a webhook, the message shows up in seconds rather than at the end of some polling cycle, which is what makes this pattern worth building at all.

The third one is quieter and pays off later. Write the raw event into a file in Google Drive, one per run, and you have an archive of exactly what Gumroad sent, in the shape it sent it. Handy the day a downstream step misbehaves and nobody remembers what the payload looked like.

Past that, the Gumroad node in n8n is a trigger and nothing more. Anything you want to do against the Gumroad API belongs in an HTTP Request node, which calls any endpoint of the service and reuses the same Gumroad credential through its predefined authentication. So the split is clean: the trigger starts the run, HTTP Request does the talking.

Two things to keep in mind before you build. There is no list of events to tick in the node: the required Resource parameter decides what fires, and any narrowing beyond that happens inside the workflow. And the webhook is registered when the workflow is activated, so a workflow left in draft receives nothing. If you want the wider picture on the platform first, the n8n review covers what the tool is good at, and the n8n training goes through building workflows like these end to end.

Connect

How do you connect Gumroad to n8n?

  1. 01

    Create the Gumroad application

    Start from a Gumroad account, then create an application for the API. Gumroad documents the steps in its help article on creating an application. That application is what produces the Access Token used by the first authentication method, and it is also where an OAuth2 setup begins. You only do this once per Gumroad account, whatever the number of workflows you plan to run afterwards.

  2. 02

    Create the credential in n8n

    The Gumroad Trigger accepts two authentication methods. The short path is the API access token: paste the Access Token from your application into a new Gumroad credential. The other path is OAuth2, which on a self-hosted n8n needs an OAuth Redirect URL, a Client ID and a Client Secret. A credential is created once in n8n and reused by every workflow after that.

  3. 03

    Wire the OAuth2 application, then activate

    For OAuth2, go to Settings > Advanced in Gumroad, paste the OAuth Redirect URL from your n8n credential as the Redirect URI, and create the application. Gumroad returns an Application ID and an Application Secret: they go into Client ID and Client Secret. Then add the Gumroad Trigger to a workflow, pick the credential and the Resource, and activate the workflow so n8n registers the webhook URL.

Triggers

What starts a Gumroad workflow?

Gumroad Trigger is the node that starts a workflow when Gumroad calls n8n. Activate the workflow: n8n gives you the webhook URL to register in Gumroad, and every call becomes an execution.

What you see in n8n

Configuration notes

01Set up the Gumroad TriggerThis node handles Gumroad events via webhooks, and it is the entry point of every Gumroad workflow in n8n. A trigger is the node that starts a run instead of waiting to be called by another node. Version 1 keeps the configuration short, and activating the workflow is what registers the webhook URL with Gumroad, so a workflow still in draft sits there receiving nothing.

This node handles Gumroad events via webhooks, and it is the entry point of every Gumroad workflow in n8n. A trigger is the node that starts a run instead of waiting to be called by another node. Version 1 keeps the configuration short, and activating the workflow is what registers the webhook URL with Gumroad, so a workflow still in draft sits there receiving nothing.

Key parameters

  • Resource: required dropdown, it selects the resource that is going to fire the event. Pick the one the workflow is meant to react to rather than accepting everything and sorting it out three nodes later.
When to use it
whenever a run has to start from something happening on Gumroad instead of from a clock. Delivery is a webhook, so there is no polling interval to tune and no waiting for the next check.
02Read the event payloadThe node has no list of events to tick, so what it receives arrives the same way every time: one item at the start of the run, carrying the event as Gumroad sent it. From there it is expressions all the way down. {{ $json.field }} reads whichever key of the event a later node needs, and a field marked required blocks that node when it resolves to nothing, which is usually how a mapping mistake shows up on the very first test run.

The node has no list of events to tick, so what it receives arrives the same way every time: one item at the start of the run, carrying the event as Gumroad sent it. From there it is expressions all the way down. {{ $json.field }} reads whichever key of the event a later node needs, and a field marked required blocks that node when it resolves to nothing, which is usually how a mapping mistake shows up on the very first test run.

Use cases
a routing step placed right after the trigger sends one branch to a spreadsheet for the record and another to a chat channel for the people who want to know now. When the run also has to talk back to Gumroad, HTTP Request calls the endpoint you need and reuses the same credential, so the workflow keeps a single place where authentication lives.
Need help

Need help automating Gumroad with n8n?

A person reads every message.

FAQ

Gumroad and n8n, the questions that come next

01Is the Gumroad n8n integration free to use?
Yes on the n8n side. The Gumroad Trigger ships with n8n, so there is nothing to install and nothing extra to pay for the node itself, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow built on one runs the same on the other. What a Gumroad account costs is a separate question and is not covered here. Budget your time instead for the setup, which is the application on the Gumroad side, one credential in n8n, and activating the workflow so the webhook gets registered.
02What credentials does the Gumroad Trigger need?
Two methods are supported. The first is an API access token: you create an application in Gumroad, it generates an Access Token, and that token goes into a Gumroad credential in n8n. The second is OAuth2, which on a self-hosted n8n asks for an OAuth Redirect URL, a Client ID and a Client Secret. You create the application under Settings then Advanced in Gumroad, paste the redirect URL from the n8n credential as the Redirect URI, and map the Application ID and Application Secret onto Client ID and Client Secret. The default scope is view_sales, and anything beyond it goes through the Custom Scopes toggle.
03What are the limits of the Gumroad node in n8n?
The n8n catalog gives Gumroad a trigger and no action node, so the node itself starts workflows rather than running operations on your behalf. That is not a dead end: HTTP Request calls any endpoint of the Gumroad API and reuses the same credential through its predefined authentication, which is the standard route for anything outside a dedicated node. The other thing worth knowing is that the trigger comes with no list of events to select. The required Resource parameter decides what fires, and whatever narrowing you need after that happens in the workflow itself, on the data the event carries.
04Does the Gumroad Trigger react in real time?
Yes, as close to it as automation gets. The node works by webhook: n8n registers a URL with Gumroad when the workflow is activated, Gumroad calls that URL when the event happens, and the run starts within seconds. There is no polling, meaning no background job asking Gumroad every few minutes whether something new happened, and therefore no interval to tune and no lag baked into the design. The practical consequence is the one that catches people out: activation is what registers the webhook, so keep the workflow active if you expect it to receive anything.
05n8n or Make for Gumroad?
It depends on four things, and price per feature is not the main one. Hosting comes first: n8n can be self-hosted with Docker or npm, or used on n8n Cloud, while Make is hosted only. Data control follows from that, since a self-hosted instance keeps the event payloads on infrastructure you own. The cost model differs too, as Make bills per operation, which changes how you feel about a workflow that fans out into many steps. Last is the visual logic and how each editor lets you branch and map data. Both run this kind of webhook workflow, so pick on those criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations