Cancel Recurly Subscription: Recurly 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	Recurly subscription ID or UUID

Sample request

{
  "subscription_id": "{{trigger.subscription_id}}"
}

Returns

{
  "id": "sub_xyz789",
  "state": "canceled",
  "expires_at": "2026-05-15T10:00:00Z",
  "canceled_at": "2026-04-15T10:00:00Z"
}

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

FAQ

Questions about Cancel Recurly Subscription.

What does the Cancel Recurly Subscription action do in Recurly?

Cancels immediately or at period end. For "customer requested cancel" or for "failed payment after N retries" dunning workflows.

What inputs does Cancel Recurly 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 Recurly 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 Recurly Subscription support batch operations?

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

More actions