Resources · Make integration

MemberPress Make integrationAutomate MemberPress with Make.

Every signup, renewal and refund in MemberPress can start an automation on its own. The MemberPress Make integration gives you 38 modules, 11 of them instant triggers. This guide is for membership site owners: connect the account, build a first scenario, then pick the right module for each job.

Try the MemberPress integration on MakeSee the 38 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the MemberPress Make integration let you automate?

The MemberPress Make integration links your membership site to Make, a tool where you chain apps together without writing code. Each chain is a scenario, and each brick in it is a module. MemberPress brings 38 of them: 11 triggers that fire when members, subscriptions or payments change, plus actions and searches on the same records.

Clean up after a refund. Watch Transactions Refunded fires the moment a payment is refunded, and Cancel a Subscription closes the plan tied to it, so nobody keeps access they no longer pay for.

Rescue a failed payment. A course creator can start from Watch Transactions Fail, pull the member's details with Get a Member, and hand them to the email or CRM app the team already uses to send a friendly reminder.

Hand out welcome coupons. When Watch Members Complete Sign Up fires, Create a Coupon generates a code for that new member, ready to drop into a welcome message.

Know the limits before you start. There is no scheduled trigger here: all 11 react on their own through a webhook. Most actions work on a record ID, so a scenario usually gets that ID from a trigger or a search module first. Anything the list misses goes through Make an API Call. The Make review helps if you are still weighing the tool, and Make pricing explains how operations are counted.

MemberPress often has an n8n node as well; the n8n vs Make comparison lays out the differences between the two tools.

Connect

How do you connect MemberPress to Make?

  1. 01

    Copy your API key

    In your website dashboard, open the MemberPress menu, click Developer, then the REST API tab. The API key sits right there on screen. Copy it; Make needs it once, and every MemberPress module reuses it afterwards.

  2. 02

    Add a MemberPress module

    In a Make scenario, add any MemberPress module and click Create a connection. A connection is your MemberPress account linked to Make. The Connection name field is optional, but a clear name helps when you run several sites.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen, then save. From now on, the connection appears in the dropdown of every MemberPress module you add, so there is nothing to retype.

First scenario

Build your first scenario: cancel access after a refund

GoalWhen a payment is refunded in MemberPress, Make cancels the matching subscription.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to place the first module. That first module decides when everything else starts.

  2. 02

    Pick the refund trigger

    Search for MemberPress, choose Watch Transactions Refunded, click Create a webhook, then Create a connection with your API key. The lightning badge on the module means MemberPress will call Make itself.

  3. 03

    Test with Run once

    Click Run once, then refund a test payment on your site. Read what the trigger received: each bundle, one item passed between modules, shows what the refund carried. Check where the subscription ID appears.

  4. 04

    Add the cancel action

    Click the + on the right of the trigger and add Cancel a Subscription. In its ID field, map the subscription ID you spotted in the refund bundle instead of typing a fixed value.

  5. 05

    Run it again, then switch on

    Run once with another test refund and confirm the subscription shows as cancelled in MemberPress. Then switch the scenario on: from that point, each refund triggers it without anyone watching.

Triggers

Triggers: what starts a MemberPress scenario

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

MemberPress1Watch Members Accounts Updated

Watch Members Accounts Updated

Instant trigger

In Make“Triggers when account of a member has been updated.”

Keeps your other tools in step with MemberPress: whenever a member's account details change, this trigger sends the updated record to your scenario.

How it fires
instant; MemberPress calls Make through a webhook as soon as the account changes, no polling involved.
When to use it
a member edits their profile and your CRM or newsletter list should show the same data without a manual copy.
Watch out
if the same scenario runs Update a Member, it can wake this trigger again. Add a filter that ignores changes your own scenario made, or it runs in a loop.
MemberPress2Watch Members Complete Sign Up

Watch Members Complete Sign Up

Instant trigger

In Make“Triggers when a member has completed sign up.”

Starts your onboarding at the right moment: the trigger fires once a new member has finished signing up, not while the form is still half filled.

How it fires
instant; the webhook from MemberPress reaches Make as soon as the signup is complete.
When to use it
send the welcome sequence, add the person to a community tool, or create a welcome coupon with Create a Coupon.
Watch out
click Create a webhook before Create a connection when you add it, otherwise the trigger never hears from your site.
MemberPress3Watch Members Deleted

Watch Members Deleted

Instant trigger

In Make“Triggers when a member has been deleted.”

Tells the rest of your stack that someone is gone: each time a member is deleted in MemberPress, the scenario receives that event and can tidy up elsewhere.

How it fires
instant; MemberPress pings Make by webhook right after the deletion.
When to use it
remove the person from a mailing list, a spreadsheet of active members or a private channel so your records match.
Watch out
the member no longer exists in MemberPress, so a Get a Member placed after this trigger has nothing left to fetch.
MemberPress4Watch Subscriptions Created

Watch Subscriptions Created

Instant trigger

In Make“Triggers when a new subscription has been created.”

Catches each new subscription as it appears, which is handy to track recurring revenue or to grant access in a tool MemberPress does not manage.

How it fires
instant; a webhook from MemberPress alerts Make the moment the subscription is created.
When to use it
log the subscription in a sheet for your finance view, or notify the sales channel when someone commits to a plan.
Watch out
a subscription created from inside Make with Create a Subscription can fire this trigger too, so plan for it if both live on the same site.
MemberPress5Watch Subscriptions Pause

Watch Subscriptions Pause

Instant trigger

In Make“Triggers when a subscription has been paused.”

Flags members who press pause, so you can react before a paused plan turns into a lost one.

How it fires
instant; MemberPress calls Make through its webhook as soon as a subscription is paused.
When to use it
send a short "see you soon" message, or tag the member in your CRM so the team knows the account is on hold.
Watch out
pausing and stopping are two separate triggers here. Pair this one with Watch Subscriptions Resume if you want the whole story in one place.
MemberPress6Watch Subscriptions Resume

Watch Subscriptions Resume

Instant trigger

In Make“Triggers when a subscription has been resumed.”

Closes the loop opened by a pause: when a paused subscription comes back to life, this trigger hands the details to your scenario.

How it fires
instant; the resume event travels from MemberPress to Make by webhook right away.
When to use it
remove the on-hold tag you set earlier, restore access in an outside tool, or send a welcome-back note.
Watch out
the scenario must be switched on to hear about a resume, so activate it before you rely on it.
MemberPress7Watch Subscriptions Stop

Watch Subscriptions Stop

Instant trigger

In Make“Triggers when a subscription has stopped.”

Spots churn as it happens: the trigger fires when a subscription has stopped, giving you a chance to learn why or to cut access in other tools.

How it fires
instant; MemberPress notifies Make by webhook the moment the subscription stops.
When to use it
send an exit survey, alert the account owner, or remove the member from a paid community space.
Watch out
do not mix it up with Watch Subscriptions Pause. A stopped plan is not waiting to resume, so treat it as a real departure.
MemberPress8Watch Transactions Complete

Watch Transactions Complete

Instant trigger

In Make“Triggers when a transaction has been completed.”

Your signal that money actually came in: each completed transaction lands in the scenario with its details, ready to be recorded or celebrated.

How it fires
instant; MemberPress calls Make via webhook as soon as the payment completes.
When to use it
push the sale into your accounting sheet, trigger an invoice in another app, or post a note in the team channel.
Watch out
each completed payment is its own bundle and costs operations on every module after it, so keep the chain short on busy sites.
MemberPress9Watch Transactions Expire

Watch Transactions Expire

Instant trigger

In Make“Triggers when a transaction has expired.”

Reminds you that access is about to lapse: the trigger fires when a transaction has expired, which is often the moment to invite a renewal.

How it fires
instant; the expiry reaches Make through a MemberPress webhook as soon as it happens.
When to use it
send a renewal link, update the member's status in your CRM, or open a follow-up task for the team.
Watch out
an expired transaction is not a failed one. Build a separate scenario on Watch Transactions Fail for declined cards.
MemberPress10Watch Transactions Fail

Watch Transactions Fail

Instant trigger

In Make“Triggers when a transaction has failed.”

Gives you a head start on declined payments: the scenario receives each failed transaction, so a member hears from you before losing access.

How it fires
instant; MemberPress sends the failure to Make by webhook the moment it is recorded.
When to use it
email the member a link to update their card, or alert whoever handles billing questions.
Watch out
add Get a Member after the trigger when your message needs the member's name or email and the failure bundle does not include them.
MemberPress11Watch Transactions Refunded

Watch Transactions Refunded

Instant trigger

In Make“Triggers when a transaction has been refunded.”

Keeps refunds from slipping through the cracks: every refunded transaction reaches your scenario, so access and bookkeeping follow automatically.

How it fires
instant; MemberPress calls Make by webhook as soon as the refund is issued.
When to use it
cancel the related subscription with Cancel a Subscription, or log the refund in your finance sheet.
Watch out
test with a real refund on a test payment and read the bundle first, so you map the right ID into the next module.
Modules

Modules: what Make can do in MemberPress

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

MemberPress1

Cancel a Subscription

Action

In Make“Cancels a subscription specified by ID.”

Ends a member's recurring plan from Make, so you no longer need to open the dashboard to stop a subscription by hand.

When to use it
after Watch Transactions Refunded, or when a support ticket in another app asks for a cancellation.
Watch out
the module needs the subscription ID, so get it from a trigger or from Search Subscriptions first.
MemberPress2

Create a Coupon

Action

In Make“Creates a new coupon.”

Produces a fresh coupon in MemberPress straight from a scenario, which lets you reward an event without logging in to write the code.

When to use it
a new member completes signup, or a partner form in another app should hand out a discount.
Watch out
every run makes a new coupon, so run it from a precise trigger rather than a broad one.
MemberPress3

Create a Member

Action

In Make“Creates a new member.”

Adds a person to your MemberPress site from data that lives somewhere else, like a form tool, a CRM or a spreadsheet row.

When to use it
you sell access through another checkout or onboard a group and want each person on the site without typing them in.
Watch out
run Search Members first when the person might already exist, to avoid a duplicate account.
MemberPress4

Create a Membership

Action

In Make“Creates a new membership.”

Sets up a new membership level on your site from Make, handy when your offers are planned in a table or another tool before they go live.

When to use it
a new program is approved in your project tool and should appear in MemberPress with the same settings every time.
Watch out
this is a structural change to the site; test it with Run once before switching the scenario on.
MemberPress5

Create a Subscription

Action

In Make“Creates a new subscription.”

Opens a subscription for a member directly from a scenario, useful when the commitment starts outside MemberPress.

When to use it
a deal closes in your CRM and the client should get a recurring plan on the site without anyone re-entering it.
Watch out
Watch Subscriptions Created can fire for it as well, so keep that in mind if another scenario listens to new subscriptions.
MemberPress6

Create a Transaction

Action

In Make“Creates a new transaction.”

Records a payment in MemberPress when the money was taken somewhere else, so the member's history on your site stays complete.

When to use it
a bank transfer or an offline sale is confirmed in another app and needs to show up in MemberPress.
Watch out
a transaction written by Make can wake Watch Transactions Complete; avoid feeding it back into the same flow.
MemberPress7

Delete a Coupon

Action

In Make“Deletes a coupon specified by ID.”

Removes a coupon you no longer want in circulation, so an old promo code cannot be used again.

When to use it
a campaign is marked as finished in your planning sheet and its code should disappear from the site too.
Watch out
a deletion does not come back; use Get a Coupon or Search Coupons to confirm the right ID before it runs.
MemberPress8

Delete a Member

Action

In Make“Deletes a member specified by ID.”

Erases a member record from MemberPress when a request arrives through another channel, such as a data removal form.

When to use it
someone asks for their account to be wiped and the request is logged in your helpdesk or form tool.
Watch out
there is no undo, and Watch Members Deleted may fire right after; add a filter so only confirmed requests reach this module.
MemberPress9

Delete a Membership

Action

In Make“Deletes a membership specified by ID.”

Takes a membership level off the site by its ID, when an offer is retired for good.

When to use it
an old program is archived in your catalog tool and should vanish from MemberPress at the same time.
Watch out
this touches the structure members rely on. Fetch the level with Get a Membership and test with Run once before activating.
MemberPress10

Delete a Subscription

Action

In Make“Deletes a subscription specified by ID.”

Removes a subscription record entirely, which is different from cancelling it and leaving a trace in the history.

When to use it
a test or duplicate subscription was created by mistake and should not stay in your data.
Watch out
for a real member who leaves, Cancel a Subscription is usually the safer pick, since a deletion cannot be reversed.
MemberPress11

Delete a Transaction

Action

In Make“Deletes a transaction specified by ID.”

Wipes a transaction from MemberPress by its ID, typically to clean up a payment that should never have been recorded.

When to use it
a duplicate was created by an earlier scenario, or a test payment is polluting your reports.
Watch out
the record is gone for good, so check it with Get a Transaction first and keep this module behind a filter.
MemberPress12

Get a Coupon

Action

In Make“Retrieves a coupon specified by ID.”

Reads one coupon's details when you already know its ID, so later modules can use them in a message or a report.

When to use it
a support request mentions a coupon and you want its current settings copied into the ticket automatically.
Watch out
it only works with an ID; when you have just the code or a partial clue, start with Search Coupons.
MemberPress13

Get a Member

Action

In Make“Retrieves a member specified by ID.”

Fetches the full member record behind an ID, which fills the gaps a trigger bundle might leave, such as the email to write to.

When to use it
right after Watch Transactions Fail, to personalize the reminder you send about the declined card.
Watch out
it returns one member only; to find people by other criteria, Search Members is the right module.
MemberPress14

Get a Membership

Action

In Make“Retrieves a membership specified by ID.”

Pulls the settings of one membership level from MemberPress, so a scenario can quote them in a message or compare them with another tool.

When to use it
a welcome email should name the level the member joined, and you have its ID from the signup.
Watch out
an ID is required; list all levels with Search Memberships when you do not have one yet.
MemberPress15

Get a Subscription

Action

In Make“Retrieves a subscription specified by ID.”

Looks up a single subscription and hands its details to the next module, for example to check its status before acting.

When to use it
before Cancel a Subscription, to confirm you are about to stop the plan the refund really concerns.
Watch out
it reads, it does not change anything; pair it with Update a Subscription when a value needs fixing.
MemberPress16

Get a Transaction

Action

In Make“Retrieves a transaction specified by ID.”

Retrieves one payment by its ID, a quick way to bring amounts and status into a scenario that started in another app.

When to use it
an accounting tool sends you a transaction reference and you want the MemberPress side attached to it.
Watch out
with no ID in hand, Search Transactions is the module that can find the payment for you.
MemberPress17

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the whole MemberPress API from your scenario, with the connection you already set up, when no ready-made module covers the job.

When to use it
you need an endpoint the 38 modules do not reach and do not want to handle authentication yourself.
Watch out
you write the request yourself, so keep the MemberPress developer documentation open while you build it.
MemberPress18

Update a Coupon

Action

In Make“Updates a coupon specified by ID.”

Edits an existing coupon from Make, so a promotion can change on the site as soon as the decision is made elsewhere.

When to use it
the marketing team updates a campaign row in a shared table and the coupon should follow.
Watch out
you need the coupon's ID; find it with Search Coupons when the table only holds the code.
MemberPress19

Update a Member

Action

In Make“Updates a member specified by ID.”

Changes a member's details in MemberPress from data held in another tool, which keeps both sides aligned.

When to use it
your CRM is the reference for contact data and each correction there should reach the site.
Watch out
the change can fire Watch Members Accounts Updated; if a scenario syncs in both directions, add a filter so it does not loop.
MemberPress20

Update a Membership

Action

In Make“Updates a membership specified by ID.”

Adjusts an existing membership level without opening your site dashboard, so offer changes decided in a planning tool reach the site as they happen.

When to use it
a level is renamed or reworked in your catalog sheet and MemberPress should match it.
Watch out
members see this change directly; test it on a draft level with Run once before activating the scenario.
MemberPress21

Update a Subscription

Action

In Make“Updates a subscription specified by ID.”

Edits a live subscription by its ID, for the cases where a plan must change without being cancelled.

When to use it
a customer agrees to a change with your team in the CRM and the subscription should reflect it.
Watch out
read the current values with Get a Subscription first so you only overwrite what really changes.
MemberPress22

Update a Transaction

Action

In Make“Updates a transaction specified by ID.”

Corrects a recorded payment in MemberPress from a scenario, useful when the truth about that payment lives in your accounting app.

When to use it
a reconciliation in another tool shows a mismatch and the MemberPress record should be fixed to match.
Watch out
map the transaction ID from Search Transactions or a trigger; a typed value would always edit the same payment.
MemberPress23

Search Coupons

Search

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

Lists coupons or filters them, so you can review what is live or find the one whose ID you need for another module.

When to use it
building a report of all active promo codes, or finding a coupon before Update a Coupon.
Watch out
a search can return zero, one or many bundles, and each one runs the modules that follow.
MemberPress24

Search Members

Search

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

Finds members matching what you ask for, or lists them all, which turns MemberPress into a source you can query from any scenario.

When to use it
before Create a Member, to check whether that person already has an account on the site.
Watch out
no match means no bundle, so the rest of the chain simply does not run; plan a route for that case.
MemberPress25

Search Memberships

Search

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

Returns your membership levels, filtered or complete, a quick way to sync your offer list with a catalog or a pricing page tool.

When to use it
you need the ID of a level to feed Get a Membership or Update a Membership.
Watch out
each level found becomes its own bundle, and every following module counts one operation per bundle.
MemberPress26

Search Subscriptions

Search

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

Pulls subscriptions that match your criteria, or the full list, so you can audit plans or locate one without knowing its ID.

When to use it
a refund bundle lacks the subscription ID and you must find it before Cancel a Subscription.
Watch out
a broad search may hand back many subscriptions at once; narrow it before chaining a cancel or delete action.
MemberPress27

Search Transactions

Search

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

Brings back payments matching a filter, or every one of them, which is the starting point for reports and reconciliations.

When to use it
exporting payments to a spreadsheet, or finding a transaction ID for Update a Transaction.
Watch out
on a busy site the list can grow long, and each result spends operations downstream; filter as tightly as you can.
Need help

Need help automating MemberPress with Make?

A person reads every message.

FAQ

MemberPress and Make: frequent questions

01Is the MemberPress Make integration free?
Yes, on the Make side. MemberPress is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Your MemberPress subscription is separate, and you need an active account for the connection to work.
02What do you need to connect MemberPress to Make?
An active MemberPress account and its API key. You find the key in your website dashboard: MemberPress menu, then Developer, then the REST API tab. In Make, add a MemberPress module, click Create a connection, give it a name if you like, and paste the key. For a trigger, Make first asks you to click Create a webhook. The connection is then reused by every MemberPress module in your scenarios.
03Do MemberPress triggers in Make fire in real time?
Yes. All 11 MemberPress triggers are instant: MemberPress calls Make through a webhook as soon as a member signs up, a subscription changes or a payment completes, fails, expires or is refunded. There is no scheduled trigger for this app, so no polling interval to set. The scenario must be switched on to receive events. You test them with Run once, then by triggering the event on your site. After the test, read the bundle each module received to see which data it carries.
04What if the MemberPress module you need is missing in Make?
Use Make an API Call. This module lets a scenario call any endpoint of the MemberPress API while reusing the connection you already created, so authentication is handled for you. It covers what the 38 listed modules do not, for example a request on data none of the Get, Search or Update modules reach. You write the request yourself, so the MemberPress developer documentation becomes your reference for that part.
05Should you use Make or n8n for MemberPress?
It depends on what your scenario needs. In Make, MemberPress offers 38 modules, including 11 instant triggers covering members, subscriptions and transactions, plus Make an API Call for the rest. The same app often has an n8n node too. Before choosing, list the events and actions your automation requires and check that each tool covers them. The n8n vs Make comparison on this site walks through the broader differences between both platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations