Oo Gumroad

Gumroad

Operate Gumroad through your OOMOL-connected account. This skill calls the gumroad connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Gumroad. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "gumroad" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "gumroad" --action "<action_name>" --data '<json>' --json

• --data takes a JSON object string or @path/to/file.json; omit it to send {}.
• The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

• get_current_user — Retrieve the authenticated Gumroad user.
• get_product — Retrieve one Gumroad product by ID.
• get_sale — Retrieve one Gumroad sale by ID.
• list_product_subscribers — List active subscribers for one Gumroad product.
• list_products — List products owned by the authenticated Gumroad user.
• list_sales — List successful Gumroad sales with optional filters and pagination.
• mark_sale_as_shipped — Mark a Gumroad sale as shipped, optionally including a tracking URL. [write]
• refund_sale — Refund a Gumroad sale, optionally as a partial refund in cents.
• resend_sale_receipt — Resend a Gumroad sale receipt to the buyer.

Safety

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change Gumroad state — confirm the exact payload and effect with the user before running.
• Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

• oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  

• Not signed in / authentication error — sign in to your OOMOL account once:

  oo auth login
  

• scope_missing / credential_expired / app_not_ready / app_not_found — Gumroad is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

  https://console.oomol.com/app-connections?provider=gumroad
  

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• Gumroad homepage: https://gumroad.com