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
Three 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: sign up 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.
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 a permission error
Permissions are fixed at the moment you connect, so a connection made before a feature existed does not cover its steps. Open My Apps in Zapier, find MemberArea and press Reconnect, then choose the same workspace again. Running Zaps keep their history and carry on.
"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 Zapier search that finds nothing ends that run by design, 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.
The course in the step is not published
Access to a draft course is never handed out, not through a Zap either. Publish the course, then run the step again.
The workspace is full
An action that creates a member stops when the plan's member limit is reached. 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
Two notes can appear in place of it. 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 a network or ad-blocker matter. Press Try again, and if it persists work on zapier.com instead.
Still stuck
Problems with Zapier itself, with another app in the Zap or with your Zapier account go to zapier.com/app/get-help. Reports about our triggers and actions reach us from there, and you are welcome to write to our support directly as well. Naming the Zap and the time of the failed run saves a round trip.