Zapier connects your memberarea to more than 10,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
- 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 with the title Connect Zapier to MemberArea. Sign in with your usual MemberArea email address and password.
- The next screen is titled Zapier wants to access your MemberArea and asks you to choose the workspace to connect. Pick it, read what Zapier will be able to do, then press Allow access.
- 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 account you sign in with has to administer a workspace. If it does not, the page says so instead of offering a choice: sign in with an account that does, or have someone give yours admin access first.
Connecting from your memberarea
You can also start inside the product and never leave it. Open Settings, then Integrations, find the Zapier entry and choose Manage Zaps. The builder that appears 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. The connection can read and write the same things an administrator can reach in the workspace: members, tags and groups, orders and subscriptions, courses and events, community content, audience contacts, datasets and the affiliate figures. It cannot change your plan, your billing or anyone's password.
A connection belongs to the workspace, not to your user account. Colleagues who build their own Zaps sign in themselves and get their own connection.
Reconnecting
Two situations call for a reconnect:
- Zapier says the connection needs attention. The access was withdrawn or has expired. Open My Apps in Zapier, find MemberArea and press Reconnect.
- A new trigger or action returns a permission error. Permissions are fixed at the moment you connect, so a connection made before a feature existed does not cover it. Reconnecting the same account is enough and takes a few seconds.
Reconnecting does not break running Zaps. They keep their history and carry on with the refreshed access.
Disconnecting
Delete the connection in Zapier under My Apps. Every Zap that used it stops at its next run and says the account is missing. Nothing is deleted inside your memberarea, and reconnecting the same workspace puts the Zaps back to work.
The integration is listed in the Zapier app directory and is marked Beta while it collects its first users. The label says nothing about what it can do. Every trigger and action is finished, reviewed by Zapier and live.