Short answer: Drop the "Chargebee → List Subscriptions" 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 |
|---|---|---|---|
Status status | options | Optional | Status. Options: All, Active, Cancelled, Non-renewing |
Limit limit | number | Optional | Limit |
{"status": "{{trigger.status}}","limit": "{{trigger.limit}}"}
{"list": [{"subscription": {"id": "sub_abc","status": "active","plan_id": "basic","customer_id": "cus_abc"}}]}
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.