Resources · Zapier integration

MemberPress Zapier integrationAutomate MemberPress with Zapier.

The MemberPress Zapier integration gives you 11 triggers, 10 actions and 3 searches. Every trigger is instant, so course completions, signups, refunds and cancellations reach your other tools without waiting, even on the free plan.

See the 24 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MemberPress Zapier integration does for a course site

The MemberPress Zapier integration links your WordPress membership plugin to the rest of your tools. MemberPress reports what happens on your site (a course finished, a payment refunded, a subscription canceled) and Zapier passes it on, or writes members, subscriptions, transactions and coupons back into MemberPress for you.

On a MemberPress site, three results come up again and again. First, a completion log: Course Completed or Lesson Completed sends each finished course to a spreadsheet, so you see who actually reaches the end. Second, a refund trail: Transaction Refunded writes every refund where your bookkeeping lives, instead of you digging through the plugin later. Third, a member created from outside: when someone buys through another tool, Create Member then Create Transaction give them access in MemberPress.

The best part for a small budget: all 11 triggers are instant. MemberPress tells Zapier the moment the event happens, so the plan's checking interval never slows these Zaps down, free plan included.

Now the limits. Zapier offers no action that creates a membership, so every membership you reference must already exist in MemberPress. There is no action to delete a member either, only a trigger when one is deleted. Coupons can be created and deleted, but there is no search to find one. And no Zap picks up what happened before you switched it on: past signups stay where they are. If you are weighing another builder for the same plugin, see our MemberPress Make integration page.

Vocabulary

Zapier vocabulary in one minute

Eight words you will meet in the editor, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, for example a refunded transaction in MemberPress.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, like creating a member.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those, nothing else.
Instant trigger
A trigger the app reports itself: it calls Zapier the moment the event happens, so nothing waits for the next check. All 11 MemberPress triggers work this way.
Polling trigger
The other kind: Zapier asks an app for new items on a timer and keeps what it has not seen. MemberPress has none.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
Search step
A step that looks up something that already exists in an app, such as a member, so later steps can use what it found.
Cost

What a MemberPress Zap really costs

MemberPress is not a premium app on Zapier: it works from the free plan. The trigger never costs a task, and only an action that succeeds is counted.

  • Premium appNo, free plan works
  • Free plan100 tasks a month, two-step Zaps
  • Trigger cost0 tasks
  • Failed actionNot counted

The free plan gives 100 tasks a month and as many Zaps as you like, but each Zap stops at two steps: one trigger, one action. Add a second action, a filter or a search and it becomes a multi-step Zap, which needs a paid plan. In a three-action Zap, each successful action counts on its own. The interval grid below is Zapier's checking delay for polling triggers; it does not apply to the MemberPress triggers, which are all instant.

Connect

Connect MemberPress to Zapier in 3 steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your MemberPress account linked to Zapier once, then reused by every step that uses it.

  2. 02

    Pick MemberPress

    Type MemberPress in the search box of the dialog, select it, then click Add connection. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.

  3. 03

    Sign in and allow access

    Sign in to MemberPress in the tab that opens, then grant Zapier access to the account. From then on, every step that uses MemberPress can reuse this connection.

First Zap

Your first Zap: a completion email that only goes to finishers of one course

GoalWhen a member completes a course, keep only the course you care about and send that person a follow-up from your email tool.

  1. 01

    Build: pick the trigger

    Create a Zap, choose MemberPress as the app and Course Completed as the event, then select your connection. The filter you add next makes it a multi-step Zap, so it needs a paid plan.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of your account, so the mapping is done on a real one. Read what the step carries before going further.

  3. 03

    Add the filter

    Click the plus icon, add Filter, then set its three boxes: the field to look at, the rule, and the value. Pick a text rule for a course name; a number rule on text never passes.

  4. 04

    Add the email action

    Add your email tool as the action and map into the message the fields the trigger brought back. Check during the test which fields MemberPress actually sends.

  5. 05

    Test, then publish

    Test each step once and read what came back. Then click Publish to switch the Zap on. Only completions after that moment will start it.

Triggers

The 11 MemberPress triggers

11 events start a Zap when something happens in MemberPress, and 11 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Course Completed

Instant trigger

In Zapier“Triggers when a course is completed in MemberPress.”

Starts your Zap when a member finishes a whole course in MemberPress. It is the cleanest signal that someone went all the way, which lesson-level events cannot give you on their own.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
log finishers in a sheet, or send the next course offer to people who just completed this one.
Watch out
it fires for every course; to react to a single course you need a filter, which means a paid plan.
2

Lesson Completed

Instant trigger

In Zapier“Triggers when a lesson is completed on a MemberPress course.”

Reacts each time a member finishes one lesson inside a MemberPress course. It is the fine-grained view of progress, step by step rather than at the finish line.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
spot the lesson where learners stall, by writing each completion to a tracking sheet.
Watch out
a course with many lessons runs the Zap many times per learner, and every successful action counts as a task on your plan.
3

Member Deleted

Instant trigger

In Zapier“Triggers when a member is deleted from the system.”

Fires when a member is removed from MemberPress. Your other tools do not hear about that removal on their own; this trigger lets a Zap pass it on.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
remove or tag the same person in your mailing list or CRM, so they stop receiving member-only messages.
Watch out
check at test which details of the removed member the trigger actually carries before you map them.
4

Member Signup Completed

Instant trigger

In Zapier“Triggers when a new member completes the signup and their payment is accepted.”

Goes off when a new member completes signup and their payment is accepted. That second condition matters: it waits for the money, not just for the form.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
the classic welcome Zap, adding each paying member to your email tool or announcing them in your team chat.
Watch out
a signup still waiting on payment does not match its description, so do not expect it here; test with a real paid signup.
5

Quiz Attempted

Instant trigger

In Zapier“Triggers when a quiz is attempted on a MemberPress course.”

Triggers when a member attempts a quiz in a MemberPress course. Attempted is the key word: the event comes in whether the learner did well or not.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keep a record of attempts per learner, so you can see which quiz people retry most.
Watch out
whether a score or a pass result comes with the event is something to check at test before you build a filter on it.
6

Subscription Created

Instant trigger

In Zapier“Triggers when a subscription is created.”

Kicks off when a subscription is created in MemberPress. This is the recurring side of the business, distinct from a one-off transaction.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
add each new subscriber to a revenue sheet, or tag them in your CRM as a recurring customer.
Watch out
as a general rule, a Zap that writes into the place its own trigger watches can set itself off again, so check at test what your action writes.
7

Subscription Expired

Instant trigger

In Zapier“Triggers when a subscription expires.”

Runs when a subscription reaches its end and expires. Nobody clicked cancel here: the term simply ran out.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
send a renewal reminder from your email tool, or move the person to a former-members list.
Watch out
an expiry and a cancellation are two separate triggers, and a Zap starts from one trigger only; check which one your follow-up needs.
8

Subscription Stopped

Instant trigger

In Zapier“Triggers when a subscription is canceled.”

Responds to a canceled subscription. The name says stopped, the official description says canceled: same event, a member who chose to leave.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
alert whoever handles retention, so a person can reach out while the decision is fresh.
Watch out
it does not cover subscriptions that simply run out; pair it with Subscription Expired if you track every exit.
9

Transaction Completed

Instant trigger

In Zapier“Triggers when a transaction has completed on MemberPress.”

Fires each time a transaction completes in MemberPress. Think of it as the cash register bell.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
write every paid transaction into your bookkeeping sheet, so the numbers do not depend on an export.
Watch out
a busy site fires this one often, and each successful action costs a task against your monthly count.
10

Transaction Expired

Instant trigger

In Zapier“Triggers when any transaction expires.”

Catches any transaction in MemberPress that expires, the payment-level counterpart of an expired subscription.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
notify the member, or flag the account in your support tool, so the expiry is visible outside MemberPress.
Watch out
it covers any transaction, so check at test which membership the event refers to before you send anything personal.
11

Transaction Refunded

Instant trigger

In Zapier“Triggers when any transaction is refunded.”

Lands in Zapier whenever any transaction is refunded. Refunds tend to vanish into the plugin; this trigger pulls each one out where you can see it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
append a line to the refund log your accountant reads, or ping the course owner in the team chat.
Watch out
a Zap only sees refunds made after it is published; older ones need a separate export.
Actions

The 10 MemberPress actions

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

1

Create Coupon

Action

In Zapier“Create a Coupon with the given field values.”

Generates a coupon that applies to the memberships you list by ID. You can set it to start later or to expire at a future date.

When to use it
hand a personal discount to someone who just finished a course, as a reason to take the next one.
Watch out
the Use On Upgrades field is marked deprecated and ignored once the newer upgrades and downgrades dropdown is set.
2

Create Member

Action

In Zapier“Create a Member with the given field values.”

Adds a new member to MemberPress from data another app sends. It needs an email and a username; if your site uses email addresses as usernames, put the same value in both.

When to use it
someone buys through an outside checkout and should get a member account.
Watch out
the welcome email option only works when a transaction is specified, and may not go out if that person already received one.
3

Create Subscription

Action

In Zapier“Create a Subscription with the given field values.”

Opens a subscription for an existing member. It asks for the member's WordPress User ID, the Membership ID, a status (active, cancelled, suspended or pending) and a creation date.

When to use it
a recurring payment handled elsewhere should show up as a subscription in MemberPress.
Watch out
the date must follow the format MemberPress expects, in UTC; trial periods only work on auto-recurring payments.
4

Create Transaction

Action

In Zapier“Create a Transaction with the given field values.”

Records a transaction for a member and a membership, both given by ID. Two switches can send a welcome email and a receipt email at the same time.

When to use it
right after Create Member, to grant access to the membership the person paid for.
Watch out
no email goes out if the person already got a welcome and the membership has no welcome of its own.
5

Delete Coupon

Action

In Zapier“Delete a Coupon with the given id.”

Removes a coupon from MemberPress, given its Coupon ID. Nothing else is needed, so the hard part is having that ID at hand.

When to use it
retire a one-person coupon once it has been used, so it cannot travel further.
Watch out
there is no coupon search, so the ID must come from an earlier step, such as the Create Coupon that made it.
6

Delete Subscription

Action

In Zapier“Delete a Subscription with the given id.”

Erases a subscription, identified by its Subscription ID. This is deletion, not cancellation, so treat it as a clean-up tool.

When to use it
clear out test subscriptions that a setup Zap created by mistake.
Watch out
a Zap runs it every time without asking, so run the test and read what comes back before switching it on.
7

Delete Transaction

Action

In Zapier“Delete a Transaction with the given id.”

Takes a transaction out of MemberPress by Transaction ID. Use it on duplicates, not on real sales.

When to use it
undo transactions an import or a misfiring Zap created twice.
Watch out
pair it with a filter so only the transactions you mean to remove reach this step.
8

Update Member

Action

In Zapier“Update a Member with the given id and field values.”

Changes an existing member, picked by Member ID. Email and username are both required, even if only one of them changes.

When to use it
a member updates their email in your CRM and MemberPress should follow.
Watch out
you need the Member ID; a Get Member search placed before this step can fetch it from an email address.
9

Update Subscription

Action

In Zapier“Update a Subscription with the given id and field values.”

Rewrites a subscription found by its Subscription ID. It asks again for the member, the membership, the status and the creation date, not only the field you want to change.

When to use it
a payment tool reports a suspended plan and MemberPress should show the same status.
Watch out
you need the Subscription ID itself; check at test that the value you map is that ID and not the subscription number.
10

Update Transaction

Action

In Zapier“Update a Transaction with the given id and field values.”

Edits a transaction by its Transaction ID, with the member and the membership required again. The welcome and receipt email switches are available here too.

When to use it
fix a transaction that was recorded against the wrong membership.
Watch out
a Get Transaction search works from the transaction number, which is not the same thing as the ID this action asks for; compare both at test.
Searches

The 3 MemberPress searches

3 search steps look for data that already exists in MemberPress, so a later step can use it.

A search step sits at the bottom of the action list, under the SEARCH heading of Action event. It finds an existing record so the next step can use it. Some fields also offer + Add search step, which inserts the search just before and wires the result in. MemberPress offers no find-or-create variant: these searches only look. Each one makes the Zap multi-step.

1

Get Member

Search

In Zapier“Get member by username or email.”

Looks up a member from an email address, the one required field. It turns an email coming from a form or a CRM into a MemberPress member the next step can act on.

When to use it
before Update Member, to get the Member ID that action needs.
Watch out
the description says username or email, but the form only requires the email; test with a real address.
2

Get Subscription

Search

In Zapier“Get one Subscription with a given subscription number.”

Retrieves one subscription from its subscription number. Handy when another tool only knows the number printed on an invoice or a receipt.

When to use it
pull a subscription's details into a support ticket that quotes its number.
Watch out
the number is not necessarily the Subscription ID the update and delete actions ask for; check what comes back.
3

Get Transaction

Search

In Zapier“Get one Transaction with a given transaction number.”

Fetches a single transaction by its transaction number. It is the one field the search asks for, so that number has to reach this step.

When to use it
a customer emails about a payment and your helpdesk Zap should attach the transaction to the ticket.
Watch out
whether the search wants the exact value or something close is decided by MemberPress, not Zapier; test with a real number.

The three settings every search exposes

  1. Successful if no search results are found?
    Left as is, a search that finds nothing stops the Zap there and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into find-or-create. MemberPress offers no such variant on Zapier, so you will not see it on these three searches.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or hand all of them on at once.
When it breaks

When a MemberPress Zap breaks

Zapier attaches no help article to MemberPress and lists no rate limit for it. What breaks comes from Zapier's general rules and from the fields themselves.

Six cases worth knowing before you publish. If a Zap still misbehaves after that, see our Zapier troubleshooting guide.

  • No catch-up on the past

    A Zap only reacts to what happens after it is switched on. Members, refunds and completions from before stay out; moving that backlog is a separate job.

  • A Zap that sets itself off

    A Zap that writes into the place its own trigger watches can start itself again and again, and burn through your task count. Check any create-and-watch pair at test.

  • Flood protection on bulk changes

    A trigger that suddenly returns a huge batch, after a bulk import or a migration, can be held back by Zapier's flood protection.

  • The welcome email that never left

    Send Welcome Email does nothing if the person already got one and the membership has no welcome of its own. Check at test whether the email went out.

  • Dates in the wrong shape

    Created At on subscriptions expects the date format MemberPress stores, in UTC. Check during the test how the date from your other app lands.

  • A field that no longer counts

    On Create Coupon, Use On Upgrades is deprecated and ignored once the upgrades and downgrades dropdown is set. Use the newer one.
Need help

Need help automating MemberPress with Zapier?

A person reads every message.

FAQ

MemberPress Zapier integration: frequent questions

01Is the MemberPress Zapier integration free?
Yes, as long as each Zap stays at two steps. MemberPress is not a premium app on Zapier, so the free plan can use it. That plan gives 100 tasks a month and an unlimited number of Zaps, but each one is limited to one trigger and one action. A completion log or a refund log fits within that. As soon as you add a filter, a search like Get Member, or a second action such as Create Transaction after Create Member, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a MemberPress Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that writes each Transaction Completed to a spreadsheet costs one task per transaction. A Zap that runs Create Member then Create Transaction costs two per buyer. An action that fails is not counted. Lesson Completed is the one to watch on a course site: it fires for every lesson every learner finishes, so it eats tasks faster than Course Completed, which fires once per course.
03Does MemberPress trigger Zaps in real time?
Yes, all 11 MemberPress triggers are instant. MemberPress tells Zapier the moment the event happens, whether it is a signup, a refund, a quiz attempt or an expired subscription, so the Zap starts right away. The checking interval of Zapier plans, 15 minutes on the free plan, only applies to polling triggers, and MemberPress has none. You will see a lightning bolt on these Zaps in the editor, which is how Zapier marks an instant trigger.
04What does it take to connect MemberPress to Zapier?
An account on MemberPress, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection is made once from the Apps page of Zapier with + Add connection: you pick MemberPress, sign in in the tab that opens and grant access. For the creation actions, also have your memberships ready in MemberPress, because Create Subscription and Create Transaction ask for a Membership ID and no action creates one.
05Why did Create Member not send the welcome email?
Because Send Welcome Email has conditions. On Create Member it only works when a transaction has been specified. And on both Create Member and Create Transaction, no email goes out if the person already received a welcome email and the membership has no welcome email of its own. If the welcome matters, give the membership its own welcome email in MemberPress, then check at test whether the email went out before you publish.
06What if the MemberPress operation you need is not in the list?
Then Zapier cannot do it with this app as it stands, and no setting will unlock it. Check first whether two steps cover it: a search like Get Member followed by Update Member replaces a missing combined action, for instance. Coupons have no search, members cannot be deleted by an action, and memberships cannot be created. The MemberPress page on Zapier shows the current list of operations, so check it there before you build.
07Zapier, Make or n8n for MemberPress?
Judge it on your own flow, not on a league table. Write down the Zap you want, for example Course Completed, then a filter on one course, then an email. On Zapier that is three steps, so a paid plan; a plain completion log with no filter stays free. Speed is not a deciding point here, since every MemberPress trigger on Zapier is instant. What separates the tools is how each one counts and prices those steps, so run the same written flow through Make and n8n pricing before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations