Short answer: You can get subscription in Stripe by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Stripe Get Subscription action to a workflow, map its 1 input 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 | Subscription ID. e.g. "sub_abc123" |
{"subscription_id": "sub_abc123"}
{"id": "sub_abc","status": "active","customer": "cus_abc123","current_period_end": 1702592000,"current_period_start": 1700000000}
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.