---
name: gumroad-browser
description: Drive the Gumroad web UI with browser automation to create products, upload files, configure checkout, and publish. Use when the user says "set up my store," "create a Gumroad product," "upload to Gumroad," or any Gumroad task the API cannot do. Not for post-creation management (offer codes in bulk, sales data, license keys): use gumroad-api.
license: MIT
metadata:
  author: TechTide AI (Alex Cinovoj)
  provenance: original
  category: Sales & RevOps
---

# Gumroad Browser Control

Gumroad's v2 API cannot create products. Creation, file uploads, cover images, and most store configuration happen in the browser or not at all. This skill is the click path for each of those jobs.

## Prerequisites

- User is logged into Gumroad in the active browser session. If not, go to https://gumroad.com/login first.
- The browser agent can reach the tab. Confirm before starting a multi-step flow.

## Task routing

| Task | Path |
|---|---|
| Create a product | Steps below, then references/product-editor.md |
| Upload deliverable files | Product edit page, Content tab |
| Store profile | https://app.gumroad.com/settings/profile |
| Offer code, variants, custom fields | Product edit page, Checkout tab |
| Integrations (Discord, Circle, Drive) | Product Settings, Integrations |
| Webhook for automation | https://app.gumroad.com/settings/advanced, Ping endpoint |
| Anything the API supports | Stop. Use gumroad-api instead. |

## Create a product

1. Navigate to https://app.gumroad.com/products/new.
2. Type the product name.
3. Enter the price in dollars. For pay-what-you-want, toggle PWYW first, then set the minimum.
4. Click "Add a product". You land on the product edit page.
5. Work the edit page tabs in order: Main info, Content, Checkout, Share, Settings. Read references/product-editor.md when you reach this step. It lists every field, tab by tab, with image specs and limits.
6. Click "Preview" and confirm the page reads correctly.
7. Toggle Published. Copy the product URL from the Share tab and report it back.

## Upload files

1. Product edit page, Content tab.
2. Click the upload area, select the file, wait for the progress bar to finish.
3. Bundle multiple files into one ZIP when practical. Buyers see filenames, so name them cleanly.
4. Toggle PDF stamping if the user wants buyer info stamped on PDFs.

## Webhook setup

1. https://app.gumroad.com/settings/advanced, "Ping endpoint" field.
2. Paste the webhook URL (e.g. <AUTOMATION_WEBHOOK_URL>).
3. Click "Send test ping to URL" and confirm the receiving end logged a POST.

## Bulk setup order

Multiple products in one session: profile first (once), then each product fully configured and published before starting the next, webhook last (it is global). Half-configured products across tabs is how fields get missed.

## Verification

After publishing, open the product URL in a fresh tab (not the edit page). Expect: correct name, price, cover, and a working buy button. If the page 404s or shows "not found," the product is still unpublished. Toggle Published in Settings and recheck.

## Completion checklist

- [ ] Name, price, and clean URL slug set
- [ ] Summary and description entered
- [ ] Cover image uploaded (16:9, under 5MB)
- [ ] All deliverable files uploaded and visible in Content
- [ ] Checkout extras configured if requested (fields, codes, variants)
- [ ] Published toggled on, public URL verified in a fresh tab
- [ ] Product URL reported to the user

Any box unchecked: not done. Fix or say so.

## Good vs bad

- Bad: "I filled in the product form and clicked save. Should be live." No preview, no URL check, publish state unknown.
- Good: "Published. Verified https://<STORE>.gumroad.com/l/<SLUG> loads with the $49 price and cover. Offer code LAUNCH tested in an incognito checkout."

## Footguns

- Gumroad redesigns its UI periodically. If a described button is missing, read the accessibility tree for similar labels before declaring failure. Do not guess-click.
- Product invisible on the store page: Published and Discover are separate toggles. Check both, then hit the direct URL.
- Cover looks cropped: use 16:9 (1280x720 or 1600x900) and keep text away from edges. Mobile crops hard.
- Upload appears stuck: large files (limit 16GB) take time. Refresh and re-upload once before escalating.
- Local file upload blocked by the browser sandbox: some browser MCPs refuse local paths in file inputs. See windows-exec for the screenshot-memory upload workaround.