Gumroad + Claude Code
Build a Gumroad reader with Claude Code
Prepare a grounded sales and product briefing
Use Claude Code to build a separate read-only Gumroad assistant with Agent200. Ground the sales and product briefing in returned source data.
On this page
Overview
Use Claude Code to implement a read-only Gumroad reader in your application. Validate identifiers, schemas and access failures before presenting a sales and product briefing.
Start with one identified product. Preserve returned product, sale and subscription fields; report missing data and keep the workflow read-only.
Provider reference: Gumroad API.
- Connector
- Gumroad
- Works with
- Claude Code · Coding agent, with the SDK
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 5 tools
- Model in examples
openai/gpt-5.6-sol
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Gumroad enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Gumroad account. They approve access once, on Gumroad's own page.
- Claude Code in your project. It writes the code with the Agent200 SDK; you review it.
Connect Gumroad to Claude Code
-
1
Step 1: Create your Agent200 API key
Create a key on the API keys page and store it securely.
.envConceptual exampleStore the Agent200 API key as an environment variable # Keep the key out of your code, prompts and chats. export AGENT200_API_KEY="paste-your-key-here" -
2
Step 2: Inspect the real tool definitions
Confirm the actual Gumroad read operations and input schemas in your runtime.
-
3
Step 3: Connect the user’s Gumroad account
Preserve the same stable user identity during authorization and later requests.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Gumroad account, once. const connection = await agent200 .user("user_123") .connect("gumroad"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
4
Step 4: Build and test the read-only answer
Prepare the sales and product briefing only from returned source data. The code example illustrates a sequence, not an SDK installation contract.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "How many sales did the ebook get this month", tools: ["gumroad"], }); console.log(result.output);
Test your connection
Run one request to check everything is wired up.
Ask
Read the Gumroad product I identify and prepare a sales and product briefing. Name the source and use only product, sale and subscription fields. State access gaps; do not change records.
What should come back
- The selected product is identified.
- Only the returned product, sale and subscription fields are reported.
- Access gaps and missing context are explicit; no source data is changed.
Check the selected product ID, account scope, read permission and pagination. Sales and subscription states may change through refunds or cancellation. Use returned dates and statuses; do not equate gross sales with payouts.
Get your API key
Create a key in the Agent200 dashboard. It reaches Gumroad and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Gumroad to Claude Code.
Goal: connect Gumroad to Claude Code with Agent200. Guide: https://www.agent200.com/connectors/gumroad/framework/claude-code/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Make sure Gumroad is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs. 3. Add the Agent200 SDK to the project and create a client with that key. 4. Give every request a stable id for the end user. Agent200 uses only that user's own connections. 5. Connect the user's Gumroad account through Agent200. If Agent200 returns an authorization link, show it to the user and continue once they have approved access on Gumroad. 6. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "gumroad" in the tools. The model decides when a Gumroad tool is needed; Agent200 executes the call. 7. Check it works with this request: "Read the Gumroad product I identify and prepare a sales and product briefing. Name the source and use only product, sale and subscription fields. State access gaps; do not change records." What should come back: - The selected product is identified. - Only the returned product, sale and subscription fields are reported. - Access gaps and missing context are explicit; no source data is changed. 8. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Gumroad, then retry. The code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
The whole guide is also available as Markdown, for agents and LLMs: /connectors/gumroad/framework/claude-code.md
Gumroad tools Claude Code can call
-
List products
Readgumroad_list_productsFind products owned by the authorized seller.
-
Read a product
Readgumroad_get_productRetrieve one identified product.
-
List sales
Readgumroad_list_salesFind sales within an explicit period or product scope.
-
Read a sale
Readgumroad_get_saleRetrieve one identified sale.
-
List subscribers
Readgumroad_list_subscribersFind subscriptions for an identified membership product.
No tool matches that search.
How it works
-
01
Your app sends the request
It calls Agent200 with the model, instructions, the input, the end user's id and the Gumroad tools.
-
02
The model picks a tool
The model decides whether a Gumroad tool is needed, and with which arguments.
-
03
Agent200 runs the call
It uses that user's own Gumroad connection, within the endpoints and scopes your project allows, and returns the result to the model.
-
04
Your app gets the result
Agent200 returns the completed result. Your app decides when the agent runs and what happens next.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Gumroad account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Gumroad enforces what its API grants.
Troubleshooting
The source cannot be read
Check the selected product ID, account scope, read permission and pagination. Sales and subscription states may change through refunds or cancellation. Use returned dates and statuses; do not equate gross sales with payouts.
FAQ
How do I verify this result?
Compare the named product and returned product, sale and subscription fields with the source. Treat missing information as missing, not as a fact.
Is this a native product integration?
This describes a separate application built with Agent200 and Claude Code; it does not install a connector into the Claude Code app.
