List Paddle Transactions: Paddle 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
Subscription ID subscription_id	string	Optional	Filter by subscription
Status status	options	Optional	Status. Options: All, Completed, Billed, Past Due

Sample request

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

Returns

{
  "data": [
    {
      "id": "txn_123",
      "status": "completed",
      "details": {
        "totals": {
          "total": "9999",
          "currency_code": "USD"
        }
      },
      "customer_id": "ctm_123"
    }
  ]
}

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

FAQ

Questions about List Paddle Transactions.

What does the List Paddle Transactions action do in Paddle?

Paginated transactions with customer, line items, totals, tax breakdown. For revenue-recognition workflows or for sync to accounting systems.

What inputs does List Paddle Transactions require?

List Paddle Transactions 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 Paddle 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 Paddle Transactions support batch operations?

Yes. Run List Paddle Transactions inside a Loop node to process arrays. Tiny Command handles Paddle's rate limits automatically so you don't have to throttle manually.

More actions