Nearly every answer is in Zap history in Zapier. It shows each run, the data that came in, the data that went out and the reason for anything that failed. Open the failed run first, then look for the case below.
The trigger never fires
These things stop an instant trigger, in this order of likelihood.
- The Zap is off. Nothing is delivered while it is off, and nothing is caught up when you turn it back on.
- The event has not actually happened. Turn the Zap on and produce it once yourself: add a test member, pay a test order, complete a lesson.
- You are watching the wrong workspace. The connection carries the workspace name. If you run more than one, check that the Zap uses the one where the event takes place.
- The workspace is on Starter. Zapier needs the Professional plan, and nothing is delivered on a lower one.
- The connection was ended. After someone pressed Disconnect on the Zapier page, or after your account lost its admin access, a trigger stays quiet until you reconnect and turn its Zap off and on once.
A polling trigger is not instant by design. It asks every few minutes, so give it that long before calling it broken.
A step is refused with "Missing scope"
The message names the permission that is missing, for example "Missing scope: payments:read." The current version of the MemberArea app does not ask for permission to read payments, courses, events and hubs, so reconnecting does not help with these four. They affect:
- the test of Order Paid, of the subscription triggers and of Affiliate Commission Created. Zapier wants a successful trigger test before it turns a Zap on, so a Zap that starts with one of these triggers can only be finished once a later version of the app asks for this permission.
- the lists of courses, lessons, events and products in action fields, which show the same message instead of loading. Map the ID from an earlier step instead.
For any other permission, reconnect: open My Apps in Zapier, find MemberArea, press Reconnect and choose the same workspace again.
"Zapier is not included in this MemberArea's plan"
The workspace is on Starter. Zapier and Make need the Professional plan or higher, while the REST API works on every paid plan. Upgrade the plan. An existing connection works again from the next run, and a new one can be made right after the upgrade.
"Member with this email already exists in the business."
Email addresses are unique inside a workspace, so Create Member refuses a second member with one that is already taken. Only that single run stops, the ones behind it carry on.
Which way out depends on what the Zap is for:
- People who are meant to exist already belong behind Find Member by Email, followed by Update Member or any action that takes a member. A search that finds nothing stops the steps behind it unless you tell Zapier to carry on, so the Zap acts only on people it actually found.
- A mixed list of new and returning people is the awkward case: MemberArea does not offer Zapier's built-in "create it if the search finds nothing" option yet, so the create step stays as it is and the runs that hit a known address end with this message. Zap history shows which ones those were.
Contacts in your audience behave the same way. There the message reads "A contact with this email address already exists." In the same way, Update Member with an address that belongs to someone else stops with "Email already used by another member in this business."
"Publish the course first"
Access to a draft course is never handed out, not through a Zap either. The step stops with "Publish the course first. Access can only be given to a published course." Publish the course, then replay the run from Zap history.
The workspace is full
An action that creates a member stops when the plan's member limit is reached, and the message names the limit, for example "Your plan's members limit (500) has been reached. Upgrade to add more." Upgrade the plan and replay the run from Zap history.
The Zap wrote into the wrong workspace
Each connection points at exactly one workspace and is named after it. Open the step, look at the account line, and switch it to the right connection. If only one exists and it is the wrong one, connect the other workspace as a second account rather than replacing the first.
A test created real data
Testing an action performs it. A test of Create Member creates a member and a test of Add Tag to Member tags someone. Delete what the test produced in your memberarea, and use an address of your own for the next one.
The builder inside your memberarea does not load
Three notes can appear in place of it.
- A purple one says Zapier is part of the Professional plan. Change plan leads to the plans.
- A blue one says Zapier opens in a new tab on this domain. The embed only runs on memberarea.io addresses, so on a domain of your own use the Open in Zapier button.
- A red one says Zapier could not be loaded, which is usually a network or ad-blocker matter. Press Try again to load it once more, and if it persists work on zapier.com instead.
The Zap cannot be turned off, or asks for a reconnect
A connection that only feeds triggers never renews itself. After 60 days in which Zapier made no call to your memberarea, it asks for a reconnect, also when you try to turn such a Zap off. Reconnect in My Apps. The triggers kept delivering all along, so nothing else is needed.
Still stuck
Problems with Zapier itself, with another app in the Zap or with your Zapier account go to zapier.com/app/get-help. For our triggers and actions you are welcome to write to our support directly. Naming the Zap and the time of the failed run saves a round trip.