Mattering Automations Gumroad integration
Connect Gumroad to Mattering Automations: products and variants, sales and refunds, license keys, offer codes, audience emails and workflows, the media library, payouts, earnings and tax forms as workflow steps, authorized with a Gumroad access token.
The Mattering Automations Gumroad integration puts Gumroad's v2 API on your automation canvas: list and create products and their variants, read sales and refund them, manage license keys, run discount codes and custom checkout questions, draft, preview, schedule and send audience emails, add steps to workflows, keep the media library, and read payouts, annual earnings and tax forms. Eighty one nodes in total, thirty three that read and forty eight that act, covering every operation Gumroad documents.
The credential is a single access token that you generate in your Gumroad account settings. There is no plan to buy first: Gumroad sells no subscription plans at all, charging a per-transaction cut with no monthly fee, so no tier gates API access and any account can create an application and issue itself a token. The decision that carries weight is not the token, it is the scopes on the application behind it, because Gumroad's own reference says the account scope covers most endpoints while narrower ones refuse an account only token.
Three things about this API shape every workflow built on it, and all three are easier to read now than to hit later. Responses from the v2 API are enveloped with a success flag, and a rejected request can answer HTTP 200 with that flag set to false. Pagination is an opaque cursor with no page number and no page size parameter anywhere. And every money column on a sale is in the minor units of that row's own currency, which makes totalling across a mixed currency window wrong in two different ways at once. All three are explained in full below, and this guide ends with the complete node reference.
Before you start
- A Gumroad account. Any account will do. Gumroad has no subscription plans, so there is no tier requirement here and nothing to upgrade. Its published pricing is per transaction and nothing monthly: 10 percent plus 50 cents on sales through your own profile and direct links, and 30 percent when a new customer finds you through the Discover marketplace. API access is not billed at all.
- An application created in the applications area of your Gumroad account settings, and an access token generated from it for your own account. The token is a single opaque string with no expiry and no refresh cycle.
- A decision about which Gumroad account holds the connection. Every node runs as that seller, so a refund is issued from their balance, an audience email arrives from their name, and a rotated license key breaks whatever their customer already installed.
- The right scopes on that application. Gumroad lists ten: account, view_profile, edit_profile, edit_products, edit_emails, view_sales, view_payouts, view_tax_data, mark_sales_as_shipped and edit_sales. Gumroad states that account gives full access to most endpoints, and that endpoints with a narrower security boundary, media being its own cited example, refuse an account only token and require the specific scope named on the endpoint. Every node in this integration names the scope its endpoint documents.
- A separate account to build against, if you intend to exercise the write nodes. The write paths here touch real commerce: a refund moves money to a real person, a published email reaches a real audience, and a rotated license key breaks a customer's installed software. A throwaway Gumroad account with a self-purchase is the honest test environment, since Gumroad documents no sandbox.
- For the tax form and annual earnings nodes, a United States seller with the tax centre enabled. Those endpoints are documented as United States only, so a token that works everywhere else can still find nothing here.
- A Mattering workspace with access to the Automations app.
Create a Gumroad application and access token
Gumroad issues API credentials from your own account settings rather than from a separate developer portal, and there is no review queue, no partner programme and no billing gate in front of it. What you create is an application, and what you paste into Mattering is an access token generated from that application for your own account. The part worth slowing down on is the scopes, because Gumroad fixes what a token can reach at the application, and a scope miss surfaces as a refusal on a credential that otherwise works perfectly.
Connect Gumroad to Mattering
Verify it works
Open any automation canvas and check the palette: a Gumroad section should list the read and action nodes. Drop Gumroad: Get User onto the canvas and run a test step. It is the natural probe because it takes no parameters and answers the question that matters before any write: which seller this connection acts as. Two fields on the response are conditional rather than missing, and knowing that saves a false alarm: the email address appears only for a token holding view_sales, and the profile URL appears only once a username is set.
Now run Gumroad: List Products without changing anything. This is where most Gumroad workflows start and it is the source behind every product picker in the integration, so a populated result is a second confirmation that the credential and the pickers are both fine. Two shape notes while you are here. The url field is documented by Gumroad as deprecated and always null, so read short_url instead. And the sales count and sales total fields appear only when the token holds view_sales or account, so their absence is a scope fact rather than a product with no sales.
Open the product picker on a node such as Gumroad: List Variant Categories and confirm it populates with product names and prices rather than raw ids. The dependent pickers are worth a look too: choosing a product narrows the variant category picker, and choosing both narrows the variant picker. Everything in this verify path is read-only, so it cannot reach a refund, an audience send or any of the ten deletes, and it is safe to re-run whenever you want to check the connection.
Node reference
81 nodes, generated from the connector itself so this reference always matches what ships.
Read and query nodes 33
Gumroad: Download Tax Form
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
gumroad_get_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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
gumroad_list_media
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
gumroad_create_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
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
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
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
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
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
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
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
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
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
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
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
gumroad_delete_media
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
gumroad_rotate_license
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
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
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
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
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
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
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
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
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
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
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
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
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
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
gumroad_upload_media
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.
Using the integration
Scopes, and why a working credential can still be refused
This is the failure mode most likely to cost you an afternoon, so it is worth being exact. Gumroad's reference lists ten scopes: account, view_profile, edit_profile, edit_products, edit_emails, view_sales, view_payouts, view_tax_data, mark_sales_as_shipped and edit_sales. It then says, in its own words, that account gives full access to most API endpoints, and that endpoints with a narrower security boundary, such as media, refuse an account only token and require the specific scope noted on the endpoint. So granting account is not a complete answer, and the failure it produces is a refusal on a token that looks fully privileged, which reads like a broken integration rather than a configuration gap. Every node in this integration names the scope its endpoint documents for exactly this reason. The three media library nodes name view_profile or edit_profile specifically, since those are the ones Gumroad cites as the counter-example. Gumroad: Refund Sale names edit_sales specifically. The payout nodes name view_payouts, the tax and earnings nodes name view_tax_data, and the sales nodes name view_sales. If one node fails on a credential that passes Test Connection, read that node's description first and check the application before you check anything else.
The success flag, and why HTTP 200 is not the verdict
Responses from Gumroad's v2 API are enveloped as a success boolean plus the resource, and the resource key changes per endpoint rather than being a single normalised data field: products, product, sales, sale, offer_codes, variant_categories, custom_fields, media, payout, tax_forms, email, workflows, and for deletes just a message. That is why each node's sample output carries its own endpoint's key. The part that matters operationally is that a rejected request can answer HTTP 200 with success set to false and a message explaining why. The integration reads the body's own flag when there is one, marks the node result unsuccessful whenever it is false regardless of the status, and lifts the message into the result as an error message so a workflow can branch on it without walking into the payload. Bodies with no success key keep the status-derived verdict, and that is correct rather than a fallback: Gumroad: Get Public Product Page and Gumroad: Get Public Profile return a bare object with an api_version and no flag, and Gumroad: Download Tax Form returns PDF bytes. Treating a missing flag as a failure would break those three working nodes.
Pagination is a cursor, and there is no page size to tune
The paginated listers, which are sales, payouts, subscribers, reviews and emails, return a next page key and a next page URL, and accept a page key back on the following call. 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 page seven and cannot ask for five hundred rows. One consequence is worth designing around: because there is no declared page size, a consumer cannot detect a truncated window by comparing a row count against a cap. The only signal is the presence of a next page key in the response, which means the window is incomplete. Two nodes break the pattern and say so on themselves. Gumroad: List Product Subscribers returns everything by default and only paginates when you ask, capping at 100 when it does. Gumroad: List Product Reviews returns up to 100 per page with no way to change it. The integration does not auto-paginate, so each node run is exactly one request and an unbounded walk never hides behind a single canvas step.
Money columns, currencies, and the yen problem
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 is a column on the row rather than a property of the account. A window from Gumroad: List Sales can therefore mix currencies. Totalling the price column across it is wrong for the exchange rate, which everybody expects, and wrong by a factor of a hundred, which nobody notices: Gumroad documents on its own refund endpoint that Japanese yen has no minor units at all, so 200 on a yen row is 200 yen while 200 on a dollar row is two dollars. Applying an exchange rate afterwards does not repair that, it conceals it. This is why the sales node declares only quantity as safely aggregatable. Quantity is unitless, so it is the one column that survives a mixed currency window. The practical habit is to group by the currency column before totalling any money, and to reach for Gumroad: Get Annual Earnings when you want a figure that matches what Gumroad itself reports, remembering that it excludes fully refunded sales from every aggregate by design, so it will not equal a naive sum of the sales list. The same care applies before calling Gumroad: Refund Sale: its amount is in the sale's own listed currency, not the buyer's local currency, so read the refundable amount off the sale with Gumroad: Get Sale first.
There is no idempotency, so retries belong to you
Nothing on this API accepts an idempotency key. There is no mechanism at all, on any endpoint, so the API cannot tell a retry apart from a second intentional call. Retrying a product create makes a second product. Retrying an audience send delivers the campaign twice. Retrying a refund issues a second refund, and there is no unrefund endpoint to undo either one. Every create node in this integration states this in its own description rather than leaving it to a guide nobody reads at the moment it matters. Two design consequences follow. First, dedupe on your side: a Mattering data table keyed on whatever your source system calls unique is the usual answer, checked before the write rather than after it. Second, do not put a money moving or audience reaching node in a path that a retry policy can re-enter. Put an approval step in front of it instead, so a second run needs a person rather than a timeout.
The fifteen destructive nodes, and the two that are not flagged
Ten of the fifteen delete something and Gumroad documents no undelete for any of them: Gumroad: Delete Product, Gumroad: Delete Variant, Gumroad: Delete Variant Category, Gumroad: Delete Offer Code, Gumroad: Delete Custom Field, Gumroad: Delete Email, Gumroad: Delete Media File, Gumroad: Delete Product Cover, Gumroad: Delete Product Thumbnail and Gumroad: Delete Resource Subscription. Two of those are bigger than their names suggest. Deleting a variant category removes the whole chooser and every option inside it, which on a tiered membership is the tier structure itself. Deleting a media file is account wide, so one call can break images on several product pages and the profile at once, and the API does not tell you which. The other five delete nothing and are flagged for what they do to a person. Gumroad: Refund Sale moves real money back to a real customer, who is notified, with no unrefund endpoint. Gumroad: Send Email publishes a draft to its audience, potentially every customer and follower, with no recall. Gumroad: Rotate License Key invalidates the old key, so everything already installed stops validating and the replacement appears only in that node's response. Gumroad: Disable License stops the customer's software validating on its next check-in, reversibly with Gumroad: Enable License but not invisibly. Gumroad: Revoke Sale Access removes a paying customer's library and downloads without refunding them, reversibly with Gumroad: Undo Revoke Sale Access. Two more reach a customer without carrying the flag, and each says so on itself: Gumroad: Resend Sale Receipt puts a real email in a buyer's inbox, and Gumroad: Mark Sale As Shipped tells the buyer their order is on its way and shows them the tracking link, with no documented unmark.
Workflow steps that turn an edit into a send
The two workflow email nodes deserve reading before they are automated, because their risk is not obvious from their names. Gumroad: Add Workflow Email adds a step to an existing workflow without changing whether the workflow is published, and the new step inherits the workflow's state. On a published workflow whose send to past customers option is on, 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. Read the workflow's state and that flag with Gumroad: Get Workflow before adding anything, and note that abandoned cart workflows do not accept added steps at all. Gumroad: Update Workflow Email has the sibling problem: changing the delay can reschedule recipients who are already partway through the sequence, which is how an edit turns into a send. Gumroad also requires the delay amount and delay unit to be sent together. On the campaign side, the safe pattern is Gumroad: Create Email, which creates a draft and sends nothing, then Gumroad: Preview Email, which delivers a copy to the seller's own address only, then a person pressing Gumroad: Send Email or Gumroad: Schedule Email. Scheduling reads its time in the seller's own timezone rather than UTC, which is the detail most likely to send a campaign at the wrong hour, and Gumroad: Unschedule Email turns a scheduled campaign back into a draft.
Attaching a file, and the step that is not a node
Putting a downloadable file on a product is four calls and only three of them are Gumroad's. Gumroad: Presign File Upload starts a multipart upload and returns an upload id, a key, the canonical file URL and one presigned URL per part. Step two is not a Gumroad call and deliberately has no node here: send each part's raw bytes to its own presigned URL with the generic HTTP node or a worker, and keep the ETag from each response. Then Gumroad: Complete File Upload with the ETag list, or Gumroad: Abort File Upload if it went wrong. Finally the canonical file URL is passed to a product create or update. Three details decide whether this works. The presigned URLs expire after 900 seconds, so a workflow that presigns and then waits on a human approval will fail. Save the canonical file URL yourself at step one, because reading the product back later returns a time limited signed URL instead and the canonical one cannot be recovered from a read. And abort has a two state answer where only one is final: accepted means the cancellation was taken but parts in flight may still land, while already gone means there is no such session, so call it again while it says accepted. One more thing about Gumroad: Update Product: its files, tags and rich content fields are full replacements rather than merges, so any file omitted is deleted along with it, and an entry sent without a URL is dropped.
Three nodes that need no credential, and what that is for
Gumroad: Verify License is documented by Gumroad as needing no OAuth application at all, which is what makes license checking possible from a customer's own machine at install time. One option on it is worth setting deliberately: the uses count increment defaults to on, so every plain check burns a seat on a multi seat license, and a dashboard poll or a monitoring workflow should turn it off. Read the refunded, disputed and subscription ended fields alongside the success flag too, because a structurally valid key can belong to a refunded purchase. Gumroad: Get Public Product Page and Gumroad: Get Public Profile are unauthenticated by construction and read exactly what a visitor sees, which means they work against products you do not own and are the catalogue and competitor monitoring pair. 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 with no dot is expanded to that creator's Gumroad subdomain, and a value containing a dot is treated as a full host, so a connected custom domain works. All three are still connector-gated in the palette, so a workspace has to have Gumroad connected to see them. That is a Mattering interface consequence rather than an API one, and it is the answer when somebody asks why a credential-free node needs a connection.
On the automation canvas and from AI assistants over MCP
Gumroad nodes chain with every other node in Mattering. A daily schedule can read Gumroad: List Sales, write the rows into a Mattering data table and open a Productivity task for anything carrying a refund or dispute flag. A form submission can create a discount code with Gumroad: Create Offer Code. A support inbox can look up an order with Gumroad: Get Sale and stop short of refunding it. Every node also speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter, the assistant built into the platform, can drive the same surface. Gumroad publishes no MCP server of its own: its first-party AI-facing tool is a command line interface that wraps the API, which Gumroad describes as built for humans and AI agents alike, rather than a Model Context Protocol server. Community MCP servers for Gumroad exist, written by independent developers rather than by Gumroad. Given what is reachable, the sensible split is to hand an assistant the 33 read nodes and keep the writes behind conditions or approval steps. An agent building a sales digest is low risk; an agent holding Gumroad: Refund Sale or Gumroad: Send Email is not. The advantage of running Gumroad here rather than in a local assistant config is that the same nodes are canvas steps, so a workflow an agent helps you design then runs on a schedule with nobody present, chains with every other connector, and holds the access token once in a shared workspace rather than on each person's machine.
Gumroad's own webhooks are managed here, but they are not triggers
This integration has no trigger nodes, so Gumroad workflows run on a schedule and read rather than listening for a push. What it does have is management of Gumroad's own webhook subscriptions. Gumroad: Create Resource Subscription points Gumroad at a URL you host for one kind of event, Gumroad: List Resource Subscriptions reads them back and Gumroad: Delete Resource Subscription removes one. Eight resources are supported: sale, refund, dispute, dispute won, cancellation, subscription updated, subscription ended and subscription restarted. Two practical notes. The lister requires a resource name, so there is no single call that shows every subscription across all eight, and subscribing to sales requires the view_sales scope specifically. And the endpoint you name has to exist and be reachable before any of this is useful, because these nodes configure delivery rather than receiving it.
Troubleshooting
A node returns HTTP 200 but nothing happened
Test Connection fails with a 401
One node is refused while every other node works
The tax form or annual earnings nodes return nothing or a 404
Totals computed from a sales window do not match Gumroad
A list is missing rows that definitely exist
A workflow ran twice and created two of everything
An audience email went out when nobody meant to send one
A product update wiped files, tags or content that was not being changed
A file upload fails partway through or the presigned URLs stop working
A media library upload is rejected
A picker on a node stays empty
Related
The Gumroad MCP
What connecting Gumroad unlocks for AI agents and automations, with common uses and FAQs.
More guides
All Automations documentation
Every integration guide, plus how connectors, credentials, and workflows fit together.
Gumroad is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.