Short answer: Drop the "Recurly → Create Recurly 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 |
|---|---|---|---|
Account Code account_code | string | Required | Account code to subscribe (your customer identifier) |
Plan Code plan_code | string | Required | Recurly plan code (e.g. monthly_pro) |
Currency currency | string | Optional | ISO 4217 currency code |
{"account_code": "{{trigger.account_code}}","plan_code": "{{trigger.plan_code}}","currency": "USD"}
{"id": "sub_xyz789","plan": {"code": "monthly_pro","name": "Monthly Pro"},"uuid": "uuid_xyz789","state": "active","currency": "USD","unit_amount": 49,"current_period_ends_at": "2026-05-15T10:00:00Z","current_period_started_at": "2026-04-15T10:00:00Z"}
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.