Short answer: You can cancel subscription in Stripe by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Stripe Cancel Subscription action to a workflow, map its 3 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 to cancel |
When to Cancel cancel_at_period_end | options | Optional | Cancel immediately or at the end of the current billing period |
Prorate prorate | options | Optional | Generate a proration credit for unused time (immediate cancellation only) |
{"subscription_id": "sub_abc123","cancel_at_period_end": "{{trigger.cancel_at_period_end}}","prorate": "{{trigger.prorate}}"}
{"id": "sub_abc123","object": "subscription","status": "canceled","canceled_at": 1700000000,"current_period_end": 1702592000}
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.