Short answer: Drop the "Chargebee → Create 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 |
|---|---|---|---|
Plan ID plan_id | string | Required | Plan ID |
Customer Email customer_email | Required | The email address. Used as the recipient or identifier depending on context. | |
First Name customer_first_name | string | Optional | First Name |
Last Name customer_last_name | string | Optional | Last Name |
{"plan_id": "{{trigger.plan_id}}","customer_email": "e.g. user@example.com","customer_first_name": "{{trigger.customer_first_name}}","customer_last_name": "{{trigger.customer_last_name}}"}
{"subscription": {"id": "sub_abc123","status": "active","plan_id": "basic-monthly","customer_id": "cus_abc123"}}
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.