Lemon Squeezy

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

Category: Productivity, Finance. Exposes 16 action(s).

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Lemon Squeezy. 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 "lemon_squeezy" --action "\x3Caction_name>"

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

oo connector run "lemon_squeezy" --action "\x3Caction_name>" --data '\x3Cjson>' --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 below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with oo connector schema before constructing --data.

Available actions

• create_customer — Create a Lemon Squeezy customer for the specified store.
• create_webhook — Create a Lemon Squeezy webhook for the specified store.
• delete_webhook — Delete a Lemon Squeezy webhook by ID. The returned acknowledgement is generated by the connector because Lemon Squeezy responds with 204 No Content.
• list_customers — List Lemon Squeezy customers with optional store or email filtering.
• list_orders — List Lemon Squeezy orders with optional store, email, or order-number filtering.
• list_products — List Lemon Squeezy products with optional store filtering and pagination.
• list_stores — List stores that belong to the authenticated Lemon Squeezy account.
• list_subscriptions — List Lemon Squeezy subscriptions with optional filters and pagination.
• list_variants — List Lemon Squeezy variants with optional product filtering and pagination.
• list_webhooks — List Lemon Squeezy webhooks with optional store filtering and pagination.
• retrieve_authenticated_user — Retrieve the currently authenticated Lemon Squeezy user.
• retrieve_customer — Retrieve a single Lemon Squeezy customer by ID.
• retrieve_store — Retrieve a single Lemon Squeezy store by ID.
• retrieve_webhook — Retrieve a single Lemon Squeezy webhook by ID.
• update_customer — Update a Lemon Squeezy customer by ID.
• update_webhook — Update a Lemon Squeezy webhook by ID.

Safety

• Read actions (get / list / search) are safe to run directly.
• Create, update, send, or post actions change Lemon Squeezy state — confirm the exact payload and effect with the user before running.
• Delete or remove actions are destructive — 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: \x3Chttps://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 — Lemon Squeezy 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=lemon_squeezy
  

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

Resources

• Lemon Squeezy homepage: https://www.lemonsqueezy.com