Resources · Make integration

ChargeOver Make integrationAutomate ChargeOver with Make.

Can Make react the moment someone subscribes or cancels in ChargeOver? Yes. The ChargeOver Make integration brings 7 instant triggers and 10 modules for customers and subscriptions. This guide links your account and walks you through a first scenario, no code involved.

Try the ChargeOver integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ChargeOver Make integration automate for you?

The ChargeOver Make integration plugs your billing account into Make. Events in ChargeOver, like a new subscription or a cancellation, can start a scenario (the automation you build in Make, a chain of small steps called modules), and Make can then create, change or look up customers and subscriptions for you.

Onboarding that starts by itself. Watch New Subscriptions fires when a plan is created. Add Get a Customer right after it to pull the buyer's full record, then hand it to your email tool or your team chat so nobody has to copy anything by hand.

Cancellations you see right away. Watch Cancelled Subscriptions reacts as soon as someone leaves, which is exactly when an account manager wants to hear about it. The reverse works too: when a customer asks to stop in your help desk, Cancel a Subscription closes the plan in ChargeOver from there.

A customer list without duplicates. Search Customers checks whether a person already exists before Create a Customer adds them, and Update a Customer keeps details in line when they change in another tool, for instance a base described on the Airtable Make integration page.

What the listed modules leave out: nothing in the list handles invoices or payments directly, so anything beyond customers, subscriptions, contacts and transactions goes through Make an API Call. Make's own ChargeOver documentation is marked as AI-generated, so double-check important details with ChargeOver. For the wider picture, read the Make review or the n8n vs Make comparison.

Connect

How do you connect ChargeOver to Make?

  1. 01

    Create API credentials in ChargeOver

    In ChargeOver, open Settings, then Developers, More Dev Tools and REST API. Enable the REST APIs and click Add New API Credentials. Leave that screen open, you will copy three values from it.

  2. 02

    Add a ChargeOver module in Make

    In your scenario, add any ChargeOver module and click Create a connection. A connection is your ChargeOver account linked to Make once and reused by every ChargeOver module. Naming it in Connection name is optional.

  3. 03

    Paste the three credentials

    For Domain, type the part of your account URL that comes before .chargeover.com. Then copy the Username shown on screen, and use the key ChargeOver labels Private Key as the API key. Save to create the connection.

First scenario

Your first ChargeOver scenario: a won deal becomes a subscription

GoalWhen a deal is closed in your sales tool, Make creates the customer in ChargeOver and starts their subscription.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the tool where deals are closed as the first module. It passes Make one bundle per deal, a bundle being one item moving from module to module.

  2. 02

    Add Create a Customer

    Click the + to the right of that first module, search for ChargeOver and choose Create a Customer. Link your account with Create a connection, then map the deal's details into the fields Make lists.

  3. 03

    Chain Create a Subscription

    Add Create a Subscription after it and map data from the customer module, so the plan lands on the account you just created instead of floating on its own.

  4. 04

    Test with Run once

    Click Run once, then close a test deal. Make runs the scenario one time and shows the bundles each module received. Open ChargeOver to check the new customer and its subscription.

  5. 05

    Schedule it and switch it on

    Set the schedule on the first module (every 15 minutes by default), then switch the scenario on. Each module run on one bundle counts as one operation, the unit Make tracks on your plan.

Triggers

Which ChargeOver triggers can start a scenario?

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

ChargeOver1Watch Cancelled Subscriptions

Watch Cancelled Subscriptions

Instant trigger

In Make“Triggers when a subscription is cancelled.”

You hear about each cancellation as it happens, with the cancelled subscription arriving as a bundle the next module can read. Churn stops being something you discover later in a report and becomes an event your scenario answers.

How it fires
instant. ChargeOver calls Make through a webhook as soon as the subscription is cancelled, which is why the module shows a lightning badge.
When to use it
to warn the account owner, remove access in another tool, or log the departure in a shared sheet.
ChargeOver2Watch New Contacts

Watch New Contacts

Instant trigger

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

Every contact added in ChargeOver can flow straight into the rest of your stack, so the people behind an account are known everywhere, not only in billing. The scenario receives one bundle per new contact.

How it fires
instant. ChargeOver pings Make through a webhook the moment the contact is created.
When to use it
when a customer adds a colleague who should also get invoices or product updates, and your mailing tool needs that name too.
Watch out
it only covers creation; later edits to a contact do not fire it.
ChargeOver3Watch New Customers

Watch New Customers

Instant trigger

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

A fresh customer record in ChargeOver becomes the starting signal for everything that follows: a CRM entry, a welcome message, a folder for the account. One bundle arrives per customer.

How it fires
instant. As soon as the customer exists, ChargeOver notifies Make by webhook.
When to use it
when your team creates customers directly in ChargeOver and other tools must catch up.
Watch out
if the same scenario also uses Create a Customer, the customers it creates could start this trigger too, so keep creating and watching in separate scenarios.
ChargeOver4Watch New Subscriptions

Watch New Subscriptions

Instant trigger

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

This is the trigger to pick when a sale matters more than a sign-up: it hands your scenario each new subscription, the plan a customer is now paying for.

How it fires
instant. A webhook from ChargeOver reaches Make right after the subscription is created, shown by the lightning badge on the module.
When to use it
to kick off onboarding, notify sales that a deal turned into revenue, or add the account to a customer success list. Chain Get a Customer after it when you need the buyer's full details.
ChargeOver5Watch New Transactions

Watch New Transactions

Instant trigger

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

Each new transaction recorded in ChargeOver shows up in your scenario as a bundle, which keeps finance tools and dashboards fed without exports.

How it fires
instant. ChargeOver sends a webhook to Make when the transaction is created.
When to use it
when you want every money movement copied to a spreadsheet or an accounting tool the moment it is recorded.
Watch out
it fires on creation. If what you care about is the outcome of a payment, Watch Transaction Status is the closer fit, since it reacts to status changes instead.
ChargeOver6Watch Transaction Status

Watch Transaction Status

Instant trigger

In Make“Triggers when a transaction status changes.”

Rather than every new transaction, this one follows what happens next: it starts your scenario whenever a transaction's status changes in ChargeOver.

How it fires
instant. ChargeOver warns Make by webhook right when the status moves.
When to use it
to react when a payment clears or gets stuck, for example by thanking the customer or alerting whoever handles collections.
Watch out
the internal key reads watchSuccessfulTransactions, yet the module listens to any status change, so read the status in the bundle before acting on it.
ChargeOver7Watch Updated Customers

Watch Updated Customers

Instant trigger

In Make“Triggers when a customer is updated.”

Keep other tools honest: whenever a customer record is edited in ChargeOver, the updated version lands in your scenario, ready to be pushed wherever that customer also lives.

How it fires
instant. ChargeOver calls Make over a webhook as soon as the customer changes.
When to use it
when billing is the reference for customer details and your CRM should follow it.
Watch out
pairing it with Update a Customer in the same flow could send changes back and forth, so push updates in one direction only.
Modules

What can Make do in ChargeOver?

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

ChargeOver1

Cancel a Subscription

Action

In Make“Cancels an existing subscription.”

Ends an existing subscription in ChargeOver from any other tool, so a cancellation request does not wait for someone to log in to billing.

When to use it
when a customer asks to stop through a help desk ticket or a form, and the plan should close right after.
Watch out
Make has no undo here, so test with a dummy subscription before switching the scenario on.
ChargeOver2

Create a Customer

Action

In Make“Creates a new customer.”

Adds a brand new customer to ChargeOver using data from earlier modules, which means sales or sign-up tools can open the billing account for you.

When to use it
when a deal closes or a trial converts somewhere else and billing should be ready without retyping.
Watch out
run Search Customers first when the person may already exist, or you will create a duplicate.
ChargeOver3

Create a Subscription

Action

In Make“Creates a new subscription.”

Starts a new subscription in ChargeOver, the step where a customer actually begins paying for a plan.

When to use it
right after Create a Customer, or after Search Customers has found the account, when an order or a signed quote should turn into recurring billing.
Watch out
map the customer from the previous module so the subscription attaches to the right account.
ChargeOver4

Delete a Customer

Action

In Make“Deletes a customer by identificator.”

Removes a customer from ChargeOver, identified by the customer's ID, which you usually get from Search Customers or a trigger bundle.

When to use it
cleaning out test records or honoring a deletion request that arrives through another tool.
Watch out
a deletion cannot be reversed from Make, so point this module at a single, confirmed ID and never at an unchecked search result.
ChargeOver5

Get a Customer

Action

In Make“Gets an existing customer.”

Fetches one existing customer with their full record, handy when a previous step only gave you an ID and the next one needs the whole record.

When to use it
after Watch New Subscriptions or Watch New Transactions, to enrich the bundle before sending a welcome email or a Slack alert.
Watch out
it reads a single customer; to find someone by other details, Search Customers is the one to use.
ChargeOver6

Get a Subscription

Action

In Make“Gets an existing subscription.”

Pulls the details of one existing subscription so later modules know exactly which plan a customer is on.

When to use it
when a transaction or cancellation reaches your scenario and you need the subscription behind it before deciding what to do next, such as routing a message to the right team.
Watch out
you need the subscription's ID from an earlier module.
ChargeOver7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Your way into any part of the ChargeOver API that the other modules skip, using the same connection, so there is no second login to set up.

When to use it
when you need something the list does not offer, such as working with invoices or payments directly.
Watch out
you describe the request yourself, so keep ChargeOver's API reference open while you build it.
ChargeOver8

Update a Customer

Action

In Make“Updates an existing customer.”

Changes an existing customer in ChargeOver so billing details match what the rest of your tools already know.

When to use it
when a company's details change in your CRM and invoices should follow without a manual edit.
Watch out
avoid running it in the same flow as Watch Updated Customers, since the updates it makes could start that trigger again.
ChargeOver9

Update a Subscription

Action

In Make“Updates an existing subscription.”

Edits an existing subscription, letting a change decided elsewhere reach billing without a trip into ChargeOver.

When to use it
when an upgrade or downgrade is approved in a form, a CRM or a support tool and the plan should reflect it.
Watch out
fetch the current state with Get a Subscription first when you are not sure which subscription the customer holds.
ChargeOver10

Search Customers

Search

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

Looks up customers in ChargeOver, or lists them all, and returns zero, one or several bundles depending on what matches.

When to use it
before Create a Customer to avoid duplicates, or to find the ID that Update a Customer or Delete a Customer needs.
Watch out
modules after it run once per result, so a broad search can cost many operations.
Need help

Need help automating ChargeOver with Make?

A person reads every message.

FAQ

ChargeOver and Make: the questions that come next

01Is the ChargeOver Make integration free?
Yes, on the Make side. ChargeOver is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes per execution, 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, lift the cap on active scenarios and allow 40 minutes per run, with usage counted in operations. You still need an active ChargeOver account, which ChargeOver bills separately according to its own pricing page.
02What do you need to connect ChargeOver to Make?
An active ChargeOver account with the REST APIs enabled, plus a set of API credentials. You create them in ChargeOver under Settings, Developers, More Dev Tools, REST API, with Add New API Credentials. Make then asks for three values: the Domain, meaning the part of your account URL before .chargeover.com, the Username shown on screen, and the Private Key used as the API key. For a trigger, click Create a webhook first, then Create a connection.
03Do ChargeOver triggers in Make fire instantly?
Yes. All 7 ChargeOver triggers are instant: ChargeOver calls Make through a webhook as soon as the event happens, whether that is a new customer, a new subscription, a cancellation, a new transaction or a transaction status change. A scheduled trigger works differently, because Make checks the app on the scenario's schedule, every 15 minutes by default. With ChargeOver, the scenario starts on the event itself, and each instant module shows a lightning badge in the editor so you can tell at a glance.
04What if a ChargeOver module is missing in Make?
Use Make an API Call. It reaches any endpoint of the ChargeOver API with the connection you already set up, so invoices, payments or anything else beyond the 17 listed modules stay within reach. The listed modules focus on customers and subscriptions, while contacts and transactions appear only as triggers. Also keep in mind that Make's ChargeOver documentation is flagged as AI-generated content, so for an important detail, confirm it with ChargeOver before building a scenario around it.
05Should you pick Make or n8n for ChargeOver?
It depends on how you like to build. On Make, ChargeOver comes with 17 modules, including 7 instant triggers, and Make an API Call for whatever those modules skip, all assembled in the scenario editor without code. The same app often has an n8n node as well, so check whether one exists for ChargeOver and whether it covers the events you need. Compare the two on your actual use case, the modules available and how your team prefers to work, rather than on reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations