ActionPaddleUpdated September 2026

How do I list Paddle transactions?

Short answer: You can list paddle transactions in Paddle by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Paddle List Paddle Transactions action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Paddle Transactions in Paddle — start free All 6 Paddle actions

List Paddle Transactions in Paddle — 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
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.

Triggered by

Apps that pair well as the trigger for List Paddle Transactions.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Paddle

2 Google Sheets triggers

HubSpot → Paddle

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Paddle returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List Paddle Transactions support batch operations?

Run List Paddle Transactions inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Paddle's rate limits.

More actions