Short answer: Drop the "Stripe → 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 |
|---|---|---|---|
Customer ID customer | string | Required | The Stripe customer ID (must have a payment method attached) |
Price ID price | string | Required | Stripe Price ID — starts with 'price_'. |
Trial Period (days) trial_period_days | string | Optional | Number of trial days before charging. Leave empty for no trial. |
Cancel at Period End cancel_at_period_end | options | Optional | Whether to cancel the subscription at the end of the current billing period |
{"customer": "cus_abc123","price": "price_abc123","trial_period_days": "e.g. 14","cancel_at_period_end": "{{trigger.cancel_at_period_end}}"}
{"id": "sub_abc123","items": {"data": [{"id": "si_abc","price": {"id": "price_abc123","currency": "usd","unit_amount": 1999}}]},"object": "subscription","status": "active","customer": "cus_abc123","current_period_end": 1702592000,"current_period_start": 1700000000}
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.