Automate Your Gumroad Product Catalog

Building a large catalog of digital products by hand in Gumroad's web interface is slow and easy to get wrong. This skill batch-creates products straight from a CSV, attaches their files, sets covers, and finishes the steps the API can't reach, so a full catalog goes up in one structured run instead of an afternoon of copy-paste.

What it does

• Batch Product Creation: Creates multiple Gumroad products from a standardized CSV, each starting safely as a draft so nothing goes live before you review it.
• File Upload and Content-Tab Attachment: Uploads local ZIP files and attaches them to each product, including the Gumroad Content tab through a Playwright browser phase the API alone can't handle.
• Cover Images: Adds covers from an image URL, or hands off to the Product Image Creator skill when you need one generated.
• Duplicate Detection: Checks each custom permalink against your existing products before creating, so re-running a batch updates instead of duplicating.
• Rate-Limit Resume: Saves progress after every row and, if Gumroad throttles the run, picks up exactly where it left off with --resume instead of starting over.
• Smart Validation: Pre-checks CSV structure, price formatting, and file existence before any API call, so errors surface before they cost you.
• Failure Resilience: Keeps processing even if individual rows fail, then returns a Markdown summary table of every create, update, skip, and error.

Supported Tools

The skill includes a dedicated Python script (batch_upload.py) for the Gumroad API, plus an optional Playwright phase for Content-tab attachment. The expanded v2 CSV schema covers name, price_cents, description, tags, custom_permalink, file_path, cover_image_path, cover_image_url, file_display_name, and file_description.

Why use this skill?

Instead of prompting an AI to "try" to use an API, this skill runs a structured, throttled, two-phase workflow: the Gumroad API for product creation and file upload, then a Playwright browser pass to finish the Content tab. It handles rate limiting by saving progress and resuming, detects duplicates before creating, keeps every product as a draft until you approve it, and ends with a clean Markdown summary of the whole run.