---
name: gumroad-weekly-sales
description: "Every Monday: last week's Gumroad revenue after refunds against the week before, with sales by product and any refunds named. Use when the user asks for this, or when it runs on a schedule."
---

# Gumroad weekly sales

Every Monday: last week's Gumroad revenue after refunds against the week before, with sales by product and any refunds named.

Gumroad's dashboard shows sales as they come in and a chart by period, which is fine for a check and awkward for a weekly number you can compare: refunds land on a different day than the sale, and products blur together.

The agent pages through last week's sales from the Gumroad API, groups them by product, subtracts refunds and compares with the week before. Creators and small founders get one revenue number per week and the product behind any change, without opening the dashboard.

## Two ways to get the data

Use the API or MCP route when you have an MCP server, a CLI or an API token for the app. Otherwise, if you can drive a browser the user is signed in to (Claude in Chrome, a Playwright or Chrome DevTools MCP server), use the browser route. Say which one you used.

## Route A: API or MCP server

### What you need

- A Gumroad access token with the `view_sales` scope, created under Settings > Advanced > Applications, in `GUMROAD_ACCESS_TOKEN`.
- Read only: the skill never issues refunds or changes products.

If something is missing, say what and stop; do not invent numbers.

### Steps

1. **Page through last week's sales** (Gumroad): `GET https://api.gumroad.com/v2/sales?after=<last Monday>&before=<this Monday>` (dates as `YYYY-MM-DD`; `after` is inclusive, `before` exclusive). Each page holds 10 sales; pass the returned `page_key` until there is none.
2. **Group by product**: Sum `price` (in cents) per `product_name` and count the sales. Keep sales marked `refunded`, `partially_refunded` or `chargedback` apart.
3. **Subtract refunds**: Revenue after refunds is gross minus refunded amounts. Name each refund with its product and amount, and recheck the previous four weeks for sales refunded since; two refunds of one product in a week is worth a look at its page or file.
4. **Compare with the week before** (Gumroad): Repeat the call for the previous Monday to Sunday and compare revenue, sales count and each product's share.
5. **Report**: Revenue after refunds and the change, sales count, revenue by product, refunds, and the best day.

## Route B: the browser

### What you need

- Signed in to Gumroad as the creator (or a team member with the Marketing or Admin role, which can see sales). The person picks the currency the dashboard displays.

If something is missing, say what and stop; do not invent numbers.

### Steps

Start at https://app.gumroad.com/dashboard/sales. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears.

1. **Set last week on the Sales analytics page**: This is **Analytics** > **Sales** in the sidebar. Set the date range to last Monday through Sunday and read the totals (sales, revenue) and the chart by day for the best day. The table below splits the week by product; copy sales count and revenue per product.
2. **Repeat for the week before**: Move the range back one week and read the same totals and per-product numbers. Analytics shows gross sales, so refunds come from the next step.
3. **List refunds**: Open **Sales** (the customers list at `https://app.gumroad.com/customers`) and use the filters to show purchases from the last five weeks that are refunded or charged back. Note product, amount and the date of the original purchase, and which week each refund belongs to.
4. **Report**: Revenue after refunds last week and the change against the week before, sales count, revenue by product, each refund with product and amount, the best day and one line on the product that moved. If the customers list is long, use **Export** and read the CSV.

Note: The analytics page counts a sale on its purchase date and does not subtract later refunds, so revenue after refunds needs both pages. Discounts and partial refunds appear only on the customers list.

## The report

- **Revenue after refunds** last week, with the change.
- **Sales** count, and revenue by product.
- **Refunds**: product and amount.
- **Best day** of the week.
- One line on the product that moved.

## Post it to Briefkin

When `BRIEFKIN_TOKEN` is set, or `~/.config/briefkin/env` exists (the installer from https://briefkin.dev/docs writes it), also send the result to the user's Briefkin board as one card. Keep the `item_key` the same on every run so the card updates in place, use a new `event_id` per run, and put today's real numbers in place of the example ones. If the request fails, say so once and carry on.

```bash
[ -n "${BRIEFKIN_TOKEN:-}" ] || . ~/.config/briefkin/env
curl -sS -X POST "${BRIEFKIN_URL:-https://briefkin.dev}/v1/events" \
  -H "authorization: Bearer $BRIEFKIN_TOKEN" \
  -H "content-type: application/json" \
  -d @- <<'JSON'
{
  "v": 1,
  "event_id": "gumroad-weekly-sales/<date of this run, e.g. 2026-10-16>",
  "item_key": "gumroad-weekly-sales",
  "project": "Acme Studio",
  "source": "Gumroad weekly sales skill",
  "kind": "metric",
  "title": "$2,828 in Gumroad sales last week, up 9%",
  "metric": {
    "label": "Revenue after refunds, last week",
    "value": 2828,
    "prefix": "$",
    "better": "higher",
    "period_start": "<start of the period, ISO 8601>",
    "period_end": "<end of the period, ISO 8601>"
  },
  "glance": [
    {
      "type": "Grid",
      "props": {
        "columns": 3
      },
      "children": [
        {
          "type": "Stat",
          "props": {
            "label": "Sales",
            "value": 94
          }
        },
        {
          "type": "Stat",
          "props": {
            "label": "Refunds",
            "value": 58,
            "prefix": "$",
            "better": "lower"
          }
        },
        {
          "type": "Stat",
          "props": {
            "label": "Top product",
            "value": "Finance template"
          }
        }
      ]
    }
  ],
  "widget": [
    {
      "type": "Table",
      "props": {
        "columns": [
          "Product",
          "Sales",
          "Revenue"
        ],
        "align": [
          "left",
          "right",
          "right"
        ],
        "rows": [
          [
            "Notion finance template",
            48,
            "$1,392"
          ],
          [
            "Icon pack pro",
            21,
            "$819"
          ],
          [
            "Course: ship your side project",
            5,
            "$495"
          ],
          [
            "Lightroom presets",
            20,
            "$180"
          ],
          [
            "Refunds (2, finance template)",
            "",
            "-$58"
          ]
        ]
      }
    },
    {
      "type": "Callout",
      "props": {
        "text": "The finance template sold 48 copies, 15 more than the week before, most on Thursday after the newsletter mention.",
        "tone": "ok"
      }
    }
  ],
  "size": "md"
}
JSON
```

Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report.

Set `period_start` and `period_end` to the window the number covers: the tile names it from them ("Last 7 days", "Today", "This month"). For a count right now (open items, a balance), send `"period_label": ""` so no period shows; for another name, send it as `period_label` (at most 24 characters).

## Run it on a schedule

Suggested: Mondays at 8:00 (`0 8 * * 1`). From cron, with the agent signed in on that machine:

```bash
0 8 * * 1 claude -p "Run the gumroad-weekly-sales skill"
# Codex: codex exec, Gemini CLI: gemini -p, Copilot CLI: copilot -p, OpenCode: opencode run
```

Or use the agent's own scheduler (Claude Code routines, Codex automations, Claude or ChatGPT scheduled tasks): https://briefkin.dev/skills/gumroad-weekly-sales#schedule

Source: https://briefkin.dev/skills/gumroad-weekly-sales
