Resources · Make integration

Recurly Make integrationAutomate Recurly with Make.

New subscribers and payments in Recurly can start work in your other tools on their own. The Recurly Make integration offers 4 modules: 2 triggers and 2 actions. This guide covers the connection, a first scenario and every module, for billing and ops teams.

Try the Recurly integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Recurly Make integration let you automate?

The Recurly Make integration links your Recurly subscription account to Make, a visual tool where you chain apps together without writing code. Make can spot new customer accounts and new transactions in Recurly, create accounts for you, and reach any other part of the Recurly API through one generic module.

Welcome every new subscriber. Watch Accounts picks up each customer account created in Recurly, so the next module can add that person to your mailing tool or post a note for the sales team. Nobody has to copy the contact by hand anymore.

Keep finance in the loop. Watch Transactions reports each new transaction. Send it to a spreadsheet or a shared channel and your accountant sees payments without logging in to Recurly.

Open the account where the deal closes. When a customer signs up somewhere else, a form or a CRM, Create an Account builds the matching customer account in Recurly, ready for billing.

Know the edges before you start. Both triggers are scheduled: Make checks Recurly on the scenario's schedule, so a change shows up at the next check, not the second it happens. The list holds no search, update or delete module, so anything beyond account creation goes through Make an API Call. The Make documentation for Recurly also warns that it is AI-generated and may contain mistakes, so verify important details with Recurly directly.

Recurly may have an n8n node as well; the n8n vs Make page sets the two tools side by side. To get comfortable with the editor first, see the Make training, and check Make pricing before you plan several scenarios.

Connect

How do you connect Recurly to Make?

  1. 01

    Create a private API key in Recurly

    In Recurly, open Integrations > API Credentials and click Add Private API Key at the bottom of the page. Give the key a name and a purpose, say it is for Make, click Save Changes, then copy the key shown on screen.

  2. 02

    Add a Recurly module in Make

    In your scenario, add any Recurly module and click Create a connection. A connection is your Recurly account linked to Make once, then reused by every Recurly module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and save

    Paste the API key you copied from Recurly into the connection window, or follow the instructions Make shows on screen, and confirm. From now on the module can read your Recurly data and list what it needs as you fill it in.

First scenario

Your first scenario with Recurly

GoalWhen a new customer signs up in another tool, Make creates the matching customer account in Recurly.

  1. 01

    Create the scenario

    Open the Scenarios page and create a new scenario. A scenario is the automation you build: a chain of modules. Click the large + to place the first module.

  2. 02

    Pick where sign-ups come from

    Choose the trigger of the app where new customers first appear, such as your form tool or CRM, and connect it. Every new sign-up will travel through the scenario as one bundle, meaning one item passed from module to module.

  3. 03

    Add Create an Account

    Click the + on the right of the first module, search for Recurly and pick Create an Account. Select the Recurly connection you made earlier, or click Create a connection if this is your first Recurly module.

  4. 04

    Map the customer details

    Fill the fields of Create an Account by clicking into each one and choosing the matching value from the first module. Make shows what the previous module returned, so there is nothing to type from memory.

  5. 05

    Test with Run once

    Click Run once, then create a test sign-up in your source app. Open the bubble above each module to read the bundles it received, and check in Recurly that the new customer account is there.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set the schedule, which is every 15 minutes by default for a new scenario. Then switch the scenario on. Each module run counts as one operation on your Make plan.

Triggers

What can start a Recurly scenario?

2 modules start a scenario when something happens in Recurly. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Recurly as soon as it happens.

Recurly1Watch Accounts

Watch Accounts

Scheduled trigger

In Make“Triggers when a new customer account is created.”

Get a heads-up for every new customer account in Recurly, delivered as one bundle per account to the rest of your scenario. It is the natural starting point for onboarding work that follows a sign-up.

How it fires
scheduled. Make checks Recurly on the scenario's schedule and picks up the accounts created since its last look, so they arrive in batches rather than one by one as they happen.
When to use it
a new subscriber should land in your mailing list, your CRM or a team channel without anyone copying details across.
Watch out
it only reacts to account creation, so changes made to an existing account will not start the scenario.
Recurly2Watch Transactions

Watch Transactions

Scheduled trigger

In Make“Triggers when a new transaction is created.”

Receive each new Recurly transaction as a bundle and send it wherever money gets tracked. Finance sees fresh activity in the tools it already uses, without a Recurly login.

How it fires
scheduled. On every run of the scenario, Make asks Recurly for transactions created since the previous run and passes them on one bundle at a time.
When to use it
you log payments in a spreadsheet, alert a shared channel when money comes in, or feed an accounting tool that needs each transaction.
Watch out
each transaction that comes through runs the next modules once, so every module after the trigger consumes operations on your plan for each one.
Modules

What can Make do in Recurly?

Recurly gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Recurly1

Create an Account

Action

In Make“Creates a new customer account.”

Open a new customer account in Recurly straight from another app, with the details mapped from the earlier modules. The customer is ready to bill the moment the scenario runs, without a manual entry in Recurly.

When to use it
a deal is marked won in your CRM or a sign-up form comes in, and the customer needs a Recurly account next.
Watch out
avoid pairing it with Watch Accounts in the same scenario, or each new account will trigger the creation of another.
Recurly2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any endpoint of the Recurly API from your scenario, reusing the connection you already set up. This is how you cover everything the other three modules leave out, such as reading or changing existing records.

When to use it
you need a Recurly operation that has no dedicated module, and you know which endpoint handles it.
Watch out
you write the request yourself, so keep the Recurly API documentation open and check the result with Run once before you switch the scenario on.
Need help

Need help automating Recurly with Make?

A person reads every message.

FAQ

Questions about Recurly and Make

01Is the Recurly Make integration free?
Yes, Recurly is a standard app in Make, so it works from the Free plan. That plan has its own limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of run time at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in operations per month. Your Recurly subscription is separate and billed by Recurly.
02What do you need to connect Recurly to Make?
You need an active Recurly account and a private API key. In Recurly, go to Integrations, then API Credentials, click Add Private API Key, give it a name and a purpose, save the changes and copy the key shown on screen. Then, in Make, add any Recurly module, click Create a connection, optionally name it, and paste the key. That one connection serves every Recurly module in all your scenarios afterwards.
03Do the Recurly triggers in Make fire instantly?
No. Watch Accounts and Watch Transactions are both scheduled triggers: Make checks Recurly on the scenario's schedule and collects what appeared since the last check. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval allowed, while paid plans go down to 1 minute. Need a faster reaction? Shorten the schedule on the first module, which on the Free plan means moving to a paid plan first.
04What if the Recurly module you need is missing in Make?
Use Make an API Call. It sends any request to the Recurly API with the connection you already have, which covers what the listed modules do not, for example reading or updating existing records. You write the request yourself, so keep the Recurly API reference nearby and test with Run once. Also note that the Make documentation for Recurly is flagged as AI-generated, so confirm important behavior with Recurly directly.
05Should you use Make or n8n for Recurly?
It depends on the tool your team already runs. In Make, Recurly offers two scheduled triggers, one action to create accounts and Make an API Call for the rest, all available from the Free plan and set up through the visual editor. Many apps also exist as an n8n node, so compare what each tool offers for Recurly against your own scenarios. The n8n vs Make comparison on this site lays out criteria to help you choose.
Same platform

Other docs you might need on this stack.

Browse all integrations