List Paddle Subscriptions: 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
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.

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

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