Short answer: You can cancel recurly subscription in Recurly by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Recurly Cancel Recurly 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 | Recurly subscription ID or UUID |
{"subscription_id": "{{trigger.subscription_id}}"}
{"id": "sub_xyz789","state": "canceled","expires_at": "2026-05-15T10:00:00Z","canceled_at": "2026-04-15T10: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.