Menu
Mattering Automations connector

A Gumroad MCP that is honest about the fifteen nodes that touch real customers

81 nodes on Gumroad's v2 API: products and variants, sales and refunds, license keys, discount codes, audience emails and workflows, the media library, payouts, earnings and tax forms. Fifteen of them are flagged destructive, and five of those delete nothing at all. They are flagged because a refund moves real money to a real customer, a published email reaches an audience with no recall, and a rotated license key stops working on the machine it was already installed on.

81 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Gumroad MCP connector does

The Gumroad connector for Mattering Automations is 81 nodes on Gumroad's v2 API at api.gumroad.com, covering every operation Gumroad documents. Thirty three read and forty eight act. Products, variant categories and variants cover the catalogue. Sales, refunds, receipts, shipping and access revocation cover an order after it is placed. License keys cover software delivery, with enable, disable, rotate, seat decrement and a verify node that needs no credential at all. Offer codes, custom checkout fields, covers, thumbnails and the refund policy cover the storefront. Audience emails and workflows cover the mailing list. Payouts, annual earnings and tax forms cover the money coming back out. The media library and the four step file attachment flow cover assets.

Every capability is a node on the Automations canvas, and every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. So an assistant can read a week of sales with Gumroad: List Sales, spot the refund requests, and stop there while a person decides whether any money moves.

Gumroad has no subscription plans, which makes the usual question on a page like this unusually simple to answer. There is no Pro tier, no Business tier and no monthly bill, so there is no plan for API access to sit behind. Gumroad's published pricing is a per-transaction cut and nothing else: 10 percent plus 50 cents on sales through your own profile and direct links, and 30 percent when a new customer finds you through Gumroad's Discover marketplace. Any account can create an application, generate an access token and call the API immediately. Nothing on this page is gated behind an upgrade, and there is no free tier exclusion list to read, because there is no paid tier to be excluded from.

Fifteen nodes carry a destructive flag and it is worth reading which ones and why, because the flag is not only about deletion. Ten of them delete: a product, a variant, a whole variant category, an offer code, a custom checkout field, an audience email, a media file, a product cover, a product thumbnail or a webhook subscription. Gumroad documents no undelete for any of them and this API has no restore endpoint, so a workflow cannot put any of them back. The other five delete nothing and are flagged because of what they do to a person. Gumroad: Refund Sale moves money out of the seller's balance and back onto a real customer's card, and there is no unrefund endpoint anywhere on this API. Gumroad: Send Email publishes a draft to its audience, potentially every customer and follower the account has, with no recall. Gumroad: Rotate License Key issues a new key and invalidates the old one, so whatever the customer already installed stops validating and only that node's response will ever tell you the replacement. Gumroad: Disable License stops a customer's software validating on its next check-in. Gumroad: Revoke Sale Access takes a paying customer's library and downloads away without refunding them.

Two more nodes reach a customer without being flagged, and both say so in their own descriptions. Gumroad: Resend Sale Receipt puts a real email in a buyer's inbox. Gumroad: Mark Sale As Shipped tells the buyer their order is on its way and shows them the tracking link, with no documented way to unmark it. And two workflow nodes can turn an edit into a send: on a published workflow whose send to past customers option is on, Gumroad: Add Workflow Email schedules the new step for eligible past customers, so a step added to a year old onboarding sequence can go out to everyone who ever bought, and Gumroad: Update Workflow Email can reschedule people already partway through when the delay changes.

There is no idempotency mechanism on this API. Nothing accepts an idempotency key, so a retried create makes a second product, a retried send delivers the campaign twice, and a retried refund issues a second refund. Every node that creates something says so in its own description, and the practical consequence is that retry logic belongs on your side of the wire: guard a money-moving or audience-reaching step with a condition, a data table lookup or an approval rather than a retry policy.

Two mechanical details shape how Gumroad workflows have to be built. Pagination is an opaque cursor: paginated listers return a next page key and accept it back, and there is no page number, no offset and no page size parameter anywhere on this API, so a workflow cannot jump to page seven and cannot ask for five hundred rows. Two endpoints break that pattern in useful ways and the nodes say which: Gumroad: List Product Subscribers returns everything by default and only paginates on request, capped at 100, and Gumroad: List Product Reviews returns up to 100 per page with no way to change it. Separately, responses from the v2 API are enveloped with a success flag, and a rejected request can answer HTTP 200 with success set to false and a message explaining why. The connector reads that flag rather than trusting the status, marks the node result unsuccessful when it is false, and lifts the message into the result as an error message so a workflow can branch on it without digging through the payload.

The money handling deserves its own warning, because the failure is silent. Every money column on a Gumroad sale, including price, the Gumroad fee, tax, shipping, tips and variant price, is expressed in the minor units of that row's own currency, and the currency lives on the row rather than on the account. So a window of sales can mix currencies, and totalling the price column across it is wrong for the exchange rate in the obvious way and wrong by a factor of a hundred in a way nobody notices, because Gumroad documents that Japanese yen has no minor units at all. That is why the connector declares only quantity as safely aggregatable on the sales node. It is unitless, so it is the one column that can be summed across a mixed currency window without being quietly incorrect.

Gumroad does not publish an MCP server of its own. Its first-party AI-facing tool is a command line interface that wraps the API and that Gumroad describes as built for humans and AI agents alike, rather than a Model Context Protocol server, and there is none in Gumroad's open source codebase or anywhere else it publishes. Community MCP servers for Gumroad do exist, built by independent developers rather than by Gumroad. So there is no vendor server to weigh against this connector, and the practical way to put Gumroad behind an MCP-capable assistant today is a connector like this one: nodes that also run on a schedule with nobody present, chain with every other connector in one workflow, hold the access token once in a shared workspace store rather than in each person's local config, and carry a destructive flag on the fifteen that need one.

One connection, three surfaces

  • Visual automations. Drag Gumroad nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Gumroad node, ready to drop on the canvas

81 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 33

Gumroad: Download Tax Form

Download the PDF of one tax form. This is the ONLY endpoint on the Gumroad API that does not return JSON on success: it answers with the raw PDF bytes and a Content-Disposition attachment header, and only switches to a JSON error envelope when it fails. This node therefore returns the file's metadata and its bytes base64 encoded rather than a parsed object, so it can be written to storage or attached to an email by a following node. Anything larger than 8 MB comes back as metadata only, because a very large base64 blob would bloat every downstream node input. The document contains the seller's tax identity, so treat the output as sensitive. US only, tax centre enabled, and requires the view_tax_data scope.

Gumroad: Get Annual Earnings

Fetch the annual earnings breakdown that matches the totals in Gumroad's own Tax Center: gross, fees, taxes, affiliate credit and net, all in the smallest currency unit, for one tax year. FULLY REFUNDED SALES ARE EXCLUDED from every aggregate, so this will not equal a naive sum of the sales list, and that is correct rather than a discrepancy. US only, tax centre enabled. A year outside the seller's available range, which runs from the account creation year to last year, returns 404. Requires the view_tax_data scope.

Gumroad: Get Email

Fetch one audience email in full: subject, HTML body, audience type, state, publish and schedule times, and its recipient and audience counts. Requires edit_emails or account.

Gumroad: Get Offer Code

Fetch one discount code by id, with its coupon text, its discount and how many times it has been redeemed. As with the lister, a fixed amount code carries amount_cents and a percentage code carries percent_off. Requires edit_products or account.

Gumroad: Get Payout

Fetch one payout, optionally with the sale ids it covers and with a full transaction ledger matching the exported payout CSV. The transaction list is the useful part for reconciliation: each entry carries a type, date, purchase id, item and buyer, taxes, shipping, sale price, Gumroad fees and net total, and the types include Sale, Chargeback, Full Refund, Partial Refund, the PayPal and Stripe Connect refund and affiliate variants, and the payout transfers themselves. Note that transactions are OFF by default while sales are ON. Requires the view_payouts scope.

Gumroad: Get Product

Fetch one product in full. This returns everything the lister returns plus custom_html, the custom landing page, so it is the read half of the custom landing page workflow. It is also the only place to see a product's covers and attached files. Note that each attached file comes back as a TIME LIMITED SIGNED download URL rather than the canonical file URL, and the canonical URL cannot be recovered from a read, so a workflow that attaches files must keep the URL that Gumroad: Complete File Upload gave it. Requires view_profile, edit_products or account.

Gumroad: Get Profile Custom HTML

Read the seller's custom profile landing page: the stored source HTML, the rendered HTML, whether a landing page is in effect and the public profile URL. Gumroad keeps only the latest version with no history, so this node plus your own version control is the whole backup story for that page.

Gumroad: Get Public Product Page

Read the public display data for ANY Gumroad product page, with no credential at all. This is the read counterpart to the authenticated product nodes: it returns exactly what the rendered page shows, meaning price, covers, description, variants, ratings and the refund policy, and it never exposes buyer, seller private or analytics fields. Because it needs no token it works against products you do not own, which makes it the node for competitor and catalogue monitoring. Note the response has NO success key: it is a bare object with an api_version, so branch on the HTTP status rather than on success.

Gumroad: Get Public Profile

Read any creator's public profile with no credential: display name, bio, avatar, social links and the products shown in their public profile sections. Seller private fields such as email, balance and tax information are never included. Like the public product page, the response has NO success key, so branch on the HTTP status.

Gumroad: Get Refund Policy

Read the account level refund policy: the period, the display title derived from it, the fine print and whether it is IN EFFECT. Read in_effect before writing anything, because it decides which of two mutually exclusive systems is live: when it is true the account policy governs and per product refund_period values are refused, and when it is false the product level fields govern and updating this policy is refused.

Gumroad: Get Sale

Fetch one sale in full. The detail shape is RICHER than the lister's and the extra fields are the ones a finance workflow actually needs: tip_cents, the tax label and whether tax was included, the payment processor and its transaction id and fee, the buyer's review, and a buyer_presentment block giving what the customer was actually charged in their own currency with the FX rate used. Requires view_sales.

Gumroad: Get Subscriber

Fetch one subscriber by id, with their product, email, purchase ids, recurrence, license key and the cancellation, end and failure timestamps that decide whether the subscription is still alive. Note the response key is the plural subscribers even though it holds a single object, which is a Gumroad quirk rather than a typo here. Requires view_sales.

Gumroad: Get User

Fetch the authenticated seller's own account: name, bio, user id, profile picture and profile URL. Two conditional fields worth knowing about because their absence is not an error: email only appears for a token holding view_sales, and url only appears once a username is set. This is also the cheapest way to confirm a credential works, which is what the connector's auth test uses.

Gumroad: Get Variant

Fetch one variant by id: its name, its price difference in the smallest currency unit and its purchase cap. Requires view_profile, edit_products or account.

Gumroad: Get Variant Category

Fetch one variant category by id. The category record itself is just an id and a title; to see the options inside it use Gumroad: List Variants. Requires view_profile, edit_products or account.

Gumroad: Get Workflow

Fetch one active workflow with every email step in it and each step's delivery statistics: sent count, opens, open rate, clicks and click rate. This is the only place the step ids appear, so run it before editing a step. Requires edit_emails or account.

Gumroad: List Categories

Fetch Gumroad's full product category tree, flat, with each entry's id, name, human label, full path and parent id. This is the lookup behind the category field on product create and update: Gumroad wants the PATH, for example design/ui-and-web/figma, not the label. It is also the source for the category picker on both product write nodes, so run it once and the pickers fill themselves.

Gumroad: List Custom Fields

List the extra questions a product asks a buyer at checkout, each with its name and whether it is required. The name is the identifier as well as the label, so this is the node to run before updating or deleting one. Note the shape quirk: required comes back as the STRING false rather than a boolean. Requires edit_products or account.

Gumroad: List Emails

List the seller's audience emails with their state, audience type, schedule and recipient counts. Filter with type to see only published, scheduled or draft. This is the source for every email picker in this connector, and the node to run first when auditing what is queued to go out. Requires edit_emails or account.

Gumroad: List Media Files

List the images in the account's media library, newest first, with each file's id, name, extension, size, hosted URL and status. The library exists because custom product and profile pages render under a Content Security Policy that BLOCKS images loaded from other sites: only inline data images and Gumroad's own asset hosts are allowed, so an image hosted anywhere else simply will not appear. Upload it here first and embed the URL this returns. Files belong to the account rather than to one product, so the same image can be reused everywhere. Requires view_profile specifically: this is the endpoint family Gumroad names when it says an account only token is refused.

Gumroad: List Offer Codes

List a product's discount codes with how many times each has been used. The response shape varies per row and that is the thing to wire around: a fixed amount code carries amount_cents and a percentage code carries percent_off, never both, so read whichever is present rather than assuming one. A universal code is one that applies to every product on the account, and those appear here too. Requires edit_products or account.

Gumroad: List Payouts

List the seller's payouts with amount, currency, status, creation and processing timestamps, the processor used and a masked bank account or PayPal address. Statuses seen here include payable, pending, completed and failed. One row can be unlike the others: the upcoming payout is included by default and carries a NULL id, because it has not happened yet, so any workflow keying on id has to handle that or turn include_upcoming off. Requires the view_payouts scope.

Gumroad: List Product Reviews

List the reviews shown on one of your product pages, newest first, with the rating, the buyer's message, the purchase id and your own published response if you left one. Only PUBLICLY VISIBLE reviews are returned, meaning a buyer left a written message or an approved video: a star only rating with no message still counts towards the product's average_rating but never appears here, so the row count and the review count on the product page will not agree. Up to 100 per page. Available with any read scope.

Gumroad: List Product Subscribers

List the ACTIVE subscribers to one membership or subscription product, with each one's email, purchase ids, recurrence, license key and lifecycle timestamps. Reading the state is the part that catches people out: a subscription is TERMINATED if any of failed_at, ended_at or cancelled_at is set and in the past, so those three have to be checked together rather than trusting one. The status field is one of alive, payment_method_update_required, pending_cancellation, pending_failure, failed_payment, fixed_subscription_period_ended or cancelled. Pagination is opt in here, unlike the rest of this API: without paginated the endpoint returns everything, and with it the page is capped at 100. Requires view_sales.

Gumroad: List Products

List every product on the authenticated seller's account, with price, currency, publication state, tags, category, thumbnail and the whole variant tree for tiered memberships. This is the node most Gumroad workflows start from, and it is the source for every product picker in this connector. Two shape notes worth knowing before wiring to it: url is documented as deprecated and always null, so read short_url instead, and sales_count and sales_usd_cents only appear when the token holds view_sales or account. The list shape also differs from the single-product shape, which adds custom_html. Requires view_profile, edit_products or account.

Gumroad: List Resource Subscriptions

List the account's active webhook subscriptions FOR ONE RESOURCE. The resource name is required, so there is no way to see every subscription in a single call: to audit them all, run this once per resource across the eight supported names. Each row carries the subscription id needed to remove it.

Gumroad: List Sales

List the seller's successful sales, filterable by date range, product, buyer email, order id, customer name or license key. Each row is a full purchase record: price and fee in the smallest unit of the SALE'S OWN currency, buyer email, variants chosen, answers to custom fields, UTM parameters, subscription state, affiliate credit and any license key. The window is after and before as YYYY-MM-DD dates, and pagination is the opaque next_page_key cursor with no page size to tune. The currency is per row rather than per account, which matters before adding any of these numbers up. Requires view_sales.

Gumroad: List Tax Forms

List the tax forms Gumroad has generated for the seller, currently 1099-K and 1099-MISC, each with its year, type and filing timestamp. A null filed_at means the form exists but has not been filed yet. This is US ONLY and only for sellers with the tax centre enabled, so an account outside that will get nothing back rather than an explanation. Asking for a year outside the seller's available range, which runs from the account creation year to last year, returns 404. Requires the view_tax_data scope.

Gumroad: List Upcoming Payouts

Fetch the payouts that have not been paid yet. There can be at most two at any moment. Every row has a NULL id and a payable status because these have not happened, so the amounts are forecasts that can still move as sales, refunds and chargebacks land: do not store them as though they were settled figures. Requires the view_payouts scope.

Gumroad: List Variant Categories

List a product's variant categories. A category is the GROUPING, for example Colors or Tier, and the individual options inside it are variants. For a tiered membership the category is usually the single Tier group and each membership tier is a variant. This is the source for every variant category picker in this connector. Requires view_profile, edit_products or account.

Gumroad: List Variants

List the options inside one variant category, with each one's name, price difference in the smallest currency unit and purchase cap. This is the source for every variant picker in this connector, and it needs both the product and the category first because a variant only means something inside its own category. Requires view_profile, edit_products or account.

Gumroad: List Workflows

List the seller's ACTIVE workflows, newest first, with each one's audience type, trigger, product, state, step count and audience filters. Only active workflows are returned, so this is not a complete inventory of everything ever built. It is the source for the workflow picker on the two workflow email nodes. Requires edit_emails or account.

Gumroad: Verify License

Check whether a license key is valid for a product, and get back the purchase behind it: buyer email, price, quantity, subscription state, refund and dispute flags, and the number of times the key has been used. This is the ONE endpoint on the whole Gumroad API that needs no credential and no OAuth application at all, which is why it can run from a customer's own machine. Watch increment_uses_count: it DEFAULTS TO TRUE, so every plain check burns a seat on a multi seat license. Set it off for a read only check such as a dashboard poll. Read the refunded, disputed and subscription_ended_at fields as well as the success flag, because a valid key can belong to a refunded purchase.

Action nodes 48

Gumroad: Abort File Upload

Cancel a multipart upload that failed partway through, so the half uploaded parts are not left behind. Read the status field in the response, because it has two meanings and only one of them is final: accepted means S3 took the cancellation but parts still in flight may land seconds later, and already_gone means there is no multipart session for this upload_id. Call this again while you see accepted, and stop when you see already gone. Requires edit_products.

Gumroad: Add Product Cover

Add a cover to a product from a publicly reachable URL. Gumroad FETCHES the URL server side and stores its own copy, so the URL has to be reachable over HTTP or HTTPS from the public internet: a private link or a presigned upload URL will not work. Images in JPEG, PNG and GIF are accepted, and so are video URLs including YouTube and Vimeo, which come back as an oembed cover. This is a PUBLICLY VISIBLE change: the cover appears on the product page as soon as it is stored. The response returns the full cover list and the main_cover_id; reorder them with the cover_ids field on Gumroad: Update Product. Gumroad has no idempotency mechanism, so running this node twice creates two records. Guard retries on your side. Requires edit_products.

Gumroad: Add Workflow Email

Add one email step to an existing workflow, without changing whether the workflow is published. The new step inherits the workflow's state, and that is the part that reaches people: on a PUBLISHED workflow whose send_to_past_customers is true, adding a step SCHEDULES IT FOR ELIGIBLE PAST CUSTOMERS, so a step added to a year old onboarding sequence can go out to everyone who ever bought. Check the workflow's state and that flag first. Abandoned cart workflows do not accept added steps at all. Gumroad has no idempotency mechanism, so running this node twice creates two records. Guard retries on your side. Requires edit_emails or account.

Gumroad: Complete File Upload

Step 3 of 4: finalize the multipart upload started by Gumroad: Presign File Upload by submitting the ETag of every part. The S3 object is not usable until this succeeds. The returned file_url is the CANONICAL url and the only value that can be attached to a product, so store it: reading the product back later gives a time limited signed URL instead and the canonical one cannot be recovered from a read. Step 4 is passing that URL to Gumroad: Create Product or Gumroad: Update Product. Requires edit_products.

Gumroad: Create Custom Field

Add an extra question to a product's checkout, for example a phone number or a Twitter handle. A PUBLICLY VISIBLE change: the field appears at checkout immediately, and marking it required means a buyer cannot complete a purchase without answering. Whatever buyers enter is returned on the sale record under custom_fields, so only ask for what you need. The name doubles as the identifier for later updates and deletes. Gumroad has no idempotency mechanism, so running this node twice creates two records. Guard retries on your side. Requires edit_products or account.

Gumroad: Create Email

Create an audience email. By default it is a DRAFT and nothing is sent, which is the safe way to use this node. Setting publish to true, or draft to false, SENDS IT IMMEDIATELY to the chosen audience, which can be every follower and customer the seller has, and there is no recall. Scheduling is a separate step on an existing email rather than an option here. Gumroad has no idempotency mechanism, so running this node twice creates two records. Guard retries on your side. A retried run with publish on sends the campaign twice. Requires edit_emails or account.

Gumroad: Create Offer Code

Create a discount code. name is the text a buyer types at checkout, so it becomes usable the moment this succeeds and anyone who learns it can redeem it: treat a generated code as live money off. amount_off is read together with offer_type, which defaults to cents, so 100 with the default means one dollar off in USD while 100 with percent means free. Set universal to apply it to EVERY product on the account rather than only this one. Cap the blast radius with max_purchase_count. Gumroad has no idempotency mechanism, so running this node twice creates two records. Guard retries on your side. Requires edit_products or account.

Gumroad: Create Product

Create a product as a DRAFT. It is not visible to buyers until Gumroad: Enable Product publishes it, which makes this the safe half of a two-step publish. native_type is fixed at creation and can never be changed afterwards, so choose it deliberately. Prices are in the smallest unit of the currency, so 100 means one dollar in USD. Covers and thumbnails are attached separately, and files need the four-call upload flow first. Gumroad has no idempotency mechanism, so running this node twice creates two records. Guard retries on your side. Requires edit_products or account.

Gumroad: Create Resource Subscription

Subscribe a URL of yours to one kind of Gumroad event, so Gumroad POSTs to it whenever that event happens. This MANAGES GUMROAD'S OWN WEBHOOKS and is not a Mattering trigger: the endpoint you name has to exist and be reachable before this is useful. Eight resources are supported: sale, refund, dispute, dispute_won, cancellation, subscription_updated, subscription_ended and subscription_restarted. The sale, refund, dispute and dispute_won payloads follow Gumroad's Ping format; the four subscription payloads carry subscription_id, product_id, product_name, user_id, user_email and purchase_ids plus their own fields. Subscribing to sales requires the view_sales scope specifically. Gumroad has no idempotency mechanism, so running this node twice creates two records. Guard retries on your side.

Gumroad: Create Variant

Add one option to a variant category, for example Red inside Colors, or Premium inside Tier. A PUBLICLY VISIBLE change: the option appears in the chooser on the product page immediately and can be bought. price_difference_cents is a DIFFERENCE from the base price, in the smallest currency unit, not an absolute price, so 250 adds 2.50 on top in a currency with minor units. Gumroad has no idempotency mechanism, so running this node twice creates two records. Guard retries on your side. Requires edit_products or account.

Gumroad: Create Variant Category

Create a variant category on a product, which is the group buyers choose from at checkout, for example Colors or Format. The category on its own does nothing until it has options: add those with Gumroad: Create Variant. A PUBLICLY VISIBLE change once options exist, because it adds a chooser to the product page. Gumroad has no idempotency mechanism, so running this node twice creates two records. Guard retries on your side. Requires edit_products or account.

Gumroad: Decrement License Uses Count

Give a seat back on a multi seat license by lowering its uses count by one. This is the deactivate half of a seat management flow: when a customer uninstalls on one machine, call this so they can activate on another without buying more seats. It pairs with the increment that Gumroad: Verify License performs by default.

Gumroad: Delete Custom Field

PERMANENTLY delete a checkout question. It disappears from the product's checkout immediately and Gumroad documents no undelete. Answers already captured on past sales are part of those sale records rather than of this field, so removing the question stops collecting new answers rather than erasing old ones. The field is addressed by its name in the URL and a name with spaces is percent encoded for you. Requires edit_products or account.

Gumroad: Delete Email

PERMANENTLY delete an audience email, draft or published. Gumroad documents no undelete, so the copy is gone. Deleting a published email does not unsend it: the messages already delivered stay in recipients' inboxes, and a published email can also have a public page on the seller's profile, which this removes. Requires edit_emails or account.

Gumroad: Delete Media File

Delete a file from the media library. The file leaves the library immediately and the hosted copy is queued for removal, so ANY PAGE STILL EMBEDDING ITS URL will show a broken image once the purge runs. Because media files are account wide rather than per product, that can be several product pages and the profile at once, and nothing in the API tells you which. Not reversible: restoring means uploading the original again, which produces a new id and a new URL. Requires edit_profile specifically.

Gumroad: Delete Offer Code

PERMANENTLY delete a discount code. The code stops working at checkout immediately, so anyone who has been given it and has not yet redeemed it will be turned away: check times_used against what you expected before running this in a campaign teardown. Gumroad documents no undelete. Requires edit_products or account.

Gumroad: Delete Product

PERMANENTLY delete a product. Gumroad documents no undelete and this API has no restore endpoint, so this is not recoverable from a workflow. Existing buyers, their sales records and their library access are outside what this call promises to preserve, so treat it as an operator action rather than an automated one. If the goal is only to stop selling, use Gumroad: Disable Product, which takes the product off sale and is reversible. Requires edit_products or account.

Gumroad: Delete Product Cover

Remove a cover from a product. A PUBLICLY VISIBLE change that takes effect on the product page immediately, and it is not reversible from this API: Gumroad stores its own copy of the image and deleting the cover discards it, so restoring means adding the original source URL again. The response returns the remaining covers and the new main_cover_id, which is null once the last cover is gone. Requires edit_products.

Gumroad: Delete Product Thumbnail

Remove a product's thumbnail so it falls back to Gumroad's default. A PUBLICLY VISIBLE change, live immediately, and not reversible from this API: the stored image is discarded, so restoring means setting it again from the original source. Requires edit_products.

Gumroad: Delete Resource Subscription

Unsubscribe from a Gumroad event, so it stops POSTing to your endpoint. The events themselves keep happening, they just stop being delivered, and Gumroad does not replay what was missed while a subscription was gone: anything that occurs between this call and a re-subscribe is simply not delivered. Re-subscribing creates a new subscription with a new id.

Gumroad: Delete Variant

PERMANENTLY delete one option from a variant category. A PUBLICLY VISIBLE change: the option disappears from the product page and can no longer be bought. Gumroad documents no undelete, and on a tiered membership the variant IS a tier, so removing one affects the members on it. Requires edit_products or account.

Gumroad: Delete Variant Category

PERMANENTLY delete a variant category. This removes the whole chooser from the product page, and the variants inside it go with it, so this is much larger than deleting one option. Gumroad documents no undelete. On a tiered membership the category IS the tier structure, so removing it changes what existing members are on: do not run this against a live membership from an automation. Requires edit_products or account.

Gumroad: Disable License

Disable a license key. CUSTOMER FACING and immediate: whatever the customer installed stops validating the next time it checks in, so this is how a paying customer's software goes dark. It is the right call for a chargeback or a leaked key and the wrong call to automate on a hunch. Reversible with Gumroad: Enable License, though the customer will have noticed.

Gumroad: Disable Product

Unpublish a product so it stops selling. A PUBLICLY VISIBLE change: the product page stops taking orders and the product leaves the seller's public listing. Nothing is deleted and existing buyers keep what they bought, so this is the reversible way to stop selling something. Reverse it with Gumroad: Enable Product. Requires edit_products or account.

Gumroad: Enable License

Re-enable a license key that was disabled, so the customer's software starts validating again. CUSTOMER FACING in the good direction: whatever they installed begins working the next time it checks in. The reverse of Gumroad: Disable License.

Gumroad: Enable Product

Publish a product so it is on sale and visible to buyers. This is the second half of the create then publish flow, and it is a PUBLICLY VISIBLE change: the product page goes live, the product can appear on the seller's profile, and anyone with the link can buy. Reversible with Gumroad: Disable Product. Requires edit_products or account.

Gumroad: Mark Sale As Shipped

Mark a physical product's sale as shipped, optionally with a tracking URL. This is CUSTOMER FACING: Gumroad tells the buyer their order is on its way and shows them the tracking link, so running it early tells someone their parcel has gone when it has not. There is no documented way to unmark it. Requires the mark_sales_as_shipped scope specifically, which exists so a fulfilment integration does not need refund rights.

Gumroad: Presign File Upload

Step 1 of 4 in attaching a file to a product: start a multipart upload and get back an upload_id, a key, the canonical file_url and one presigned URL per 100 MB part. Step 2 is NOT a Gumroad call and has no node here: PUT each part's raw bytes to its own presigned URL with the generic HTTP node or a worker, and keep the ETag response header from each. Then use Gumroad: Complete File Upload, or Gumroad: Abort File Upload if it goes wrong. The presigned URLs EXPIRE AFTER 900 SECONDS, so a workflow that presigns and then waits on a human will fail. Save the canonical file_url yourself: reading the product back later returns a time limited signed URL instead, and the canonical one cannot be recovered. Maximum file size 20 GB. Requires edit_products.

Gumroad: Preview Email

Send a preview of an audience email to the SELLER'S OWN email address only. No customer or follower receives anything, which makes this the safe way to check rendering before a real send. It does still deliver a real message to the seller's inbox, so a loop over this fills their mailbox. Requires edit_emails or account.

Gumroad: Preview Profile Custom HTML

Run profile HTML through Gumroad's sanitizer and get back the cleaned result and a report of what was stripped, WITHOUT saving anything. Nothing changes on the public profile, which makes this the node to iterate with before publishing. Use it to catch a template whose scripts or attributes will not survive sanitization, rather than discovering that on the live page.

Gumroad: Refund Sale

REFUND A SALE. This moves real money out of the seller's balance back to a real customer's card, the customer is notified by Gumroad, and there is no unrefund endpoint on this API. Treat it as irreversible. Leaving the amount blank refunds the sale IN FULL. The amount, when given, is in the minor units of the SALE'S OWN listed currency, which is the currency field on the sale record and not the buyer's local currency: most currencies have 100 minor units, so 200 means 2.00, but Japanese yen has none, so 200 means 200 yen. Check amount_refundable_in_currency on the sale before calling. Gumroad has no idempotency mechanism, so running this node twice creates two records. Guard retries on your side. A retried run issues a second partial refund. Requires the edit_sales scope specifically.

Gumroad: Resend Sale Receipt

Send the purchase receipt to the customer's email again. This PUTS A REAL EMAIL IN A CUSTOMER'S INBOX, which is usually what you want when someone says they never got their download link, and is not what you want in a loop: there is no throttle here beyond your own. The response is a bare success with no sale object. Requires the edit_sales scope specifically.

Gumroad: Revoke Sale Access

Take the buyer's access away WITHOUT refunding them. The sale stays in the seller's records and the customer keeps being charged nothing back, but they lose their library and download access, so this is customer visible and it is the harsher half of a dispute. Gumroad applies the same rules as its Customers page and REFUSES this for refunded sales, physical products and subscriptions. Reversible with Gumroad: Undo Revoke Sale Access. Requires the edit_sales scope specifically.

Gumroad: Rotate License Key

Issue a new license key and INVALIDATE THE OLD ONE. Gumroad states plainly that the old key will no longer be valid, so everything the customer has already installed with it stops validating and they have to be given the new key, which this node returns and nothing else will tell you again. Use it when a key has leaked; do not use it as a routine hygiene job. There is no way to restore the previous key.

Gumroad: Schedule Email

Schedule a draft audience email to publish at a set time. The time is read in the SELLER'S timezone, not UTC, which is the detail most likely to send a campaign at the wrong hour. Rescheduling an email that is already scheduled just replaces the publish time. Only the timing is fixed here: the audience is resolved at publish time and sending eligibility is re-checked then, so a schedule set today can reach people who joined tomorrow. Reversible with Gumroad: Unschedule Email until it fires. Requires edit_emails or account.

Gumroad: Send Email

PUBLISH A DRAFT AND SEND IT TO ITS AUDIENCE. This reaches real people, potentially every customer and follower the seller has, and there is no recall and no undo. It is marked destructive for that reason rather than because anything is deleted. Preview it first with Gumroad: Preview Email, and confirm the audience on the email record before running this. Gumroad has no idempotency mechanism, so running this node twice creates two records. Guard retries on your side. Requires edit_emails or account.

Gumroad: Set Product Thumbnail

Set the small square image that represents a product in listings, on the profile and in receipts. Supply either a publicly reachable image URL, which Gumroad downloads and stores itself, or a signed blob id from a direct upload. Gumroad enforces the shape: the image must be SQUARE, at least 600 by 600 pixels, under 5 MB, and JPG, PNG or GIF. A PUBLICLY VISIBLE change, live as soon as it is stored. Setting a new thumbnail replaces the old one. Requires edit_products.

Gumroad: Undo Revoke Sale Access

Give a buyer back the access that was revoked, restoring their library and downloads. This is the undo for Gumroad: Revoke Sale Access and is customer visible in the good direction. Requires the edit_sales scope specifically.

Gumroad: Unschedule Email

Cancel a scheduled audience email and turn it back into a draft. The pending publish job is cancelled, so this is the stop button for a campaign that has not gone out yet. It has no effect on an email that already published. Requires edit_emails or account.

Gumroad: Update Custom Field

Edit one of a product's checkout questions. The field is addressed BY ITS CURRENT NAME in the URL, which is why that name is a separate config field from the new name: Gumroad's own example is /custom_fields/phone%20number, so a name with spaces has to be percent encoded, and this connector does that for you. A PUBLICLY VISIBLE change at checkout. Renaming a field changes the key that answers arrive under on future sales, while sales already recorded keep the old key. Requires edit_products or account.

Gumroad: Update Offer Code

Edit an existing discount code. Gumroad only documents changing the coupon text, the redemption cap and the minimum order total here; the discount AMOUNT is not an updatable field, so changing how much a code takes off means deleting it and creating a new one. Raising or removing max_purchase_count immediately allows more redemptions of a code that may already be circulating. Requires edit_products or account.

Gumroad: Update Product

Update a product, sending only the fields you want to change. Three fields are FULL REPLACEMENTS rather than merges: files, tags and rich_content. Any file you leave out is deleted, and an entry sent without a url is dropped along with the file it pointed at, so to keep an existing file you must resubmit its id with its current canonical URL. Setting custom_html publishes a custom landing page that buyers see instead of the default product page, and Gumroad rate limits that to 30 updates a minute per token; the response carries a sanitization_report of what was stripped, a previous_custom_html for one step rollback, and a warning when the page has no buy element. price is rejected for tiered memberships, where tier pricing lives on the variant nodes. Changes are live for buyers immediately. Requires edit_products or account.

Gumroad: Update Profile Custom HTML

Publish or clear the seller's custom profile landing page. This is LIVE IMMEDIATELY on the public profile, so it replaces what visitors see the moment it succeeds. Send an empty value to clear it and fall back to the default profile. Gumroad sanitizes the HTML and returns a sanitization_report of exactly what was stripped, plus previous_custom_html so a bad deploy can be rolled back in one step; only the latest version is stored, with no history beyond that. Preview first with Gumroad: Preview Profile Custom HTML.

Gumroad: Update Refund Policy

Set the account level refund policy that buyers see on every product. A PUBLICLY VISIBLE change with commercial and legal weight: shortening the period changes what customers are entitled to, on every product at once. Gumroad REFUSES this call when the account level policy is not in effect for the seller; in that case set policies per product with the refund_period and refund_fine_print fields on the product write nodes instead. Check in_effect with Gumroad: Get Refund Policy first.

Gumroad: Update Variant

Change one variant's name, price difference or purchase cap. A PUBLICLY VISIBLE change that takes effect on the product page immediately, and a PRICE CHANGE, so treat it with the care you would give any live pricing edit. price_difference_cents is a difference from the base price in the smallest currency unit, not an absolute price. Requires edit_products or account.

Gumroad: Update Variant Category

Rename a variant category. A PUBLICLY VISIBLE change: the label above the chooser on the product page changes immediately. The options inside it are untouched. Requires edit_products or account.

Gumroad: Update Workflow Email

Edit one email step in a workflow without changing whether the workflow is published. Fields you leave out stay as they are, and at least one has to be supplied. Two rules Gumroad enforces: delay_amount and delay_unit must be sent TOGETHER, and CHANGING THE DELAY CAN RESCHEDULE RECIPIENTS who are already partway through the sequence, which is how an edit turns into a send. Abandoned cart workflows accept subject and body changes but not delay changes. Requires edit_emails or account.

Gumroad: Upload Media File

Add an image to the media library, either from a publicly reachable URL that Gumroad downloads for you or from a signed blob id produced by a direct upload. The limits are real and each fails differently: images up to 10 MB, at most 500 files held at once, and at most 20 UPLOADS PER 10 MINUTES, which is the tightest documented rate limit on this API. SVG is refused outright, because these files are served from a Gumroad domain and SVG can carry script. The file type is decided by inspecting the bytes, not by trusting the extension. Suspended or closed accounts cannot upload. Requires edit_profile specifically; an account only token is refused here. Gumroad has no idempotency mechanism, so running this node twice creates two records. Guard retries on your side.

Connecting Gumroad takes one credential

Gumroad issues access tokens from its own account settings rather than from a separate developer portal: open Settings, then Advanced, and use the application form there. You create an application, then generate an access token for your own account from it, which is the credential this connector takes. There is no purchase step and no review queue in front of it, because Gumroad sells no plans and gates nothing here behind billing. One thing to get right before you build: Gumroad's scopes are not a formality. Its reference lists ten of them, account, view_profile, edit_profile, edit_products, edit_emails, view_sales, view_payouts, view_tax_data, mark_sales_as_shipped and edit_sales, and states that account gives full access to most endpoints while endpoints with a narrower security boundary, such as media, refuse an account only token and require the specific scope named on the endpoint. Every node in this connector names the scope its endpoint documents, because a missing scope is the most likely reason a correctly built workflow fails, and it fails as a refusal on a token that looks fully privileged.

1

Sign in to Gumroad, open Settings and then Advanced, and create an application from the form there. Any Gumroad account can do this. There is no plan requirement, because Gumroad has no plans.

2

Generate an access token for your own account from that application, and copy it. This is the single opaque string the connector needs, and it has no expiry and no refresh cycle, so there is nothing to renew on a schedule.

3

Decide which Gumroad account should hold the connection before you generate anything. Every node runs as that seller, so a refund, an audience email or a license rotation is issued in their name and lands in their customers' inboxes.

4

In Mattering Automations, open Connectors, click Add Connector, choose Gumroad, then click Create new credential and paste the access token. It is stored encrypted and never appears in workflow output or logs.

5

Click Test Connection. Mattering calls Gumroad's user endpoint, which takes no parameters and is the cheapest authenticated call on the API. It sends the token both ways, as a bearer header and as a request parameter, which is exactly what every node does, so a pass proves the path the nodes actually take. A rejected token answers a plain HTTP 401.

6

All 81 Gumroad nodes appear in the canvas palette. Run Gumroad: Get User first, then Gumroad: List Products, which is where most Gumroad workflows start and is the source behind every product picker in the connector. A pass here does not prove your scopes are complete, so if a later node is refused on a working credential, check the scope its description names.

Common uses for the Gumroad MCP

A refund queue where a person decides and the workflow does the typing

Gumroad: List Sales pulls a window of purchases with the buyer, the product, the amount and the refund and dispute flags already on the row, so a support inbox or a form can be matched against a real order rather than a customer's description of one. Gumroad: Get Sale then reads the single order in full, including how much is still refundable in its own currency, which is the number to check before anything moves. Keep Gumroad: Refund Sale behind an approval step rather than a condition. There is no unrefund endpoint on this API and no idempotency key, so a retried refund is a second refund, and a blank amount refunds in full rather than doing nothing.

License seat management for software you actually ship

Gumroad: Verify License is the only node on this connector that needs no credential and no application at all, which is what makes it callable from a customer's own machine at install time. Watch its uses count option, which defaults to on, so every plain check burns a seat on a multi seat license and a dashboard poll should turn it off. Gumroad: Decrement License Uses Count gives a seat back when someone uninstalls, and Gumroad: Disable License and Gumroad: Enable License handle suspension and reinstatement. Save Gumroad: Rotate License Key for a leaked key: it invalidates the old one immediately, everything already installed stops validating, and the replacement key appears only in that node's response.

Launch a product without publishing it by accident

Gumroad: Create Product makes a draft rather than a live listing, which makes the whole flow safe to automate: the product is not visible to buyers until Gumroad: Enable Product publishes it. Gumroad: Create Variant Category and Gumroad: Create Variant build the chooser buyers pick from, Gumroad: Set Product Thumbnail and Gumroad: Add Product Cover handle the images, and Gumroad: Create Offer Code sets up the launch discount. Read Gumroad: Update Product carefully before wiring it into anything automated, because its files, tags and rich content fields are full replacements rather than merges, so a partial update wipes what it omits.

An audience email that gets previewed before it gets sent

Gumroad: Create Email creates a draft by default and sends nothing, which is the half worth automating. Gumroad: Preview Email delivers a copy to the seller's own address only, so a person can read the real thing before anyone else does. Gumroad: Schedule Email queues it, and its time is read in the seller's own timezone rather than UTC, which is the detail most likely to send a campaign at the wrong hour. Gumroad: Unschedule Email is the stop button, turning a scheduled campaign back into a draft. Leave Gumroad: Send Email for a human to press, because it reaches the whole audience and there is no recall.

Catalogue and competitor monitoring with no credential at all

Gumroad: Get Public Product Page and Gumroad: Get Public Profile read what a Gumroad page actually shows a visitor, and they need no token, so they work against products you do not own. That makes them the pair for watching a competitor's price, description, variants and rating on a schedule, or for checking that your own live pages say what you think they say after a bulk update. Both are served from the creator's own store domain rather than the API host, so each takes a store domain field: a bare username is expanded for you, and a value with a dot is treated as a full host, so a creator's connected custom domain works. Their responses carry no success flag, being bare objects, so branch on the HTTP status for these two.

Finance reporting that does not silently add currencies together

Gumroad: List Sales windows by date and Gumroad: Get Annual Earnings returns the yearly breakdown that matches Gumroad's own Tax Center, with gross, fees, taxes, affiliate credit and net. Two things keep the numbers honest. Earnings excludes fully refunded sales from every aggregate, so it will not equal a naive sum of the sales list, and that is correct rather than a discrepancy. And every money column on a sale is in the minor units of that row's own currency, so group by the currency column before totalling anything. On the payout side, Gumroad: List Payouts includes the upcoming payout by default and that row carries a null id, so use Gumroad: List Upcoming Payouts when you want the forecast separately and keep it out of anything you store as settled.

Example: A daily sales digest that flags refund candidates without issuing any refunds

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a daily schedule fires. This connector has no trigger nodes, so Gumroad workflows run on a schedule and read rather than listening for a push. Gumroad does have webhooks of its own, and Gumroad: Create Resource Subscription manages them, but it points Gumroad at an endpoint you host rather than creating a Mattering trigger.

2

Gumroad: List Sales reads yesterday's window using the after and before date filters. The response carries a next page key when there is more, and because this API has no page size parameter, the presence of that key is the only signal that the window is incomplete.

3

A branch checks the success flag on the result rather than only the status, because Gumroad can answer HTTP 200 with success set to false and a message explaining the refusal.

4

Rows are grouped by their own currency column before any totalling, and only the quantity column is summed across the whole window, because the money columns are in each row's own minor units and Japanese yen has none.

5

Rows carrying a refund, dispute or chargeback flag are collected into a Mattering data table, and Gumroad: Get Sale reads the amount still refundable in the sale's own currency for each of them.

6

An AI step drafts a short summary of the day and a plain recommendation per flagged order. Nothing has been written to Gumroad at this point and no money has moved.

7

A task is created in Mattering Productivity with the figures and the drafts, so a person approves each refund individually. Gumroad: Refund Sale sits behind that approval rather than in the loop, because there is no unrefund endpoint and no idempotency key on this API.

Gumroad MCP questions, answered

What can this connector actually do in Gumroad?

81 nodes: 33 read and 48 act, covering every operation Gumroad documents on its v2 API. Reads cover products, variant categories and variants, sales, subscribers, product reviews, offer codes, custom checkout fields, audience emails, workflows and their per step statistics, the media library, payouts and upcoming payouts, annual earnings, tax forms and their PDFs, the refund policy, the seller account, license verification, and the two public endpoints that read any creator's product page or profile without a credential. Writes cover creating and updating products, variants, variant categories, offer codes, custom fields, audience emails and workflow steps, publishing and unpublishing products, refunding sales, resending receipts, marking shipped, revoking and restoring access, enabling, disabling, rotating and decrementing licenses, covers and thumbnails, the profile custom HTML, the account refund policy, webhook subscriptions, and the presign, complete and abort steps of the file attachment flow. Not included and worth knowing: uploading the file bytes themselves, which is a direct transfer to storage rather than a Gumroad call and belongs in a generic HTTP node, and trigger nodes, which this connector does not have.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and work with Gumroad through them. Matter, the assistant built into the platform, uses the same nodes natively. The same nodes are also steps on the automation canvas, so a workflow an agent helps you design then runs on a schedule with nobody present. Given what is reachable here, the sensible split is to hand an assistant the 33 read nodes and keep the writes behind a condition or an approval, especially the refund, the audience send and the three license nodes that reach a customer's installed software.

Does Gumroad publish its own MCP server?

No. There is no first-party Gumroad MCP server. What Gumroad does ship for AI use is a command line interface that wraps its API, which it describes as built for humans and AI agents alike, and there is no Model Context Protocol server in its open source codebase or anywhere else it publishes. Community MCP servers for Gumroad exist, written by independent developers rather than by Gumroad, so if you are comparing options that is what you are comparing against. This page is not competing with a vendor server, and a connector is the practical way to put Gumroad behind an MCP-capable assistant today. The argument for doing it here rather than in a local config is the same one that holds when a vendor does ship a server: these nodes also run on a schedule or from another workflow with nobody present, chain with every other connector in one canvas, hold the access token once in a shared workspace store rather than on each person's machine, and carry destructive flags on the fifteen nodes that need them.

Do I need a paid Gumroad plan to use the API?

No, and the reason is worth stating plainly rather than hedging, because it is unusual. Gumroad does not sell subscription plans at all. There is no monthly bill, no Pro tier and no Business tier, so there is no plan for API access to sit behind and no free tier exclusion list to read. Gumroad's published pricing is per transaction and taken only when you sell something: 10 percent plus 50 cents on sales through your own profile and direct links, and 30 percent on sales where a new customer finds you through the Discover marketplace. Creating an application and generating an access token is available to any Gumroad account. One endpoint does not even need that: license verification requires no credential and no application whatsoever.

Which nodes can hurt me, and what exactly do they do?

Fifteen carry a destructive flag. Ten of them delete a product, a variant, a variant category, an offer code, a custom checkout field, an audience email, a media file, a product cover, a product thumbnail or a webhook subscription, and Gumroad documents no undelete for any of them. Two of those are larger than they look: deleting a variant category takes the whole chooser and every option inside it, which on a tiered membership is the tier structure itself, and deleting a media file is account wide, so one delete can break images on several product pages and the profile at once without the API telling you which. The other five delete nothing. Gumroad: Refund Sale moves real money to a real customer with no unrefund endpoint, and a blank amount refunds in full. Gumroad: Send Email reaches the whole audience with no recall. Gumroad: Rotate License Key invalidates the customer's installed key. Gumroad: Disable License stops their software validating. Gumroad: Revoke Sale Access removes a paying customer's access without refunding, though Gumroad: Undo Revoke Sale Access reverses that one. Two more reach a customer without being flagged and say so in their descriptions: resending a receipt and marking a sale as shipped, which tells the buyer their order is on its way.

Why can I not just add up the price column on a list of sales?

Because every money column on a Gumroad sale, price, the Gumroad fee, tax, shipping, tips and variant price, is in the minor units of that row's own currency, and the currency is a column on the row rather than a property of the account. A window of sales can therefore mix currencies. That makes a naive total wrong for the exchange rate, which is obvious, and wrong by a factor of a hundred, which is not: Gumroad documents on its own refund endpoint that Japanese yen has no minor units, so a yen row's 200 is 200 yen while a dollar row's 200 is two dollars. Applying an exchange rate afterwards does not fix the second error, it just hides it. That is why the connector declares only quantity as safely aggregatable on the sales node: it is unitless. Group by the currency column before totalling money, and use Gumroad: Get Annual Earnings when you want a figure that matches what Gumroad itself reports, remembering it excludes fully refunded sales from every aggregate by design.

How does pagination work, and can I control the page size?

It is an opaque cursor and no, you cannot. The paginated listers return a next page key and accept it back on the next call, and there is no page number, no offset and no page size or per page parameter anywhere on the v2 API. So a workflow cannot jump to a page and cannot ask for a larger page, and the presence of a next page key is the only signal that a window is incomplete. Two nodes differ and say so: Gumroad: List Product Subscribers returns everything by default and only paginates when asked, capping at 100 when it does, and Gumroad: List Product Reviews returns up to 100 per page with no way to change it. The connector does not auto-paginate, so each node run is one request and an unbounded walk never hides behind a single canvas step.

What are Gumroad's rate limits, and can I retry safely?

Gumroad documents no global throttle on the v2 seller API, no 429 contract and no retry delay header. Treat that as absent documentation rather than a promise of unlimited calls. What Gumroad does document is per endpoint, and each of those limits is stated on the node it applies to: media uploads are capped per ten minute window with a ceiling on how many files the library holds at once, and the custom HTML endpoints, on products and on the seller profile alike, carry their own per minute caps for saving and for previewing. Retrying is the sharper question, because there is no idempotency mechanism anywhere on this API. Nothing accepts an idempotency key, so a retried create makes a second record, a retried send delivers the campaign twice, and a retried refund issues a second refund. Dedupe on your side rather than relying on a retry policy, and keep the money moving and audience reaching nodes behind an approval.

A node returned HTTP 200 but nothing happened. What is going on?

Check the success flag. Responses from Gumroad's v2 API are enveloped as a success boolean plus the resource, and a rejected request can answer HTTP 200 with success set to false and a message explaining why, so the status alone is not the verdict. The connector reads that flag, marks the node result unsuccessful when it is false whatever the status was, and lifts the message into the result as an error message so a workflow can branch on it directly. Two other causes look similar. A missing scope is the most common: Gumroad states that its account scope covers most endpoints but that narrower ones, media being its own example, refuse an account only token and need the specific scope, so a credential that passed Test Connection can still be refused by one node. And three nodes carry no envelope at all by design, because the two public endpoints return a bare object and the tax form download returns PDF bytes, so those branch on the HTTP status instead.

81 nodes waiting on the canvas

Put Gumroad to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Gumroad is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products