ActionPaddleUpdated September 2026

How do I list Paddle subscriptions?

Short answer: You can list paddle subscriptions in Paddle by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Paddle List Paddle Subscriptions 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 Subscriptions in Paddle — start free All 6 Paddle actions

List Paddle Subscriptions 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
Status status	options	Optional	Status. Options: All, Active, Canceled, Past Due
Customer ID customer_id	string	Optional	Filter by customer

Sample request

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

Returns

{
  "data": [
    {
      "id": "sub_123",
      "status": "active",
      "customer_id": "ctm_123",
      "current_billing_period": {
        "ends_at": "2026-05-01T00:00:00Z",
        "starts_at": "2026-04-01T00:00:00Z"
      }
    }
  ]
}

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

Triggered by

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

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 Subscriptions.

What does the List Paddle Subscriptions action do in Paddle?

Paginated subscriptions with filters. For MRR reporting and for "subscriptions ending this month" renewal-management workflows.

What inputs does List Paddle Subscriptions require?

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

Run List Paddle Subscriptions 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