Recurly
Subscription billing events on Recurly
Recurly is the subscription-billing platform for businesses whose entire revenue model lives on recurring payments, SaaS, streaming, subscription boxes, anything where the dunning logic, proration, and revenue-recognition rules need to be correct or the business breaks. Three triggers cover the high-stakes moments: Subscription Created (a new customer signed up), Subscription Canceled (churn, the moment that needs the most downstream automation), Payment Success (revenue cleared). Six actions cover the operational surface: Create Account, Create Subscription, Get Account, Get Subscription, Cancel Subscription, List Invoices. The integration uses a Recurly API key from your account settings. Common patterns: Subscription Canceled fires a workflow that runs a churn-investigation flow (AI classifies the cancellation reason from a text field, fans to HubSpot as a Closed-Lost reason, and adds the contact to a winback Mailchimp audience), or Payment Success on a high-MRR account triggers a customer-success notification.
Workflows start when Recurly does.
3 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when a payment captures successfully. The revenue-event hook for accounting sync and customer-onboarding workflows in subscription businesses.
Fires when a subscription cancels. For churn-tracking workflows and for revoking subscription access.
Fires on new subscription creation. Payload includes plan, account, trial dates. The base hook for SaaS onboarding workflows.
Do anything Recurly can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Cancel Recurly Subscription | Cancels immediately or at period end. For "customer requested cancel" or for "failed payment after N retries" dunning workflows. |
| Create Recurly Account | Creates a customer account in Recurly (precursor to subscriptions). For "new lead → provision Recurly account before subscription" workflows. |
| Create Recurly Subscription | Provisions a new subscription on an existing account with plan, trial, addons. For "B2B deal closed → provision their subscription from the deal data" workflows. |
| Get Recurly Account | Returns the account with billing info and current subscriptions. The standard lookup for customer-context workflows. |
| Get Recurly Subscription | Returns a subscription with plan, status, billing cycle, next charge date. For renewal-management and access-validation workflows. |
| List Recurly Invoices | Paginated invoices with filters. For accounts-receivable workflows and for sync to accounting systems. |
Pre-built Recurly workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Recurly once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Recurly field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Recurly integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Recurly to Tiny Command?
What Recurly triggers does Tiny Command support?
What Recurly actions can I run from a workflow?
Is the Recurly integration real-time?
Do I need to write code to use Recurly with Tiny Command?
How much does the Recurly integration cost?
More payments apps people connect.
Same category as Recurly, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Recurly.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
