Zapier connects your memberarea to more than 7,000 other apps without a line of code. A new signup can land in your newsletter tool, a paid order can appear in Slack, and a form somewhere else can create the member here. You connect the two once, and every Zap you build afterwards reuses that connection.
Zapier and Make are part of the Professional plan and above. The REST API itself is included in every paid plan, so your own scripts and the WordPress plugin work on Starter too; only these two automation platforms need the higher plan.
Connecting from Zapier
MemberArea has its own page in the Zapier app directory, listing every trigger and action: MemberArea on Zapier. Zapier marks the app as beta there.
-
In Zapier, create a Zap and pick MemberArea as the app for the trigger or the action.
-
Choose the event, then press Sign in under Account.
-
A MemberArea window opens. If you are not signed in to MemberArea in this browser yet, it asks for your usual email address and password first. With two-step verification turned on, the next screen asks for the code.
-
The next screen asks you to choose the workspace, lists what Zapier will be able to do, and ends with Allow access.
The MemberArea consent screen for Zapier with the workspace highline.memberarea.local selected, the list of what Zapier will be allowed to do and the Allow access button. -
The window closes and Zapier shows the connection, named after the workspace you picked.
That name is the only thing that tells two connections apart later, so it is worth reading before you build. If you run several workspaces, connect each one separately and pick the right one in every Zap step.
The bottom of the screen says which account you are signed in as. If that is the wrong one, press Use another account and sign in again.
The account you sign in with has to administer a workspace. If it does not, the page says so instead of offering a choice. Press Use another account to sign in with one that does, or have someone give yours admin access first.
On the Starter plan
A workspace on Starter shows Needs the Professional plan on its tile. You can still press Allow access, but Zapier then stops with "Zapier is not included in this MemberArea's plan" and saves no connection. Upgrade the plan first, then connect. A connection made earlier on a higher plan stays in Zapier after a downgrade, but its steps are refused with the same message and its triggers deliver nothing until the plan is upgraded again.
Building from your memberarea
You can also start inside the product and never leave it. Open Settings, then Integrations, and press Create Zaps at the top of the page. The page that opens is called Zapier and holds Zapier's own builder. The builder asks for its own Zapier login the first time and then works exactly like the one on zapier.com. The article on building your first Zap walks through it.
What Zapier is allowed to do
The consent screen lists the permissions in plain words before you agree to anything. Among them, Zapier can:
- read, create, edit and remove members, their tags and custom fields, and assign roles other than admin and owner
- manage groups, global fields, community content and badges, and audience contacts
- enrol members in courses, mark their progress, and register or check them in for events
- read and answer inbox conversations and tickets, and start automations
- register affiliate conversions, assign members to affiliates and redeem reward balances
- create and remove the webhooks its instant triggers rely on
It cannot change your plan, your billing, your payment settings or anyone's password.
A connection belongs to you and to the workspace you picked. Colleagues who build their own Zaps sign in themselves and get their own connection. If your account loses its admin access to the workspace, the connection stops working at once, and its Zaps stop with it.
Reconnecting
Zapier asks you to reconnect when the access was withdrawn or has expired. Open My Apps in Zapier, find MemberArea and press Reconnect, then choose the same workspace again. Zaps keep their history, and their actions and searches carry on with the new access. If the access was withdrawn, through Disconnect or because your account lost its admin access, the triggers stopped with it and stay quiet until you turn each Zap off and on once.
A connection that is only used by triggers does not renew itself. After 60 days in which Zapier made no call to your memberarea, its triggers keep delivering, but Zapier needs a reconnect before the next action, search or dropdown, and before you can turn such a Zap off.
Seeing and ending connections
Every Zapier and Make account with access to your workspace is listed on the Zapier page under Connections, with the address of the person who connected it and the number of active triggers. Disconnect ends the access right away: every Zap that uses the connection stops, and Zapier asks for a reconnect. Nothing is deleted inside your memberarea. To bring the Zaps back, reconnect the same workspace in Zapier, then turn every Zap that starts with a MemberArea trigger off and on once, so its trigger subscribes again.
You can also delete the connection in Zapier under My Apps. The webhooks that instant triggers create appear in your memberarea under Payments, then Settings, then Webhooks, named Zapier and marked API. You can pause them there, but their address and events belong to Zapier.
The integration is listed in the Zapier app directory and is marked Beta while it collects its first users.