Gumroad MCP integration for AI agents.

Connect AI agents to Gumroad through 9 structured actions, including get current user, refund sale, and mark sale as shipped. Review authentication, inputs…

ACTION CONTRACTS
9
AUTHENTICATION
API key
SOURCE STATUS
Provider-backed

CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE

CAPABILITY PROFILE

What the Gumroad integration exposes

The Gumroad Agent App exposes 9 provider-backed actions for finance and marketing work. Its current contract lets an authorized agent retrieve the authenticated gumroad user, refund a gumroad sale, optionally as a partial refund in cents, and mark a gumroad sale as shipped, optionally including a tracking url. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.

A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.

For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Gumroad account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.

VERIFIED ACTION SAMPLE

Real Gumroad capabilities.

Showing 9 of 9 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.

get_current_userREAD

Retrieve the authenticated Gumroad user.

refund_saleHIGH IMPACT

Refund a Gumroad sale, optionally as a partial refund in cents.

INPUTS: saleId / amountCents

mark_sale_as_shippedREVIEW

Mark a Gumroad sale as shipped, optionally including a tracking URL.

INPUTS: saleId / trackingUrl

get_productREAD

Retrieve one Gumroad product by ID.

INPUTS: productId

get_saleREAD

Retrieve one Gumroad sale by ID.

INPUTS: saleId

list_product_subscribersREAD

List active subscribers for one Gumroad product.

INPUTS: productId / email / paginated / pageKey

list_productsREAD

List products owned by the authenticated Gumroad user.

list_salesREAD

List successful Gumroad sales with optional filters and pagination.

INPUTS: after / before / productId / email / orderId

resend_sale_receiptREVIEW

Resend a Gumroad sale receipt to the buyer.

INPUTS: saleId

INPUT CONTRACTS

Know what the action needs before it runs.

refund_sale

saleIdREQUIRED
Gumroad resource ID.
amountCentsOPTIONAL
Partial refund amount in the sale currency's smallest unit.

mark_sale_as_shipped

saleIdREQUIRED
Gumroad resource ID.
trackingUrlOPTIONAL
Tracking URL to attach to the shipment.

get_product

productIdREQUIRED
Gumroad resource ID.

get_sale

saleIdREQUIRED
Gumroad resource ID.

PROVIDER-SPECIFIC WORKFLOWS

Jobs this Agent App can support

Inspect Get Current User

Retrieve the authenticated Gumroad user. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.

get_current_user

Control Refund Sale

Refund a Gumroad sale, optionally as a partial refund in cents. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.

refund_sale

Verify with Get Product

Retrieve one Gumroad product by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.

get_product

SAFETY BOUNDARY

Operate Gumroad with explicit limits

  • Authorize Gumroad with API key and grant only the provider access required by the selected actions.
  • 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
  • Treat `refund_sale` as high-impact operations and require an explicit approval boundary.
  • No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Gumroad rather than assuming unrestricted access.
  • After a call, inspect the structured result and execution record before reporting that the Gumroad task completed successfully.

CONNECTION MODEL

API key

Gumroad access token passed as the access_token parameter. Generate it from the official Gumroad API page while signed in: https://gumroad.com/api.

Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.

READ SIGNALS
6
WRITE SIGNALS
0
HIGH IMPACT
1
REVIEW SIGNALS
2

EVIDENCE AND AVAILABILITY

Provider reference

Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Gumroad.

Official Gumroad website

ONE CONNECTION. REAL WORK.

Give your agent software it can use.

Connect through MCP or explore the Agent App catalog and choose only the capabilities your workflow needs.

EXPLORE AGENT APPS