Resources · Make integration

ReCharge Make integrationAutomate ReCharge with Make.

What if every failed charge or new subscriber reached the right person on its own? The ReCharge Make integration offers 89 modules, 30 of them instant triggers. This guide is for subscription stores: connect your account, build a first scenario, then pick the modules you need.

Try the ReCharge integration on MakeSee the 89 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ReCharge Make integration do for your store?

The ReCharge Make integration links your subscription store to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, reads or changes something. ReCharge tells Make when a charge, order or subscription moves, and Make carries the news to your other tools.

Rescue failed payments. Watch Charge Failed starts the scenario as soon as a renewal bounces, Get a Customer adds the subscriber's details, and your helpdesk or email tool takes it from there. Watch Charge Maximum Retries Reached covers the last warning.

Keep fulfillment in step. Watch Order Created, Watch Order Cancelled and Change an Order Date keep a warehouse sheet or a logistics partner aligned with what customers change in ReCharge.

Run offers from your other tools. Create a Discount followed by Add a Discount to a Charge turns a survey answer or a CRM tag into a real reduction on the next payment, and Skip a Charge answers a pause request without opening ReCharge.

A few limits are worth knowing. Validate an Address only works for USA addresses, and Make's own documentation for this app is flagged as AI-generated from ReCharge's docs, so verify anything critical in ReCharge. When a need goes beyond the modules, Make an API Call reaches the rest of the API.

Wondering whether n8n would suit you better? The n8n vs Make comparison lays out the criteria. For the tool itself, read the Make review, and if a scenario misbehaves, the Make troubleshooting guide is the place to start.

Connect

How do you connect ReCharge to Make?

  1. 01

    Generate an API token in ReCharge

    In ReCharge, open Tools & apps, then API tokens, and click Create an API Token. Give it a name and a contact email, choose the scope permissions, click Save and copy the token shown on screen.

  2. 02

    Add a ReCharge module in Make

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

  3. 03

    Paste the token and save

    Paste the token you copied into the credentials field, or follow the on-screen instructions, and confirm. Make can now read and change your ReCharge data within the permissions you selected for the token.

First scenario

Your first scenario: alert support when a charge fails

GoalWhen a charge fails in ReCharge, Make fetches the customer so your team can follow up.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario. An empty canvas opens with a big + in the middle: click it to add the first module, the one that starts everything.

  2. 02

    Add the failed charge trigger

    Search for ReCharge, pick Watch Charge Failed, click Create a webhook, then create or select your connection. The lightning badge on the module confirms it is an instant trigger.

  3. 03

    Fetch the customer

    Click the + on the right of the trigger, add Get a Customer, and map the customer from the data the trigger brought in. Make shows that data in a panel, so you click it instead of typing it.

  4. 04

    Test with Run once

    Click Run once, then produce a failed charge in a test setup. Open the bubbles to read each bundle, the item that passed from one module to the next.

  5. 05

    Add your alert and switch it on

    Add the module of your helpdesk or email app after Get a Customer, run one more test, then switch the scenario on. From then on, ReCharge calls it by webhook as soon as a charge fails.

Triggers

Which ReCharge events can start a scenario?

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

ReCharge1Watch Address Created

Watch Address Created

Instant trigger

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

Every new address saved in ReCharge lands in your scenario as a bundle (one item passed from module to module), ready to copy into a shipping sheet or a CRM.

How it fires
Instant. ReCharge calls Make through a webhook as soon as it happens, so there is no polling interval to set.
When to use it
A shop that prepares its own parcels wants each fresh delivery address checked before the first box leaves.
Watch out
The first time you add it, click Create a webhook before Create a connection, otherwise the module has nothing to listen to.
ReCharge2Watch Address Updated

Watch Address Updated

Instant trigger

In Make“Triggers when an existing address is updated.”

Your scenario starts whenever a subscriber changes an existing address, so the new details can reach your warehouse tool before the next shipment is packed.

How it fires
Instant: the lightning badge on the module means ReCharge pushes the event to Make by webhook the moment it occurs.
When to use it
Customers who move often edit their address in the portal, and your logistics partner needs the updated version without anyone retyping it.
Watch out
Each edit counts as one event and each module run on it uses one operation (one execution, what Make counts on your plan), so busy stores should keep the flow short.
ReCharge3Watch Charge Created

Watch Charge Created

Instant trigger

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

You get a bundle for every new charge ReCharge creates, which lets you log upcoming revenue in a spreadsheet or tell your finance tool that money is on its way.

How it fires
Instant, through a webhook. Make waits and ReCharge calls it as soon as the event happens.
When to use it
Pick it to track charges from the moment they exist, rather than waiting for the payment result.
Watch out
A created charge is not a paid charge. If your follow-up depends on the money arriving, choose Watch Charge Paid instead.
ReCharge4Watch Charge Failed

Watch Charge Failed

Instant trigger

In Make“Triggers when an existing charge is failed.”

Hear about a failed payment the moment ReCharge records it, then alert the customer or your support team before the subscriber quietly churns.

How it fires
Instant. The event reaches Make by webhook as soon as ReCharge records it, no schedule involved.
When to use it
Retention teams use it to open a ticket or send a friendly card-update email as soon as a renewal bounces.
Watch out
Pair it with Get a Customer if your message needs the subscriber's name or email, because the trigger alone may not carry everything you want to show.
ReCharge5Watch Charge Maximum Retries Reached

Watch Charge Maximum Retries Reached

Instant trigger

In Make“Triggers when the maximum number of charge retries is reached.”

This one tells you that ReCharge has stopped retrying a charge, which is the last useful moment to reach the customer personally.

How it fires
Instant. ReCharge calls Make through a webhook as soon as it happens, so there is no polling interval to set.
When to use it
Choose it over Watch Charge Failed when a single failure is too noisy and you only want to act once the retries are exhausted.
Watch out
ReCharge decides when the limit is reached, not Make. Your scenario only reacts to that decision, it does not change it.
ReCharge6Watch Charge Paid

Watch Charge Paid

Instant trigger

In Make“Triggers when an existing charge is paid.”

Each successful payment becomes a bundle you can push to accounting, a revenue dashboard or a thank-you sequence.

How it fires
Instant: the lightning badge on the module means ReCharge pushes the event to Make by webhook the moment it occurs.
When to use it
A brand that sends a handwritten note or a loyalty point after every paid renewal can hang that step on this trigger.
Watch out
Refunds arrive later through Watch Charge Refunded. If you keep totals in a sheet, plan a second scenario so paid and refunded amounts both land there.
ReCharge7Watch Charge Refunded

Watch Charge Refunded

Instant trigger

In Make“Triggers when an existing charge is refunded.”

Make learns about every refunded charge, so your books, your analytics and your customer notes stay in line with what ReCharge actually kept.

How it fires
Instant, through a webhook. Make waits and ReCharge calls it as soon as the event happens.
When to use it
Finance teams that reconcile subscriptions outside ReCharge use it to write a correcting line right away.
Watch out
A refund can follow a paid charge you already logged. Match on the charge in your destination instead of adding a new row blindly, or you will count it twice.
ReCharge8Watch Charge Upcoming

Watch Charge Upcoming

Instant trigger

In Make“Triggers when an existing charge is upcoming.”

Your scenario hears about a charge that is coming up, which gives you room to warn the subscriber or adjust the order before it is billed.

How it fires
Instant. The event reaches Make by webhook as soon as ReCharge records it, no schedule involved.
When to use it
Useful for a pre-renewal reminder, or for asking the customer whether they want to skip this delivery.
Watch out
The trigger only reacts to what ReCharge flags as upcoming. That timing is set in ReCharge, so check it there before promising a date to anyone.
ReCharge9Watch Charge Updated

Watch Charge Updated

Instant trigger

In Make“Triggers when an existing charge is updated.”

Any change ReCharge records on an existing charge reaches Make as a bundle, so you never have to compare two versions by hand.

How it fires
Instant. ReCharge calls Make through a webhook as soon as it happens, so there is no polling interval to set.
When to use it
Take it when you mirror charges in another tool and want that copy to follow every edit.
Watch out
Updates can be frequent. Add a filter after the trigger so only the changes you care about go on, which saves operations.
ReCharge10Watch Customer Activated

Watch Customer Activated

Instant trigger

In Make“Triggers when an existing customer is activated.”

A customer switching to active in ReCharge kicks off your scenario, ideal for a welcome-back message or a CRM tag.

How it fires
Instant: the lightning badge on the module means ReCharge pushes the event to Make by webhook the moment it occurs.
When to use it
Win-back campaigns use it to thank returning subscribers and stop the reactivation emails they were still receiving.
Watch out
Activation is not creation. For brand-new accounts, Watch Customer Created is the module to pick.
ReCharge11Watch Customer Created

Watch Customer Created

Instant trigger

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

New ReCharge customers show up in Make one by one, so you can add them to your newsletter tool or your CRM without a CSV export.

How it fires
Instant, through a webhook. Make waits and ReCharge calls it as soon as the event happens.
When to use it
Pick it when the onboarding sequence should start with the account, before any order ships.
Watch out
Add a Search Customers step in your CRM app first if the person may already exist there, or you risk duplicate contacts.
ReCharge12Watch Customer Deactivated

Watch Customer Deactivated

Instant trigger

In Make“Triggers when an existing customer is deactivated.”

The scenario runs when a customer becomes inactive in ReCharge, so a churn survey or a final offer can go out while the decision is fresh.

How it fires
Instant. The event reaches Make by webhook as soon as ReCharge records it, no schedule involved.
When to use it
Customer success teams use it to flag lost accounts in the CRM and stop marketing emails that no longer fit.
Watch out
Keep the message light. A deactivation can come from several causes, and the trigger does not tell you which one on its own.
ReCharge13Watch Customer's Payment Method Updated

Watch Customer's Payment Method Updated

Instant trigger

In Make“Triggers when a customer's payment method is updated.”

You get notified when a customer changes the card or payment method on file, which usually ends a payment problem.

How it fires
Instant. ReCharge calls Make through a webhook as soon as it happens, so there is no polling interval to set.
When to use it
After a failed charge, use it to close the support ticket or stop the reminder sequence automatically.
Watch out
The bundle concerns the customer, not a charge. To retry anything, you still need a separate module and a clear rule in your scenario.
ReCharge14Watch Customer Updated

Watch Customer Updated

Instant trigger

In Make“Triggers when an existing customer is updated.”

Edits to a customer record, such as a new email or name, flow into Make so your other tools stay in sync with ReCharge.

How it fires
Instant: the lightning badge on the module means ReCharge pushes the event to Make by webhook the moment it occurs.
When to use it
Choose it when ReCharge is where customers maintain their details and your CRM should copy those changes.
Watch out
If your scenario writes back with Update a Customer, that update can start this trigger again. A filter after the trigger keeps the flow from looping.
ReCharge15Watch Onetime Created

Watch Onetime Created

Instant trigger

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

A new onetime record in ReCharge starts your scenario, handy for telling the warehouse that an extra item joins an order.

How it fires
Instant, through a webhook. Make waits and ReCharge calls it as soon as the event happens.
When to use it
Stores selling add-ons next to subscriptions use it to update stock counts or packing notes.
Watch out
Onetimes and subscriptions are separate objects in ReCharge. A scenario watching subscriptions will not see this event.
ReCharge16Watch Onetime Deleted

Watch Onetime Deleted

Instant trigger

In Make“Triggers when an existing onetime is deleted.”

When a onetime disappears from ReCharge, Make hears about it, so your packing list or stock sheet can drop the item too.

How it fires
Instant. The event reaches Make by webhook as soon as ReCharge records it, no schedule involved.
When to use it
Pick it when a customer can remove extras from the portal and your fulfillment team works from another tool.
Watch out
The record is gone in ReCharge. Keep the details you need in the destination before deletion, since a Get a Onetime afterwards has nothing to return.
ReCharge17Watch Onetime Updated

Watch Onetime Updated

Instant trigger

In Make“Triggers when an existing onetime is updated.”

Every change to an existing onetime reaches Make, so quantities or dates in your other tools follow what the customer edited.

How it fires
Instant. ReCharge calls Make through a webhook as soon as it happens, so there is no polling interval to set.
When to use it
Take it when onetimes are mirrored in an inventory sheet that must stay exact.
Watch out
Several edits in a row mean several bundles. Your destination should update the same line rather than add a new one each time.
ReCharge18Watch Order Cancelled

Watch Order Cancelled

Instant trigger

In Make“Triggers when an existing order is cancelled.”

A cancelled order in ReCharge triggers your scenario, so the warehouse stops preparing a box nobody will receive.

How it fires
Instant: the lightning badge on the module means ReCharge pushes the event to Make by webhook the moment it occurs.
When to use it
Use it when fulfillment runs outside ReCharge and every cancellation must reach the packing team.
Watch out
Cancelling an order is different from cancelling a subscription. Watch Subscription Cancelled covers the second case.
ReCharge19Watch Order Created

Watch Order Created

Instant trigger

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

Each new ReCharge order becomes a bundle you can send to a fulfillment tool, a Slack channel or a shipping sheet.

How it fires
Instant, through a webhook. Make waits and ReCharge calls it as soon as the event happens.
When to use it
This is the classic starting point for sending orders to a third-party logistics provider.
Watch out
Created does not mean processed. If your partner should only receive finished orders, Watch Order Processed fits better.
ReCharge20Watch Order Deleted

Watch Order Deleted

Instant trigger

In Make“Triggers when an existing order is deleted.”

Your scenario reacts when an order is deleted in ReCharge, so the copy in your other tools can be removed or marked.

How it fires
Instant. The event reaches Make by webhook as soon as ReCharge records it, no schedule involved.
When to use it
Choose it to keep a reporting sheet honest when orders vanish from ReCharge.
Watch out
Nothing can be fetched from ReCharge afterwards. Rely on what the trigger bundle carries and on the data you saved earlier.
ReCharge21Watch Order Processed

Watch Order Processed

Instant trigger

In Make“Triggers when an existing order is processed.”

Make is told when ReCharge finishes processing an order, the right moment to hand it to shipping or send a confirmation.

How it fires
Instant. ReCharge calls Make through a webhook as soon as it happens, so there is no polling interval to set.
When to use it
Use it when downstream steps should only run on orders that went through, not on drafts or upcoming ones.
Watch out
If you also watch Order Created, the same order can pass through two scenarios. Decide which one owns each follow-up.
ReCharge22Watch Order Upcoming

Watch Order Upcoming

Instant trigger

In Make“Triggers when an existing order is upcoming.”

You get a heads-up on orders that are about to happen, which leaves space for a reminder or a last change.

How it fires
Instant: the lightning badge on the module means ReCharge pushes the event to Make by webhook the moment it occurs.
When to use it
Subscription boxes use it to invite customers to swap a product before the order goes out.
Watch out
ReCharge sets what counts as upcoming. Check that timing in ReCharge before promising anything in your message.
ReCharge23Watch Order Updated

Watch Order Updated

Instant trigger

In Make“Triggers when an existing order is updated.”

Changes to an existing order land in Make, so your fulfillment copy stays aligned with ReCharge.

How it fires
Instant, through a webhook. Make waits and ReCharge calls it as soon as the event happens.
When to use it
Pick it when support agents edit orders in ReCharge and the warehouse works from a separate list.
Watch out
Updates from your own scenario (Update an Order) fire it too. Guard the flow with a filter to avoid endless round trips.
ReCharge24Watch Subscription Activated

Watch Subscription Activated

Instant trigger

In Make“Triggers when an existing subscription is activated.”

The scenario starts as soon as a subscription turns active, a good moment for onboarding content or a first-box checklist.

How it fires
Instant. The event reaches Make by webhook as soon as ReCharge records it, no schedule involved.
When to use it
Use it to add the subscriber to a tag or a list in your email tool the moment the plan is live.
Watch out
Reactivations can fire it as well. If your welcome email should only go to newcomers, check the history in a later step.
ReCharge25Watch Subscription Cancelled

Watch Subscription Cancelled

Instant trigger

In Make“Triggers when an existing subscription is cancelled.”

A subscriber cancelling reaches Make right away, so you can log the reason, alert the team or send an exit survey.

How it fires
Instant. ReCharge calls Make through a webhook as soon as it happens, so there is no polling interval to set.
When to use it
Retention workflows rely on it to measure churn in a sheet and to trigger a win-back offer.
Watch out
A cancelled subscription is still in ReCharge. Watch Subscription Deleted is the event for records that are removed.
ReCharge26Watch Subscription Created

Watch Subscription Created

Instant trigger

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

Every new subscription arrives in your scenario as a bundle, perfect for a welcome sequence or a CRM deal.

How it fires
Instant: the lightning badge on the module means ReCharge pushes the event to Make by webhook the moment it occurs.
When to use it
Growth teams hook it to their analytics sheet to see new plans appear as they are sold.
Watch out
One customer can hold several subscriptions. Your destination should key on the subscription, not only on the customer.
ReCharge27Watch Subscription Deleted

Watch Subscription Deleted

Instant trigger

In Make“Triggers when an existing subscription is deleted.”

This trigger fires when a subscription is removed from ReCharge, so the matching record elsewhere can be archived.

How it fires
Instant, through a webhook. Make waits and ReCharge calls it as soon as the event happens.
When to use it
Choose it to clean a CRM or reporting sheet when subscriptions are deleted rather than cancelled.
Watch out
After deletion, Get a Subscription has nothing to return. Store what matters before, or work only with the trigger bundle.
ReCharge28Watch Subscription Skipped

Watch Subscription Skipped

Instant trigger

In Make“Triggers when an existing subscription is skipped.”

Make is warned when a subscriber skips a delivery, which lets you adjust stock forecasts or send a short check-in.

How it fires
Instant. The event reaches Make by webhook as soon as ReCharge records it, no schedule involved.
When to use it
Use it when skipped boxes change what the warehouse should prepare.
Watch out
The opposite move, a subscriber taking the skip back, arrives through Watch Subscription Unskipped. Watch both if your sheet counts skips.
ReCharge29Watch Subscription Unskipped

Watch Subscription Unskipped

Instant trigger

In Make“Triggers when an existing subscription is unskipped.”

A skip taken back in ReCharge triggers your scenario, so the delivery returns to your packing plan.

How it fires
Instant. ReCharge calls Make through a webhook as soon as it happens, so there is no polling interval to set.
When to use it
Pick it together with Watch Subscription Skipped to keep a forecast sheet accurate in both directions.
Watch out
If only one of the pair is active, your numbers drift. Turn both scenarios on, keeping the Free plan's limit of 2 active scenarios in mind.
ReCharge30Watch Subscription Updated

Watch Subscription Updated

Instant trigger

In Make“Triggers when an existing subscription is updated.”

Every change ReCharge records on an existing subscription lands in Make, so the copies you keep elsewhere stay aligned.

How it fires
Instant: the lightning badge on the module means ReCharge pushes the event to Make by webhook the moment it occurs.
When to use it
Take it when a CRM or data warehouse mirrors subscriptions and should reflect each edit.
Watch out
It fires often. A filter after the trigger keeps only the changes your scenario needs and saves operations.
Modules

What can ReCharge do inside a scenario?

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

ReCharge1

Activate a Subscription

Action

In Make“Activates an existing subscription.”

Turns an existing subscription back on in ReCharge from your scenario, so a returning customer is live again without manual clicks.

When to use it
A win-back form filled on your site can reactivate the plan directly.
Watch out
Map the right subscription. A Search Subscriptions step before it helps find it when you only know the customer.
ReCharge2

Add a Discount to a Charge

Action

In Make“Adds a discount to a charge.”

Applies an existing discount to one specific charge, useful for a goodwill gesture on the next payment only.

When to use it
Support can grant a one-time reduction after a delivery problem, triggered from a helpdesk tag.
Watch out
The discount must already exist. Create a Discount first if you are building offers on the fly.
ReCharge3

Add a Discount to an Address

Action

In Make“Adds a discount to an address.”

Attaches a discount to an address, so the reduction follows the orders shipped there rather than a single charge.

When to use it
Pick it when a promotion targets a household or a delivery location rather than one payment.
Watch out
Remove it later with Remove a Discount from an Address, or the reduction keeps applying.
ReCharge4

Cancel a Subscription

Action

In Make“Cancels an existing subscription.”

Stops an existing subscription from your scenario, for example when a cancellation request arrives through a form or a support tool.

When to use it
Teams that handle cancellations outside ReCharge use it to apply the decision without logging in.
Watch out
Cancelling is not deleting: the record stays in ReCharge. Double-check the subscription you map before running it.
ReCharge5

Change an Order Date

Action

In Make“Changes an order date.”

Moves an order to another date in ReCharge, handy when a customer asks to receive the box later.

When to use it
A support macro or a form answer can push the order date without anyone opening ReCharge.
Watch out
Changing an order is not the same as moving the next charge. Change the Next Charge Date handles billing timing.
ReCharge6

Change a Subscription Address

Action

In Make“Changes an existing subscription address.”

Points an existing subscription to another address, so every future delivery of that plan goes to the new place instead of the old one.

When to use it
Use it when a customer moves and sends the new details through a form or a helpdesk outside ReCharge.
Watch out
The address has to exist in ReCharge first. If it is brand new, run Create an Address earlier in the scenario and map its result here.
ReCharge7

Change the Next Charge Date

Action

In Make“Changes the next charge date.”

Shifts the date of the next charge for a subscription, giving the customer breathing room or aligning billing with a delivery.

When to use it
Pick it when a customer asks to delay a renewal through your helpdesk.
Watch out
This affects billing. Confirm the new date with the customer before your scenario sends it.
ReCharge8

Clone an Order

Action

In Make“Clones an existing order.”

Copies an existing order, a quick way to resend the same box after a lost parcel.

When to use it
Support teams use it when a replacement shipment should match the original order exactly.
Watch out
Check what the clone contains before it ships. Test with Run once on a real order first.
ReCharge9

Count Addresses

Action

In Make“Counts all existing addresses.”

Returns how many addresses ReCharge holds as a single number, which you can drop straight into a report row or a message to the team.

When to use it
Use it for a dashboard tile when searching every address and counting the bundles yourself would waste operations.
Watch out
You get a total, not the addresses themselves. Search Addresses is the module that brings back the actual records.
ReCharge10

Count Charges

Action

In Make“Counts all existing charges.”

Gives you the number of charges in ReCharge in one operation, ready for a revenue or health report.

When to use it
Pick it when a KPI sheet needs a charge total without pulling every record.
Watch out
A count is cheap in operations compared with a search that returns many bundles.
ReCharge11

Count Customers

Action

In Make“Counts all existing customers.”

Returns the total number of customers stored in ReCharge, one clean figure for a growth dashboard or a team update.

When to use it
Handy when a report built in Google Sheets or posted to Slack needs that headline number without pulling every customer record.
Watch out
It says how many, not who. To follow individual changes, the customer triggers are the right starting point.
ReCharge12

Count Discounts

Action

In Make“Counts all existing discounts.”

Tells you how many discounts exist in ReCharge, useful to keep an eye on promotions piling up.

When to use it
Marketing teams use it to spot when old codes should be cleaned out.
Watch out
A count is only a figure. Pair it with Search Discounts to see which ones they are.
ReCharge13

Count Metafields

Action

In Make“Counts all existing metafields.”

Returns how many metafields are stored in ReCharge, a quick way to see how much custom data your scenarios have attached so far.

When to use it
Pick it when you audit the extra data written into ReCharge by several automations and want a number before digging in.
Watch out
It counts without listing anything. Use Search Metafields when you need to read the values themselves.
ReCharge14

Count Orders

Action

In Make“Counts all existing orders.”

Gives the total of orders in ReCharge as one value, ready to land in a reporting row or a summary message for the operations team.

When to use it
Use it for an order volume indicator in a dashboard, when the number matters more than the details of each order.
Watch out
One number costs one operation. It will not send each order down the scenario, so pick Search Orders if you need them one by one.
ReCharge15

Count Subscriptions

Action

In Make“Counts all existing subscriptions.”

Returns how many subscriptions ReCharge holds, the headline figure most subscription businesses watch before anything else.

When to use it
Drop it into a report or a Slack message so the whole team sees the same total without opening ReCharge.
Watch out
The count alone will not split active and cancelled plans for you. Search Subscriptions brings back the records if you need that detail.
ReCharge16

Create a Discount

Action

In Make“Creates a new discount.”

Creates a new discount in ReCharge from your scenario, so offers can be generated by events instead of by hand.

When to use it
Useful when a referral or a survey answer should produce a personal discount.
Watch out
Creating is only half the job. Add a Discount to a Charge or to an Address to apply it.
ReCharge17

Create a Metafield

Action

In Make“Creates a new metafield.”

Adds a metafield to ReCharge, a slot for custom data your team wants to keep next to a record.

When to use it
Pick it to store a note or tag coming from another tool, such as a CRM segment.
Watch out
Stay consistent with names across scenarios, or you will end up with several metafields meaning the same thing.
ReCharge18

Create an Address

Action

In Make“Creates a new address.”

Saves a new address in ReCharge from your scenario, so it is ready to attach to a subscription or an order later in the flow.

When to use it
Use it when addresses are collected in a form, a CRM or a checkout tool and must also exist in ReCharge.
Watch out
Validation is a separate step. Validate an Address can check the new record afterwards, but it only works for USA addresses.
ReCharge19

Create a Onetime

Action

In Make“Creates a new onetime.”

Adds a onetime record in ReCharge, so an extra item can be included next to a subscription.

When to use it
Upsell flows use it when a customer accepts an offer in an email or on a landing page.
Watch out
Map the right address or subscription context. A wrong target means the item ships elsewhere.
ReCharge20

Create a Subscription

Action

In Make“Creates a new subscription.”

Opens a new subscription in ReCharge straight from your scenario, without anyone filling the ReCharge admin by hand.

When to use it
Use it when plans are sold through a channel ReCharge does not see directly, such as a sales call logged in a CRM.
Watch out
Check that the customer and the address already exist before this step. A Search Customers module placed earlier helps you avoid duplicates.
ReCharge21

Delete a Customer

Action

In Make“Deletes an existing customer.”

Removes a customer from ReCharge, typically to honor a data deletion request coming from a form.

When to use it
Privacy workflows use it when a request must be applied everywhere at once.
Watch out
Treat it as final: plan a Get a Customer step first if you need to archive the record.
ReCharge22

Delete a Discount

Action

In Make“Deletes an existing discount.”

Removes a discount from ReCharge entirely, which keeps your list of offers short and easy to read for the whole team.

When to use it
Pick it when a campaign ends and its code should disappear everywhere, triggered for example by a row marked as closed in a sheet.
Watch out
Deleting a discount is not the same as taking it off one charge. For that narrower job, use Remove a Discount from a Charge.
ReCharge23

Delete a Metafield

Action

In Make“Deletes an existing metafield.”

Erases a metafield from ReCharge once the custom data it holds no longer serves any scenario or any person on the team.

When to use it
Use it in cleanup scenarios, after a data migration or when a tag your automations used to write has been retired.
Watch out
Make sure no other scenario still reads that metafield. Those scenarios would find nothing and may stop on an error.
ReCharge24

Delete an Address

Action

In Make“Deletes an existing address.”

Removes an address from ReCharge, for example an old location a customer told support they no longer use.

When to use it
Choose it in a cleanup scenario started by a support request or a form, so nobody has to search for the address by hand.
Watch out
Check that no active subscription still points to that address before running it. Get a Subscription or Search Subscriptions helps you verify.
ReCharge25

Delete an Order

Action

In Make“Deletes an existing order.”

Deletes an order from ReCharge from inside your scenario, so duplicates or test entries do not pollute your reports.

When to use it
Useful for removing test orders created while you built other scenarios, or duplicates spotted by a check earlier in the flow.
Watch out
Treat the deletion as final. Test the module with Run once on a test order, never on a live customer order.
ReCharge26

Delete a Onetime

Action

In Make“Deletes an existing onetime.”

Removes a onetime record from ReCharge, taking the extra item out of what the customer will receive.

When to use it
Pick it when a customer declines an add-on through an email reply, a chat or a form connected to Make.
Watch out
If another scenario runs on Watch Onetime Deleted, your deletion can start it. Make sure the two do not feed each other in a loop.
ReCharge27

Delete a Subscription

Action

In Make“Deletes an existing subscription.”

Removes a subscription from ReCharge entirely, record included, instead of simply stopping it.

When to use it
Use it for test data or subscriptions created by mistake by another automation, not for customers who decide to leave.
Watch out
For a real churn, Cancel a Subscription keeps the record in ReCharge. Delete only when you are sure nobody will need that history.
ReCharge28

Get a Charge

Action

In Make“Retrieves an existing charge.”

Fetches the full details of one charge, so later modules can use its amount, status or dates.

When to use it
Pick it after a trigger that gives you only part of the charge, before sending a precise message.
Watch out
It returns one charge. To find several, Search Charges is the module.
ReCharge29

Get a Customer

Action

In Make“Retrieves an existing customer.”

Pulls one customer record from ReCharge, giving you the details needed for an email or a CRM update.

When to use it
Place it right after a charge or subscription trigger when the message needs the person's details.
Watch out
You need to know which customer to fetch. Map it from the trigger bundle.
ReCharge30

Get a Discount

Action

In Make“Retrieves an existing discount.”

Retrieves one discount with its details, so later modules can quote the exact offer instead of a vague promise.

When to use it
Useful when a support reply or a confirmation email should mention the discount applied to a customer's order.
Watch out
It returns one discount per run. When you need several, or do not know which one, Search Discounts is the better starting point.
ReCharge31

Get a Metafield

Action

In Make“Retrieves an existing metafield.”

Reads one metafield back from ReCharge, bringing the custom data you stored earlier into the current scenario.

When to use it
Pick it when a decision in your scenario, such as which email to send, depends on a value another automation saved.
Watch out
If that metafield was deleted, there is nothing to read. Add a filter or an error route so the scenario does not stop halfway.
ReCharge32

Get an Address

Action

In Make“Retrieves an existing address.”

Fetches one address from ReCharge with its details, ready to feed a shipping label or a check before dispatch.

When to use it
Use it before sending delivery data to a logistics tool, so the partner receives the address exactly as ReCharge stores it.
Watch out
If the address is in the USA, you can follow with Validate an Address. For other countries, that validation step does not apply.
ReCharge33

Get an Order

Action

In Make“Retrieves an existing order.”

Loads one order with its details, the solid base for a confirmation message or a request to a fulfillment partner.

When to use it
Place it after an order trigger when the next app needs more than the trigger itself delivers.
Watch out
One order costs one operation. For a batch of orders, Search Orders returns them in a single step and suits the job better.
ReCharge34

Get a Onetime

Action

In Make“Retrieves an existing onetime.”

Retrieves one onetime record with its details, so the extra item can appear by name in the next steps of your scenario.

When to use it
Pick it when a packing slip, a Slack alert or a customer message should mention the add-on precisely.
Watch out
Once a onetime has been deleted in ReCharge, this module has nothing left to fetch. Store what you need while it still exists.
ReCharge35

Get a Shop

Action

In Make“Retrieves your shop information.”

Returns your shop information from ReCharge, the store context that sits above every customer, order and subscription.

When to use it
Useful at the start of a report, or when a message or a document generated by Make needs your store details.
Watch out
It only reads data. It does not change any setting of your shop, so it is safe to test with Run once.
ReCharge36

Get a Subscription

Action

In Make“Retrieves an existing subscription.”

Fetches one subscription with its details, so the next modules know which plan, status and dates are involved.

When to use it
Use it after a charge trigger when your follow-up message depends on the plan the customer holds.
Watch out
The module does not guess which subscription you mean. Map it from an earlier bundle, such as the one a trigger delivered.
ReCharge37

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the ReCharge API from your scenario, using the connection you already created, to cover what the listed modules leave out.

When to use it
Choose it when you need an operation that none of the 89 modules offers, once you have checked the list on this page.
Watch out
You write the request yourself, so keep ReCharge's API documentation open and test with Run once before switching the scenario on.
ReCharge38

Remove a Discount from a Charge

Action

In Make“Removes a discount from a charge.”

Takes a discount off one specific charge, so that payment goes through at its normal amount.

When to use it
Pick it when a discount was added by mistake, or when an offer should stop before the next billing.
Watch out
Only that charge changes. The discount itself stays in ReCharge and can still be applied elsewhere, so delete it separately if needed.
ReCharge39

Remove a Discount from an Address

Action

In Make“Removes a discount from an address.”

Detaches a discount from an address, so future orders shipped there go back to full price.

When to use it
Use it to close a promotion that was tied to a delivery location, for instance when a partner office leaves your program.
Watch out
The discount still exists after this step. Delete a Discount is the module if you want it gone from ReCharge entirely.
ReCharge40

Skip a Charge

Action

In Make“Skips a charge.”

Skips a charge in ReCharge, so the customer is not billed for that cycle and keeps the subscription running.

When to use it
Handy when a customer asks to skip a delivery through a form, an email reply or a chat connected to Make.
Watch out
Unskip a Charge reverses the move. Keep both modules in mind if customers can change their mind after the request.
ReCharge41

Unskip a Charge

Action

In Make“Unskips a charge.”

Puts a skipped charge back on track, so the subscriber is billed and shipped as planned again. It is the undo button for Skip a Charge.

When to use it
A customer changes their mind after skipping and writes to support asking for the next box after all.
Watch out
Make needs to know which charge to restore; place Search Charges before it and map the charge from that module.
ReCharge42

Update a Customer

Action

In Make“Updates an existing customer.”

Edits an existing customer record in ReCharge from your scenario, so the details your team keeps elsewhere stay in line with what ReCharge holds. Each run of the module counts as one operation, the unit Make bills on your plan.

When to use it
A shopper corrects their contact details in your help desk or CRM and ReCharge should carry the same information.
Watch out
Pick the customer with Search Customers or Get a Customer first; otherwise the scenario has nothing to point at.
ReCharge43

Update a Discount

Action

In Make“Updates an existing discount.”

Changes a discount that already exists in ReCharge instead of creating a new one next to it. Your promo keeps its identity while its settings move.

When to use it
A campaign is extended or adjusted and the code shoppers already know has to keep working with the new setup.
Watch out
Locate the discount with Search Discounts or Get a Discount first, then check the result with Run once before switching the scenario on.
ReCharge44

Update a Metafield

Action

In Make“Updates an existing metafield.”

Rewrites the value of a metafield already stored in ReCharge, the extra data your shop attaches to its records. The record stays the same, only the stored value changes.

When to use it
A value computed in another tool, a spreadsheet or a form answer, needs to land on the matching ReCharge record.
Watch out
Use Search Metafields to find the right one; if nothing exists yet, Create a Metafield is the module to pick instead.
ReCharge45

Update an Address

Action

In Make“Updates an existing address.”

Modifies a saved shipping address in ReCharge, so the next deliveries go where the customer actually lives now.

When to use it
A subscriber announces a move through a form or an email and you want the change applied without anyone retyping it.
Watch out
For US addresses, chain Validate an Address after the update to check the result before the next shipment.
ReCharge46

Update an Order

Action

In Make“Updates an existing order.”

Edits an order that ReCharge has already generated, keeping the same order rather than cloning or recreating it.

When to use it
Support fixes a detail on a pending order after a customer request, and the fix should come from a single place in your process.
Watch out
An order ReCharge has already processed may no longer be the right target; filter on its status from Search Orders or Get an Order before you touch it.
ReCharge47

Update a Onetime

Action

In Make“Updates an existing onetime.”

Adjusts a onetime already attached to a customer in ReCharge, without deleting it and starting over.

When to use it
A customer asks to change the extra item they added to an upcoming delivery.
Watch out
Onetimes and subscriptions are separate records; if the change concerns the recurring product, Update a Subscription is the right module.
ReCharge48

Update a Subscription

Action

In Make“Updates an existing subscription.”

Changes an active subscription in ReCharge from Make, the central record of what a customer receives and pays again and again.

When to use it
Your team decides on a plan change in another tool, such as a support ticket or a CRM stage, and ReCharge must follow.
Watch out
Dedicated modules exist for the address and the next charge date: Change a Subscription Address and Change the Next Charge Date say more clearly what the scenario does.
ReCharge49

Validate an Address

Action

In Make“Validates an existing address. Address validation works only for USA addresses.”

Checks an address stored in ReCharge and tells your scenario whether it holds up, before a package leaves for a street that does not exist.

When to use it
Right after Create an Address or Update an Address, to catch a typo while the customer can still be reached.
Watch out
According to the doc, validation only works for addresses in the USA, so route other countries around this module with a filter.
ReCharge50

List Shipping Countries

Search

In Make“Lists all existing shipping countries.”

Returns the countries your ReCharge shop ships to, one bundle per country (a bundle is one item passed from a module to the next).

When to use it
Before accepting an address from a form, to check that the destination is one you actually serve.
Watch out
Each country comes out as its own bundle, so the following modules run once per country unless you aggregate them.
ReCharge51

Search Addresses

Search

In Make“Searches for addresses or lists them all.”

Finds addresses in ReCharge, or lists them all, and hands each match to the next module as a separate bundle.

When to use it
You hold a customer and want every delivery address on file before editing one or adding a discount to it.
Watch out
A search can return zero, one or many results; plan the case where nothing matches so the scenario does not stop silently.
ReCharge52

Search Charges

Search

In Make“Searches for charges or lists them all.”

Looks up charges in ReCharge and returns zero, one or several, the billing lines that turn a subscription into a payment.

When to use it
It feeds Skip a Charge, Unskip a Charge or a discount module when you first need the ID of the right charge.
Watch out
Listing everything multiplies the bundles, and each module after it spends one operation per bundle.
ReCharge53

Search Customers

Search

In Make“Searches for customers or lists them all.”

Pulls customers out of ReCharge by search, or all of them, so the scenario can act on the right person.

When to use it
An email address arrives from a form or a help desk and you need the matching ReCharge customer before any update.
Watch out
If two records match, both continue down the scenario; add a filter or keep only the first result.
ReCharge54

Search Discounts

Search

In Make“Searches for discounts or lists them all.”

Retrieves discounts configured in ReCharge, one bundle each, to reuse them further down the scenario.

When to use it
Before attaching a promo to a charge or an address, to fetch the discount by what you know about it.
Watch out
No match means no bundle, and the modules placed after it simply do not run for that execution.
ReCharge55

Search Metafields

Search

In Make“Searches for metafields or lists them all.”

Brings back metafields stored in ReCharge, that extra data layer your shop adds to its records.

When to use it
You want to read a custom value before deciding what the scenario does, or locate the metafield to update.
Watch out
Several metafields can come back at once; check with Run once how many bundles arrive before mapping them.
ReCharge56

Search Onetimes

Search

In Make“Searches for onetimes or lists them all.”

Lists the onetimes in ReCharge, or the ones matching your search, each as its own bundle.

When to use it
To review the extra items planned on upcoming deliveries, or to find the one a customer wants removed.
Watch out
If the next step is Delete a Onetime, check the results first: a deletion cannot be undone.
ReCharge57

Search Orders

Search

In Make“Searches for orders or lists them all.”

Gets orders from ReCharge that match your criteria, so an export or a follow-up works on real data.

When to use it
Feeding a reporting sheet, or finding the order a support ticket is about before editing it.
Watch out
A broad search can return many bundles; each module that follows counts one operation per order.
ReCharge58

Search Payment Sources

Search

In Make“Searches for payment sources or lists them all.”

Returns the payment sources saved in ReCharge, the means customers are billed with.

When to use it
Following a failed charge, to see which payment source a customer has on file before reaching out.
Watch out
This module only reads; there is no module in the list to edit a payment source, which would need Make an API Call.
ReCharge59

Search Subscriptions

Search

In Make“Searches for subscriptions or lists them all.”

Finds subscriptions in ReCharge and sends each one down the scenario as a bundle.

When to use it
Starting point for a batch change, or to locate a customer's subscription before cancelling it.
Watch out
Test with Run once and read the bundles: an unfiltered list can reach every subscriber at once.
Need help

Need help automating ReCharge with Make?

A person reads every message.

FAQ

ReCharge and Make: common questions

01Is the ReCharge Make integration free?
Yes, on the Make side. ReCharge is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Every module run counts as one operation on your plan. Paid plans lift these limits, for example with unlimited active scenarios. You still need an active ReCharge account, whose subscription is handled by ReCharge itself, so check their pricing page for that part.
02What do you need to connect ReCharge to Make?
An active ReCharge account and an API token. You create the token in ReCharge under Tools & apps, then API tokens, with a name, a contact email and the scope permissions you want to grant. In Make, add a ReCharge module, click Create a connection, give it a name if you like and paste the token. If the module is an instant trigger, Make asks you to click Create a webhook first, then Create a connection.
03Does the ReCharge trigger react in real time?
Yes. All 30 ReCharge triggers are instant: ReCharge calls Make through a webhook as soon as the event happens, whether it is a new order, a failed charge or a skipped subscription. You do not set a polling interval for them, unlike scheduled triggers, which Make checks every 15 minutes by default. Once the scenario is switched on, each event starts one run, and each module it runs uses operations from your plan.
04What if a ReCharge module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the ReCharge API with the connection you already have, so you are not limited to the 89 listed modules. You will write the request yourself, which calls for ReCharge's API documentation. Keep in mind that Make's page for this app is marked as AI-generated from ReCharge's documentation, so double-check any detail that matters before building on it.
05Should you use Make or n8n for ReCharge?
It depends on where your other automations already run and on the modules you need. On Make, ReCharge comes with 89 modules, including 30 instant triggers and a Make an API Call module for the rest of the API. If you are weighing n8n, check whether it offers a node for ReCharge that covers the same events, then compare both tools on your own scenario. The comparison page linked above lists the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations