List Transactions

paddle.list_transactions
ActionBusiness appsconnection required

Calls the Paddle API with the connection's credentials.

List payments, filtered by customer, subscription, status, invoice number or date.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Paddle
Secret shape
the Paddle API key (pdl_…), or {"api_key": "…"}
Config it needs
environment, base_url
Resolved by
config.connection_id, else node.connection_id

Configuration

14 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
customer_id
Comma-separated customer ids to filter by.
stringNo———
subscription_id
Comma-separated subscription ids to filter by.
stringNo———
status
Only transactions in this state.
stringNo—one of "draft", "ready", "billed", "paid", "completed", "canceled", "past_due"—
invoice_number
Comma-separated Paddle invoice numbers to filter by.
stringNo———
collection_mode
automatic when Paddle charges the card, manual for an invoice.
stringNo—one of "automatic", "manual"—
origin
Comma-separated origins, such as api or subscription_recurring.
stringNo———
billed_at
RFC 3339 filter on billing date; suffix the field with [GTE] or [LT].
stringNo———
created_at
RFC 3339 filter on creation date; suffix with [GTE] or [LT].
stringNo———
updated_at
RFC 3339 filter on last-modified date; suffix with [GTE] or [LT].
stringNo———
include
Related entities to embed, such as customer, address or adjustments.
stringNo———
per_page
How many transactions to return; Paddle caps this endpoint at 30.
numberNo—1–3030
after
Paddle id to continue after — pass the previous run's next_after.
stringNo———
order_by
Sort clause such as id[ASC] or created_at[DESC].
stringNo———
ids
Comma-separated Paddle ids to return only those records.
stringNo———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "per_page": 30
}

Output

One shape.

result

FieldTypeExample
items
The records on this page, exactly as Paddle returned them.
array—
count
How many records are on this page.
number—
next_after
Cursor to pass as 'after' for the next page; empty at the end.
string—
next_url
Paddle's own URI for the next page, or empty at the end.
string—
has_more
True when Paddle has further pages to give.
boolean—
estimated_total
Paddle's estimate of the total matching records.
number—
request_id
Paddle's request id, quoted when contacting their support.
string—
{
  "count": 0,
  "estimated_total": 0,
  "has_more": false,
  "items": [],
  "next_after": "",
  "next_url": "",
  "request_id": ""
}

See List Transactions run in a workflow.

In a technical demo we add the Paddle connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.