Resources · Make integration

ChartMogul Make integrationAutomate ChartMogul with Make.

Your billing data lives in several tools, and ChartMogul only knows what it receives. The ChartMogul Make integration gives you 27 modules to push customers, plans and invoices in, or read them back out. This guide connects your account and walks you through a first scenario.

Try the ChartMogul integration on MakeSee the 27 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ChartMogul Make integration do for you?

The ChartMogul Make integration links your ChartMogul account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick that creates, reads, updates or lists something. With it, the customers, plans and invoices ChartMogul tracks can be fed from your other apps without writing an API script.

Feed invoices from a tool ChartMogul does not read. When a sale lands in your billing or checkout app, Create a Customer and Import an Invoice send it to ChartMogul, and Import an Invoice Transaction adds the transaction linked to that invoice.

Keep your catalog in step. A new offer on your pricing page becomes a record through Create a Plan, gets filed under Create a Plan Group, and Update a Plan follows the changes you make later.

Send ChartMogul records elsewhere. List Customers or List Customer's Subscriptions return one bundle per record (a bundle is one item passed to the next module), which you can drop into a spreadsheet or a CRM.

What Make does not do here: ChartMogul has no trigger, so nothing starts a scenario from inside ChartMogul, and List Invoices only returns invoices created through the API. Make also notes that the official module documentation is AI-generated, so check important details against ChartMogul's own docs. If you are weighing tools, the n8n vs Make comparison lays out the criteria, Make pricing explains how operations are counted, and Make training covers the editor from scratch.

Connect

How do you connect ChartMogul to Make?

  1. 01

    Copy your API key from ChartMogul

    In ChartMogul, open Profile, click View Profile, then API Keys in the sidebar. Copy the key shown in the API Keys table. You need an active ChartMogul account to reach this page.

  2. 02

    Add a ChartMogul module in Make

    Open your scenario, click the + and search for ChartMogul. Pick any module, then click Create a connection. A connection is your ChartMogul account linked to Make once. You can type a label in Connection name if you manage several accounts.

  3. 03

    Paste the key and save

    Paste the credentials you copied into the connection window and confirm. From then on, every ChartMogul module in every scenario can reuse this connection without asking for the key again.

First scenario

Your first scenario: turn a payment into ChartMogul data

GoalWhen a payment is recorded in your billing tool, Make creates the matching customer in ChartMogul and imports the invoice.

  1. 01

    Start a new scenario

    From the Scenarios page, create a new scenario and click the +. Since ChartMogul has no trigger, the first module is the one from your billing or checkout app that reports a new payment.

  2. 02

    Add Create a Customer

    Click the + on the right of the first module, search ChartMogul and choose Create a Customer. Select your connection, or click Create a connection if this is your first ChartMogul module.

  3. 03

    Map the buyer's details

    The customer is created under a data source, so pick the one that holds your imported data. Then map the buyer's details from the first module into the customer fields Make shows you.

  4. 04

    Attach the invoice

    Add Import an Invoice after it. Map the customer the previous module just created, then the invoice details the payment app sent, so the invoice lands on the right record.

  5. 05

    Test with Run once

    Click Run once and trigger a test payment. Each module shows the bundles it received; open them to confirm the customer and the invoice appear in ChartMogul as expected.

  6. 06

    Schedule it and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Save, then switch the scenario on.

Modules

Every ChartMogul module in Make, explained

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

ChartMogul1

Add a Custom Attribute to a Customer

Action

In Make“Adds a custom attribute to an existing customer.”

Stamps an existing ChartMogul customer with an extra piece of context you track somewhere else, like the acquisition channel or the account owner, so that detail sits right next to their subscription history.

When to use it
after a deal closes in your CRM and you want the rep's name recorded on the customer.
Watch out
the customer has to exist already; find it first with List Customers.
ChartMogul2

Cancel a Customer's Subscription

Action

In Make“Cancels a subscription that was generated from an imported invoice.”

Ends a subscription in ChartMogul so the churn shows up there without anyone editing records by hand. It only works on subscriptions that came from an imported invoice.

When to use it
a customer cancels in a billing tool you feed through Import an Invoice, and ChartMogul needs to know.
Watch out
fetch the subscription with List Customer's Subscriptions first to target the right one.
ChartMogul3

Create a Customer

Action

In Make“Creates a customer object in ChartMogul under the specified data source.”

Adds a brand new customer record to ChartMogul, attached to the data source you pick. It is usually the first write in any scenario that imports billing data.

When to use it
a first purchase arrives from your checkout app and the buyer is not in ChartMogul yet.
Watch out
running it for a returning buyer can create a duplicate; check with List Customers before it if repeat buyers are common.
ChartMogul4

Create a Data Source

Action

In Make“Creates a data source object for importing data into ChartMogul.”

Sets up a new data source, the container ChartMogul uses to receive imported customers, plans and invoices. Every import-based scenario needs one to point at.

When to use it
you connect a new billing system and want its records kept apart from the others.
Watch out
this is a setup step, so run it once and reuse the result rather than placing it inside a recurring flow.
ChartMogul5

Create a Plan

Action

In Make“Creates a plan object in ChartMogul under the specified data source.”

Registers a pricing plan in ChartMogul under a chosen data source, so the invoices you import later can reference it.

When to use it
your team launches a new offer in the billing tool and you want ChartMogul to know it before the first invoice comes in.
Watch out
use the same data source as the invoices that will point to this plan.
ChartMogul6

Create a Plan Group

Action

In Make“Creates a plan group object in ChartMogul.”

Creates a group that bundles several plans together, handy when monthly and yearly versions of one offer should be read as a single product.

When to use it
a new product line arrives with several price points and you want them grouped from the start.
Watch out
the plans themselves come from Create a Plan; build them first so you have something to put in the group.
ChartMogul7

Delete a Customer

Action

In Make“Deletes the specified customer object and all its associated data.”

Removes a customer from ChartMogul along with every piece of data attached to it. Use it to honor an erasure request or wipe a test record.

When to use it
your support tool logs a data deletion request and ChartMogul must follow.
Watch out
there is no undo, and the attached data goes with it; add a filter so only the intended customer reaches this module.
ChartMogul8

Delete a Data Source

Action

In Make“Deletes the specified data source object and all its associated data.”

Erases a whole data source together with everything imported into it. It is the heaviest cleanup module in the list.

When to use it
you retire a billing system or clear out a sandbox you used while testing imports.
Watch out
every customer, plan and invoice tied to that source disappears too, so confirm the source with Get a Data Source before the delete runs.
ChartMogul9

Delete an Invoice

Action

In Make“Deletes the specified invoice object and all its associated data.”

Takes one invoice out of ChartMogul, with the data linked to it, so a wrong import stops affecting your figures.

When to use it
an invoice was voided in the billing tool, or a scenario test pushed a duplicate you need to remove.
Watch out
deletion is permanent; look the invoice up with Get an Invoice first and make sure you hold the right identifier.
ChartMogul10

Delete a Plan

Action

In Make“Deletes the specified plan object from your ChartMogul account.”

Removes a plan from your ChartMogul account, the tidy way to clear offers that were created by mistake.

When to use it
a plan was duplicated during an import, or an offer was dropped before any customer bought it.
Watch out
deletion is permanent, so check the plan with Get a Plan or List Plans before you run it.
ChartMogul11

Delete a Plan Group

Action

In Make“Deletes the specified plan group object from your ChartMogul account.”

Removes a plan group from ChartMogul when a grouping no longer matches how you sell.

When to use it
you restructure your offers and the old bundle of monthly and yearly plans should go.
Watch out
confirm the group with Get a Plan Group first, since a scenario can map the wrong identifier as easily as the right one.
ChartMogul12

Get a Customer

Action

In Make“Retrieves a customer object from your ChartMogul account.”

Fetches one customer record from ChartMogul when you already know which one you want, and hands its details to the next module.

When to use it
a support ticket comes in and you want the customer's ChartMogul data added to it.
Watch out
it needs the customer's identifier; if you only have an email or a name, start with List Customers instead.
ChartMogul13

Get a Data Source

Action

In Make“Retrieves a data source object from your ChartMogul account.”

Reads a single data source so a scenario can check which one it is about to write into or clean up.

When to use it
as a safety check before Delete a Data Source, or to confirm the source a new plan should go under.
Watch out
you need the source's identifier; List Data Sources shows them all if you do not have it at hand.
ChartMogul14

Get an Invoice

Action

In Make“Retrieves an invoice object from your ChartMogul account.”

Pulls the details of one invoice out of ChartMogul, ready to map into an email, a ticket or an accounting tool.

When to use it
finance asks about a specific charge and you want the invoice attached to the request automatically.
Watch out
it reads one invoice by identifier; to browse several, List Invoices is the better fit.
ChartMogul15

Get a Plan

Action

In Make“Retrieves a plan object from your ChartMogul account.”

Returns one plan from ChartMogul so you can reuse its details further down the scenario, for example before updating it.

When to use it
a price changes in your billing tool and you want to compare it with what ChartMogul has on file.
Watch out
you need the plan's identifier; List Plans gives you the full catalog if you are unsure.
ChartMogul16

Get a Plan Group

Action

In Make“Retrieves a plan group object from your ChartMogul account.”

Reads one plan group so the scenario knows how an offer is packaged in ChartMogul before acting on it.

When to use it
before Update a Plan Group or Delete a Plan Group, to check you have the group you think you have.
Watch out
it reads a single group from its identifier; there is no listing module for groups in this app, so keep those identifiers somewhere handy.
ChartMogul17

Import an Invoice

Action

In Make“Creates invoices for a given API customer.”

Sends invoices for a given customer into ChartMogul. This is the module that turns sales from a tool ChartMogul does not read natively into subscription data.

When to use it
each time your checkout or invoicing app records a sale, right after Create a Customer or a customer lookup.
Watch out
the customer must exist first, and it must be one created through the API.
ChartMogul18

Import an Invoice Transaction

Action

In Make“Creates a transaction object for an invoice imported using the Import API.”

Attaches a transaction to an invoice that was already imported through the API, so ChartMogul sees what happened to that invoice after it was sent.

When to use it
your payment provider reports a new event on a charge whose invoice already sits in ChartMogul.
Watch out
it only works on invoices that came in through Import an Invoice or the Import API, not on invoices from other sources.
ChartMogul19

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the ChartMogul API with the connection you already set up, so you are not stuck when no listed module does what you need.

When to use it
you need a ChartMogul operation that none of the other listed modules covers.
Watch out
you describe the request yourself, so keep ChartMogul's API reference open while you fill it in.
ChartMogul20

Update a Customer

Action

In Make“Updates certain modifiable attributes of a customer object in your ChartMogul account.”

Changes the editable details of a customer already in ChartMogul, so a company rename or a new contact does not leave stale data behind.

When to use it
a customer edits their profile in your app or CRM and ChartMogul should follow.
Watch out
only certain attributes can be modified with this module; find the customer first with List Customers so you edit the right record.
ChartMogul21

Update a Plan

Action

In Make“Updates a plan object in your ChartMogul account.”

Edits a plan that already lives in ChartMogul, which keeps your catalog aligned when an offer changes name or details.

When to use it
marketing renames an offer in the billing tool and the reports should show the new label.
Watch out
target the plan by its identifier, taken from Get a Plan or List Plans, rather than typing it by hand.
ChartMogul22

Update a Plan Group

Action

In Make“Updates a plan group object in your ChartMogul account.”

Modifies an existing plan group, for instance to rename it when a product line is rebranded.

When to use it
your offer structure changes but the group itself should stay, with a new name or new content.
Watch out
check the group with Get a Plan Group before editing, so the scenario does not overwrite a neighboring group because of a mapping slip.
ChartMogul23

List Customers

Search

In Make“Returns a list of all customer objects in your ChartMogul account.”

Returns the customers in your ChartMogul account as separate bundles, so each one can go through the following modules on its own.

When to use it
copying your customer base into a spreadsheet, or finding a customer before Update a Customer.
Watch out
every bundle that moves on costs operations in the next modules, so add a filter right after it when you only need a few customers.
ChartMogul24

List Customer's Subscriptions

Search

In Make“Returns a list of subscription objects for a given customer.”

Gives you every subscription attached to one customer, one bundle each, which is the view you need before changing any of them.

When to use it
before Cancel a Customer's Subscription, or to show an account manager what a client pays for.
Watch out
it works customer by customer, so pass it the identifier from Get a Customer or List Customers.
ChartMogul25

List Data Sources

Search

In Make“Lists all data source objects in your ChartMogul account.”

Shows all the data sources in your ChartMogul account, useful when a scenario has to pick where to send an import.

When to use it
you run several billing systems and want to check which sources exist before creating customers or plans.
Watch out
it can return zero, one or several bundles; if you only need one source, add a filter so later modules do not run for each.
ChartMogul26

List Invoices

Search

In Make“Returns a list of invoice objects created using the API in your ChartMogul account.”

Returns the invoices that were created through the API in your ChartMogul account, one bundle per invoice.

When to use it
reconciling what your scenarios imported against your billing tool, or exporting that list to a spreadsheet.
Watch out
only invoices pushed through the API appear here, so an empty result does not mean the account holds no invoices at all.
ChartMogul27

List Plans

Search

In Make“Returns a list of plan objects in your ChartMogul account.”

Pulls your whole ChartMogul plan catalog, one bundle per plan, so you can compare it with the offers in your billing tool.

When to use it
checking for missing or duplicated plans before a big import, or feeding a pricing sheet.
Watch out
each plan becomes its own bundle; add an aggregator or a filter after it if the next step only needs a summary.
Need help

Need help automating ChartMogul with Make?

A person reads every message.

FAQ

ChartMogul and Make: common questions

01Is the ChartMogul Make integration free?
Yes, on the Make side. ChartMogul is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs them every 15 minutes at the shortest, caps each run at 5 minutes and files at 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift the scenario limit and allow a 1 minute interval. Every module execution counts as an operation, which is the unit Make bills on. Your ChartMogul subscription is separate and set by ChartMogul.
02What do you need to connect ChartMogul to Make?
An active ChartMogul account and its API key. In ChartMogul, go to Profile, click View Profile, then API Keys in the sidebar and copy the key from the table. In Make, add any ChartMogul module, click Create a connection, optionally name it, and paste the credentials. The connection is then shared by all ChartMogul modules, so you set it up once. No developer account and no extra app to install are mentioned in the official documentation.
03Can ChartMogul start a Make scenario on its own?
No. ChartMogul has no trigger in Make, so nothing inside ChartMogul can launch a scenario. You have two ways around it. Start the scenario with a module from another app, typically the billing or checkout tool where a payment happens, and let the ChartMogul modules follow. Or put a ChartMogul search such as List Customers first and let Make run it on a schedule, every 15 minutes by default, down to 1 minute on paid plans. Either way, the first module decides when the rest runs.
04What if a ChartMogul module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the ChartMogul API with the connection you already have, so you do not need a second setup. You write the request yourself, which asks for a bit more care than a ready-made module. Keep one more point in mind: Make states that the module documentation for this app is AI-generated and may contain mistakes, so check important behavior against ChartMogul's own API documentation before relying on it in production.
05Should you use Make or n8n for ChartMogul?
It depends on what your team already runs. On Make, ChartMogul offers 27 modules covering customers, subscriptions, plans, plan groups, data sources and invoices, plus Make an API Call for the rest, with no trigger. n8n often has a node for the same app, so the practical test is to compare the operations each side lists against the flows you need. Neither choice is universally better. If you already build in Make, staying there keeps every scenario and connection in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations