Get Lemon Squeezy Order: Lemon Squeezy action

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
Order ID order_id	string	Required	The Order ID assigned by Lemon Squeezy. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.

Sample request

{
  "order_id": "{{trigger.order_id}}"
}

Returns

{
  "data": {
    "id": "1",
    "attributes": {
      "total": 1000,
      "status": "paid",
      "identifier": "ord_abc",
      "user_email": "jane@x.com"
    }
  }
}

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

FAQ

Questions about Get Lemon Squeezy Order.

What does the Get Lemon Squeezy Order action do in Lemon Squeezy?

Returns an order by ID with line items, customer, tax breakdown, payment status. The standard lookup before downstream provisioning.

What inputs does Get Lemon Squeezy Order require?

Required: Order ID. Every input accepts a static value or a variable from any upstream node in your workflow.

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 Get Lemon Squeezy Order support batch operations?

Yes. Run Get Lemon Squeezy Order inside a Loop node to process arrays. Tiny Command handles Lemon Squeezy's rate limits automatically so you don't have to throttle manually.

More actions