List Etsy Receipts (Orders): Etsy 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
Limit limit	string	Optional	—
Paid? was_paid	options	Optional	—
Shipped? was_shipped	options	Optional	—

Sample request

{
  "limit": "{{trigger.limit}}",
  "was_paid": "{{trigger.was_paid}}",
  "was_shipped": "{{trigger.was_shipped}}"
}

Returns

{
  "count": 50,
  "results": [
    {
      "name": "Jane Doe",
      "was_paid": true,
      "grandtotal": {
        "amount": 2500,
        "divisor": 100,
        "currency_code": "USD"
      },
      "receipt_id": 789,
      "was_shipped": false
    }
  ]
}

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

FAQ

Questions about List Etsy Receipts (Orders).

What does the List Etsy Receipts (Orders) action do in Etsy?

Paginated receipts (orders) with filters by date range and status. Etsy doesn't emit order webhooks, so this is the polling-based pattern for "every 5 min, list new orders and push to fulfilment".

What inputs does List Etsy Receipts (Orders) require?

List Etsy Receipts (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 Etsy 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 Etsy Receipts (Orders) support batch operations?

Yes. Run List Etsy Receipts (Orders) inside a Loop node to process arrays. Tiny Command handles Etsy's rate limits automatically so you don't have to throttle manually.

More actions