Cancel Subscription: Stripe action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Subscription ID subscription_id	string	Required	The subscription to cancel
When to Cancel cancel_at_period_end	options	Optional	Cancel immediately or at the end of the current billing period
Prorate prorate	options	Optional	Generate a proration credit for unused time (immediate cancellation only)

Sample request

{
  "subscription_id": "sub_abc123",
  "cancel_at_period_end": "{{trigger.cancel_at_period_end}}",
  "prorate": "{{trigger.prorate}}"
}

Returns

{
  "id": "sub_abc123",
  "object": "subscription",
  "status": "canceled",
  "canceled_at": 1700000000,
  "current_period_end": 1702592000
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Cancel Subscription.

What does the Cancel Subscription action do in Stripe?

Cancels a Stripe subscription either immediately or at period end (cancel_at_period_end=true). The latter is the default for customer-friendly churn.

What inputs does Cancel Subscription require?

Required: Subscription ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Stripe returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Cancel Subscription support batch operations?

Yes. Run Cancel Subscription inside a Loop node to process arrays. Tiny Command handles Stripe's rate limits automatically so you don't have to throttle manually.

More actions