How to list lemon squeezy orders in Lemon Squeezy

List Lemon Squeezy Orders in Lemon Squeezy — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Store ID storeId	string	Optional	Store ID
Status status	options	Optional	Status. Options: All, Paid, Refunded

Sample request

{
  "storeId": "{{trigger.storeId}}",
  "status": "{{trigger.status}}"
}

Returns

{
  "data": [
    {
      "id": "1",
      "attributes": {
        "total": 999,
        "status": "paid",
        "store_id": 1,
        "created_at": "2026-04-11T10:00:00Z",
        "user_email": "buyer@example.com"
      }
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Lemon Squeezy Orders.

What does the List Lemon Squeezy Orders action do in Lemon Squeezy?

Paginated orders with filters by status, store, date range. For "weekly revenue rollup" or for backfill workflows on missed webhooks.

What inputs does List Lemon Squeezy Orders require?

List Lemon Squeezy Orders has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Lemon Squeezy returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Lemon Squeezy Orders support batch operations?

Yes. Run List Lemon Squeezy Orders inside a Loop node to process arrays. TinyCommand handles Lemon Squeezy's rate limits automatically so you don't have to throttle manually.

More actions