Short answer: Drop the "Zoho Billing → 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 |
|---|---|---|---|
Organization ID organization_id | string | Required | Organization ID. Example: 10234695 |
Customer ID customer_id | string | Required | Customer ID. Example: 903000000000099 |
Plan Code plan_code | string | Required | Plan Code. Example: basic-monthly |
Start Date starts_at | string | Optional | Leave empty for today |
Auto Collect Payment auto_collect | options | Optional | Auto Collect Payment. Options: No, Yes |
{"organization_id": "e.g. 10234695","customer_id": "e.g. 903000000000099","plan_code": "e.g. basic-monthly","starts_at": "YYYY-MM-DD","auto_collect": "{{trigger.auto_collect}}"}
{"code": 0,"message": "Subscription created","subscription": {"plan": {"name": "Basic","plan_code": "basic-monthly"},"status": "live","subscription_id": "sub001"}}
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.