Resources · Make integration

Memberspot Make integrationAutomate Memberspot with Make.

Can a sale in one tool open a course in Memberspot without anyone touching it? The Memberspot Make integration gives you 8 action modules to grant, revoke or delete access and to tag members. This page walks course creators through the connection and a first working scenario.

Try the Memberspot integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Memberspot Make integration do for you?

The Memberspot Make integration lets Make manage who gets into your courses. In Make you build a scenario, the automation itself, made of modules chained one after the other, each one a single brick. Here every Memberspot module is an action: it opens, closes or cleans up a member's access when something happens elsewhere.

Enroll buyers without manual work. A sale lands in your checkout or payment app, and Grant Access gives the buyer the course. If that person is not a member yet, Memberspot creates the account on the spot.

Pause access and keep the progress. When a subscription stops in your billing tool, Revoke Access closes the course but keeps what the member already completed, so a returning customer picks up where they left off. Revoke Order Access does the same for one order ID.

Clean up for good. After a refund or a deletion request, Delete Access, Delete Order Access or Delete Users remove access or the member entirely. Set Users Custom Property Values adds labels you can use to segment members.

Memberspot has no trigger in Make, so the scenario always starts from another app or from a schedule. Anything the listed modules skip can go through Make an API Call. The same app often exists in n8n too; the n8n vs Make comparison lays out the differences, and the Make pricing page explains how operations are counted.

Connect

How do you connect Memberspot to Make?

  1. 01

    Copy your API key

    In your Memberspot dashboard, open the area where API integrations are managed and copy the API key shown there. You need an active Memberspot account for this, so check your plan before you start.

  2. 02

    Add a Memberspot module

    In your Make scenario, add any Memberspot module and click Create a connection. A connection is your Memberspot account linked to Make once, then reused by every Memberspot module you add.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like, it is optional. Then paste the API key you copied and confirm. Make can now act on your members.

First scenario

Build your first scenario: enroll a buyer

GoalWhen a customer pays in your shop, Make opens the matching Memberspot course and labels the member.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the trigger of the app where your sales happen.

  2. 02

    Add Grant Access

    Click the + on the right of that first module, search Memberspot and choose Grant Access. Link your account with Create a connection, then map the buyer data from the sale.

  3. 03

    Label the new member

    Add Set Users Custom Property Values after it and map the same buyer, plus a value such as the product bought. Your member list then shows where each person came from.

  4. 04

    Test with Run once

    Click Run once and look at the bundles, the items each module received. Check in Memberspot that the test buyer really has the course before going further.

  5. 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 counts as one operation on your Make plan.

Modules

Memberspot modules in Make, one by one

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

Memberspot1

Delete Access

Action

In Make“Deletes the access of a member (member progress in the courses will be deleted).”

Removes a member's access to a course and wipes the progress they made in it, leaving a clean slate.

When to use it
a refund is confirmed and the buyer should lose the course along with any trace of their lessons, for example when you restart a cohort from zero.
Watch out
progress cannot be recovered afterwards; if you only want to pause access, pick Revoke Access instead.
Memberspot2

Delete Order Access

Action

In Make“Deletes access for a specific order ID.”

Cancels the access tied to one specific order ID, so only what that purchase unlocked disappears and other purchases stay intact.

When to use it
a customer bought two offers and refunds only one; map the order ID from your payment app and the other course is left alone.
Watch out
map the order ID straight from the sale record rather than typing it, so the right purchase is cancelled.
Memberspot3

Delete Users

Action

In Make“Delete users by mail”

Erases members from Memberspot using their email address, which is the tidy answer when someone asks you to remove their account completely.

When to use it
a data deletion request arrives through your support form and you want the member gone without opening the dashboard.
Watch out
this is final; test with Run once on a dummy address before switching the scenario on.
Memberspot4

Grant Access

Action

In Make“Grants access to a course (when the member is not existing, the member will be created).”

Gives a person access to a course and, if they are not a member yet, creates their Memberspot account in the same step.

When to use it
right after a payment or a signup in another app, so the buyer can open the course without waiting for you.
Watch out
run it once per buyer; placing it after a module that returns several bundles will enroll every one of them.
Memberspot5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Memberspot API with the connection you already set up, for the cases the seven ready-made modules do not cover.

When to use it
you need a Memberspot operation that has no dedicated module and you are comfortable reading API documentation.
Watch out
you write the request yourself, so check the Memberspot API reference for the path and the expected body.
Memberspot6

Revoke Access

Action

In Make“Revokes a member's access to a course (member progress in the courses will not be deleted).”

Closes a member's access to a course while keeping the progress they already made, so nothing is lost if they come back.

When to use it
a subscription payment fails or a membership is paused, and you want to lock the course until the customer renews.
Watch out
this only locks the course; if the member's progress should go too, Delete Access is the module you want.
Memberspot7

Revoke Order Access

Action

In Make“Revokes access for a specific order ID.”

Suspends the access linked to one order ID, keeping progress, which suits buyers who hold several offers at once.

When to use it
one installment of a payment plan bounces and only the course from that order should be locked for now.
Watch out
progress stays in place here; to remove that order's access for good, choose Delete Order Access.
Memberspot8

Set Users Custom Property Values

Action

In Make“Sets the custom properties to a user.”

Writes values into the custom properties of a member, so each profile carries the details you decided to track, ready for segmenting later.

When to use it
straight after Grant Access, to record which product or campaign brought the member in.
Watch out
test with Run once and open the member profile in Memberspot to confirm the values landed where you expected.
Need help

Need help automating Memberspot with Make?

A person reads every message.

FAQ

Memberspot and Make: common questions

01Is the Memberspot Make integration free?
Yes, on the Make side. Memberspot is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs and up to 5 minutes per run. Paid plans lower the interval to 1 minute and lift the active scenario cap. You still need an active Memberspot account with its own subscription, which Make does not cover. Each module run on one bundle counts as one operation, so a scenario that enrolls one buyer and sets one property uses two.
02What do you need to connect Memberspot to Make?
An active Memberspot account and its API key. Open your Memberspot dashboard, go to the section that manages API integrations and copy the key. In Make, add a Memberspot module, click Create a connection, optionally name it, paste the key and save. The connection is then shared by every Memberspot module in your scenarios. There is no webhook step either, since every Memberspot module is an action. Name the connection after the account if you run more than one school.
03Can Memberspot start a Make scenario in real time?
No, Memberspot has no trigger module in Make, so it cannot start a scenario by itself. Begin with a trigger from another app, such as your checkout or form tool; if that app offers an instant trigger, it calls Make through a webhook as soon as something happens. You can also start from a plain schedule, every 15 minutes by default, and add the Memberspot actions after it. Either way, Memberspot joins the flow as the second or third module, which is exactly how the first scenario on this page is built.
04What if a Memberspot module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Memberspot API with the connection you already have, so actions without a ready-made module stay possible. You write the request yourself, which means reading the Memberspot API reference. Make also notes that its Memberspot documentation is AI-generated, so confirm important details with Memberspot directly. If you only need to pause or remove access, the eight listed modules already cover grant, revoke and delete, per member or per order ID.
05Should you use Make or n8n for Memberspot?
It depends on the tool you already run. Memberspot has 8 action modules in Make, including Make an API Call, and the same app often has an n8n node as well. If your other automations live in Make, keeping Memberspot there avoids splitting your workflows. The n8n vs Make comparison linked above lays out the criteria to decide. In practice, the choice rests on where your team already works rather than on the app itself.
Same platform

Other docs you might need on this stack.

Browse all integrations