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.
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 |
{"status": "{{trigger.status}}","customer_id": "{{trigger.customer_id}}"}
{"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.
Any of these apps can fire this action as part of a workflow.