Short answer: Drop the "Recurly → Recurly Subscription Canceled" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Recurly, not on a polling schedule.
Drop it on the canvas. Configure a couple of fields. Publish.
You don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"plan_code": "monthly_pro","expires_at": "2026-05-15T10:00:00Z","canceled_at": "2026-04-15T10:00:00Z","account_code": "user_123","subscription_uuid": "uuid_xyz789"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| plan_code | string | "monthly_pro" |
| expires_at | string | "2026-05-15T10:00:00Z" |
| canceled_at | string | "2026-04-15T10:00:00Z" |
| account_code | string | "user_123" |
| subscription_uuid | string | "uuid_xyz789" |
One trigger. 6+ downstream actions. Zero glue.