Resources · Make integration

Hotmart Make integrationAutomate Hotmart with Make.

Your Hotmart subscriptions can be handled from other tools, without a line of code. The Hotmart Make integration gives you 5 modules: 3 actions and 2 searches. This page explains each one, walks through the connection and builds a first scenario with you.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Hotmart Make integration do for you?

The Hotmart Make integration links your Hotmart account to Make, a no-code tool where you chain apps together. Inside Make you build a scenario, which is the automation itself, out of modules, the small bricks that each do one job. With Hotmart, those bricks read and manage the subscriptions and purchases of your subscribers.

Cancellations handled where they arrive. A student fills in a cancellation form in another app, and Cancel a Subscription closes the matching Hotmart subscription. Your support team no longer copies the request by hand.

A second chance for a lapsed member. When a customer agrees to come back, Reactivate and Charge a Subscription restarts the plan and charges it in one step.

A clear view of who pays for what. List Subscriptions pulls every subscription into a sheet or a CRM, and Get a Subscribers' Purchases shows what one buyer has bought before you answer a ticket. If you keep that data in a base, the Airtable Make integration is a natural next stop.

What the integration does not do: Hotmart has no trigger in Make, so nothing starts on its own when a sale happens. Your scenario opens on another app or on a schedule, and anything the five modules skip goes through Make an API Call. Hotmart may also be covered in n8n; the n8n vs Make comparison helps you weigh both, and our Make review gives the full picture of the tool.

Connect

How do you connect your Hotmart account to Make?

  1. 01

    Collect your three Hotmart credentials

    In your Hotmart account, gather three values: the Client ID, the Client Secret and the Basic Token. Keep them in a safe note for a moment, Make asks for all three together.

  2. 02

    Open a Hotmart module in Make

    In a scenario, click the + and search for Hotmart, then pick any of its modules. Click Create a connection: a window opens with the fields for your credentials.

  3. 03

    Paste the values and save

    Paste the Client ID, the Client Secret and the Basic Token, then save. That connection is your Hotmart account linked to Make once; every other Hotmart module of your scenarios reuses it.

First scenario

Your first scenario: cancel a subscription on request

GoalWhen a customer asks to cancel through a form in another app, Make cancels the matching Hotmart subscription.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + to add the first module. That first brick is the form app where your cancellation requests land.

  2. 02

    Add the Hotmart action

    Click the + on the right of the form module, search for Hotmart and choose Cancel a Subscription. Select the connection you created, or click Create a connection if you skipped that part.

  3. 03

    Map the request to the subscription

    Fill the module fields with data from the form module. Each request travels as a bundle, one item passed from a module to the next, so the answer of one customer lands in the right field.

  4. 04

    Test with Run once

    Click Run once, then send a test request from a subscription you control. Open each module to read the bundles it received and confirm the right subscription was targeted.

  5. 05

    Switch the scenario on

    Set the schedule on the first module, every 15 minutes by default, and turn the scenario on. From then on, each new request is picked up without you.

Modules

What each Hotmart module does

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

Actions

3 modules
Hotmart1

Cancel a Subscription

Action

In MakeCancels a subscription.

This module ends a Hotmart subscription for you, so a customer who asked to leave is handled without a trip to your Hotmart dashboard. It is the natural last step of any cancellation flow.

When to use it
a cancellation request reaches you through a form, an email or your help desk, and you want Hotmart to follow automatically.
Watch out
check the mapping on a subscription you control first, because a cancellation aimed at the wrong customer hits a real paying member.
Hotmart2

Reactivate and Charge a Subscription

Action

In MakeReactivates and charges a subscription.

Bring a lapsed member back in a single step: the module switches a subscription on again and charges it right away. You skip the manual reactivation in Hotmart.

When to use it
a customer replies yes to a win-back offer, or your team approves a comeback in its CRM.
Watch out
the charge happens as part of the reactivation, so only place this module after a clear agreement from the buyer.
Hotmart3

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Here is your way around the short list of modules. It calls any endpoint of the Hotmart API with the connection you already set up, so you reach data the four other modules do not cover.

When to use it
you need a piece of Hotmart that has no dedicated module, and the Hotmart API documentation lists the endpoint.
Watch out
you write the request yourself, so read that documentation before you build.

Searches

2 modules
Hotmart4

List Subscriptions

Search

In MakeLists all subscriptions.

Get the whole picture of your recurring revenue: the module returns the subscriptions of your account, each one as its own bundle that the next module can write to a sheet or a CRM.

When to use it
you want a report of active and cancelled members, or you need to feed a dashboard.
Watch out
a search can return zero, one or many bundles, and every bundle that reaches a following module costs an operation, one run of that module counted on your plan.
Hotmart5

Get a Subscribers' Purchases

Search

In MakeReturns information about a subscribers' purchases.

Know what a buyer owns before you answer them. The module returns the purchases of one subscriber, so support can see the course or plan in question at a glance.

When to use it
a support ticket arrives and you want the buyer's history added to it automatically.
Watch out
it is a search, so a subscriber with several purchases sends several bundles; the next module then runs once for each of them.
Need help

Need help automating Hotmart with Make?

A person reads every message.

FAQ

Questions about the Hotmart Make integration

01Is the Hotmart Make integration free?
Yes. Hotmart is a standard app in Make, available from the Free plan. The Free plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in operations each month, so the number of subscriptions you process matters more than the number of scenarios.
02What do you need to connect Hotmart to Make?
You need a Hotmart account and three values taken from it: the Client ID, the Client Secret and the Basic Token. In Make, open any Hotmart module, click Create a connection and paste the three values. The Make documentation lists no other prerequisite. Once saved, the connection is shared by every Hotmart module, so you only do this setup once, then reuse it in each new scenario you build around your subscriptions.
03Can a Hotmart scenario in Make start when a sale happens?
No, not from Hotmart itself: the app has no trigger module in Make, so it cannot start a scenario on its own. You have two ways to start anyway. Open the scenario on another app, for example a form or a help desk, and let its trigger launch the Hotmart modules. Or open it on a schedule set on the first module, every 15 minutes by default, with a search such as List Subscriptions at the start of the chain.
04What if a Hotmart action is missing from Make?
Use Make an API Call. It reaches any endpoint of the Hotmart API with the connection you already have, so you are not limited to the four ready-made modules. The Hotmart API documentation lists the available endpoints; pick the one you need and build the request in the module. The Make documentation gives no numeric limit for this app, so the only constraints to plan for are those of your Make plan.
05Should you use Make or n8n for Hotmart?
It depends on the tool your team already works in. In Make, Hotmart comes with five modules focused on subscriptions and purchases, plus Make an API Call for the rest, and you build everything in a visual editor. The same app often has an n8n node too, so check what that node offers before choosing. Compare the actions each side covers for your case, then pick the tool where the rest of your automations already live.