Start free
ActionPaddleUpdated June 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.

FieldTypeRequiredDescription
Subscription ID
subscription_id
stringOptionalFilter by subscription
Status
status
optionsOptionalStatus. 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.

Gmail → Paddle
1 Gmail triggers
Slack → Paddle
13 Slack triggers
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 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. TinyCommand handles Paddle's rate limits automatically so you don't have to throttle manually.
More actions

Other Paddle actions.

Action
Cancel Paddle Subscription
Cancels immediately or at period end. For "customer requested cancel → execute" workflows or for "failed payment after N retries → cancel" dunning workflows.
Action
Create Paddle Customer
Creates a customer record with email, name. For "new B2B customer → provision in Paddle for billing" workflows.
Action
Get Paddle Customer
Returns customer details by ID. The standard lookup for customer-context workflows or for resolving customer IDs to readable identity.
Action
List Paddle Products
Returns the product catalog with pricing variants. Useful for resolving product IDs at workflow setup and for catalog inventory.
Action
List Paddle Subscriptions
Paginated subscriptions with filters. For MRR reporting and for "subscriptions ending this month" renewal-management workflows.
List Paddle Transactions in Paddle — start free