CartMango Make integrationAutomate CartMango with Make.
Can Make work with your CartMango sales and subscriptions? The CartMango Make integration gives you 6 action modules, from new sales to expired subscriptions. This guide shows how to connect your account, test each module and build a first scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the CartMango Make integration do?
The CartMango Make integration links your CartMango account to Make, a no-code automation tool. You then place CartMango modules inside a scenario (the automation you build in Make, a chain of modules) and pass sales and subscription data to the rest of your tools without writing code.
Six modules are available, all typed as actions: New sale, Recurring subscription payment, Sale refunded, Subscription canceled, Subscription expired, plus Make an API call. A module is one brick of a scenario. Because none of them is a trigger, a CartMango scenario always starts from something else: the schedule of Make or a trigger from another app.
Three setups make sense for a shop that sells online. A sales follow-up: another app starts the scenario, and the New sale module brings the CartMango side into the flow. A retention check: Subscription canceled and Subscription expired sit next to each other in a scenario that feeds your customer list. A refund log: Sale refunded passes its data on to a sheet or a message for your finance team.
Be clear about the limits. Make itself says its CartMango documentation is incomplete, because too little public information exists about the app. No module comes with an official description, so the only reliable way to learn what each one returns is to add it and click Run once. When a listed module does not cover your case, Make an API call reaches the rest of the CartMango API with the same connection.
If you are new to the editor, the Make training walks through the basics, and the n8n vs Make comparison helps if you are still choosing a tool. Stuck on an error? Open Make troubleshooting.
How do you connect CartMango to Make?
- 01
Add a CartMango module
In your scenario, click the + and search for CartMango. Pick any of its modules, then click Create a connection. A connection is your CartMango account linked to Make once, then reused by every CartMango module.
- 02
Name the connection
Giving the connection a name is optional, but it helps when you run several shops or a test account next to the live one. A clear label such as the store name avoids picking the wrong account later.
- 03
Authorize and save
Depending on what CartMango asks for, either approve Make on the CartMango page that opens, or paste the key CartMango gives you. Then click Save, and the module is ready to be filled in.
Your first scenario with CartMango
GoalWhen another app starts your scenario, Make runs the CartMango New sale module and hands its data to the next step.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the + to add the first module. Since CartMango has no trigger, this first module comes from another app you already use.
- 02
Add New sale
Click the + on the right of that first module, search for CartMango and choose New sale. Click Create a connection to link your account, then fill the fields Make shows.
- 03
Add Make an API call
Click the + on the right of New sale and add Make an API call for a CartMango action with no module of its own. Map values from New sale instead of typing them, so each bundle (one item passing between modules) carries its own data.
- 04
Test with Run once
Click Run once to execute the scenario one time. Open the bubble above New sale to read the bundle it received and returned: this is the only sure way to see what the module gives you.
- 05
Schedule and switch 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 counts on your plan.
What each CartMango module does
CartMango gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Make an API call
ActionIn the docs onlyMake an API call gives you access to any CartMango API endpoint from your scenario, reusing the connection you already created. It is your way out when the five named modules do not cover a task.
New sale
ActionIn the docs onlyNew sale brings a CartMango sale into your scenario so later modules can use it. Make lists it as an action and publishes no description, so the name is your main clue about its content.
Recurring subscription payment
ActionIn the docs onlyJudging by its name, Recurring subscription payment turns the renewals of your subscribers into data a scenario can pass on. It is the module to look at when your CartMango revenue comes from plans rather than single orders.
Sale refunded
ActionIn the docs onlySale refunded lets your scenario deal with the CartMango orders that were paid back. Pick it rather than New sale when the money went the other way and you need to correct a total or warn someone.
Subscription canceled
ActionIn the docs onlySubscription canceled puts the customers who stopped their plan within reach of your scenario. That is the moment a retention email or a note to your support team can still make a difference.
Subscription expired
ActionIn the docs onlySubscription expired covers the plans that reached their end, which is different from a customer actively canceling. Use it to keep access lists and customer tags aligned with what CartMango knows.
Need help automating CartMango with Make?
A person reads every message.
