Short answer: You can cancel paddle subscription in Paddle by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Paddle Cancel Paddle Subscription 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 |
|---|---|---|---|
Subscription ID subscription_id | string | Required | The Subscription ID assigned by Paddle. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Effective From effective_from | options | Optional | – |
{"subscription_id": "{{trigger.subscription_id}}","effective_from": "{{trigger.effective_from}}"}
{"data": {"id": "sub_abc","status": "canceled","canceled_at": "2026-05-11T00: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.