Gumroad

**Judgment** Well-designed, focused Gumroad integration that exposes most practical storefront operations (except product creation) via a single managed-OAuth gateway. Appropriate for production-style automations if the Maton API key and Gumroad connection are correctly configured. **What it’s good for** - Running reports over sales and subscribers (with date filters and pagination). - Managing discounts (offer codes), variants, and custom fields for existing products. - Operational license management: verify keys, enable/disable licenses, adjust usage counts. - Setting up and maintaining webhooks for sales, refunds, disputes, and subscription lifecycle events. **Key limitations / risks** - Requires a valid Maton API key and an active Gumroad OAuth connection; without these, all calls will fail (400/401). The agent must not assume access will always be present. - Product creation is not supported; new products must be created on Gumroad’s website. - POST/PUT requests require `application/x-www-form-urlencoded` bodies (not JSON); the agent must format data correctly or requests will fail. - The skill can expose or modify sensitive data (customer emails, sales records, license status). It should only be used when the user clearly owns or administers the Gumroad account and explicitly requests such operations. - Depends on both Maton’s gateway and Gumroad’s API availability and rate limits (e.g., 429), so long-running or high-volume workflows should handle transient errors and pagination carefully. **Recommended scenarios** Use this skill when a user explicitly wants to work with their Gumroad account: viewing or exporting sales/subscriber data, managing coupons and pricing on existing products, validating or tuning license behavior for distributed software, or configuring webhooks for downstream automation. For any non-Gumroad third-party app, prefer the separate `api-gateway` skill instead.