Short answer: Drop the "Chargebee → Cancel Subscription" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Subscription ID subscriptionId | string | Required | Subscription ID |
Cancel at End of Term end_of_term | boolean | Optional | If true, cancels at end of billing period. If false, cancels immediately. |
{"subscriptionId": "{{trigger.subscriptionId}}","end_of_term": "{{trigger.end_of_term}}"}
{"subscription": {"id": "sub_abc","status": "non_renewing","cancelled_at": 1712835600}}
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.
Triggered by anything in the catalog. Free tier available. No credit card.