The integration offers close to 100 steps, which covers most of what the product can do. They come in three kinds. A trigger starts a Zap when something happens here. An action does something here. A search looks something up so a later step can use it.
Triggers
All of them except the last row are instant: your memberarea pushes the event to Zapier within seconds of it happening, as long as the Zap is turned on.
| Area | Triggers |
|---|---|
| Members | New Member, Member Logged In, Tag Added to Member, Tag Removed From Member, Member Field Changed |
| Payments | Order Paid, Invoice Paid, Refund Created, New Subscription, Subscription Renewed, Subscription Cancelled, Subscription Payment Failed |
| Affiliates | Affiliate Commission Created, Affiliate Payout Paid |
| Courses | Course Completed, Lesson Completed |
| Events | New Event Registration, Event Attendance Recorded |
| Community | New Community Post, Member Leveled Up, Badge Earned |
| Audience | New Contact |
| Inbox | New Inbox Message, New Ticket |
| Checked every few minutes | New Tag, New Group |
New Member fires for every new member of the workspace, however they joined: signup page, Google or single sign-on, checkout, a member you add by hand, an import, or another tool such as Digistore24, ManyChat or HubSpot. An import that adds 500 new members therefore starts the Zap 500 times; rows for people who are already members do not start it.
Amounts in payment and affiliate triggers come in the smallest unit of the currency: 4900 with the currency EUR means 49.00 euros.
In the current version of the app, the test of Order Paid, of the four subscription triggers and of Affiliate Commission Created ends with "Missing scope: payments:read." Zapier wants a successful trigger test before it turns a Zap on, so a Zap that starts with one of these can only be finished once a later version of the app asks for this permission.
Actions
| Area | Actions |
|---|---|
| Members | Create Member, Update Member, Remove Member, Set Member Custom Field, Assign Role to Member |
| Tags and groups | Create Tag, Delete Tag, Add Tag to Member, Remove Tag From Member, Create Group, Update Group, Delete Group, Add Member to Group, Remove Member From Group |
| Courses | Enroll Member in Course, Unenroll Member From Course, Mark Lesson Complete for Member, Mark Course Complete for Member, Reset Course Progress for Member |
| Events | Register Member for Event, Cancel Event Registration, Check in Member at Event |
| Community | Create, update and delete areas, forums, posts, comments and badges, Award Badge to Member, Revoke Badge From Member |
| Audience | Create Contact, Update Contact, Delete Contact, Add Tag to Contact, Remove Tag From Contact |
| Inbox | Reply to Conversation, Update Conversation, Create Ticket, Update Ticket, Delete Ticket, Add Note to Ticket |
| Affiliates | Assign Member to Affiliate, Remove Affiliate Claim, Register Affiliate Conversion, Redeem Member Reward |
| Automations | Trigger Automation |
| Global fields | Create Global Field, Update Global Field, Set Global Field Value, Delete Global Field |
A few of them behave in a way worth knowing before you build:
- Remove Member takes the person out of this workspace. Their MemberArea account stays, and so do their memberships elsewhere.
- Assign Role to Member lists every role, but admin, owner and roles with team or role management rights are refused with "This role cannot be assigned via the API."
- Register Affiliate Conversion and Redeem Member Reward take amounts in the smallest currency unit and need an Idempotency Key: a value that is unique for each sale or redemption, such as the order number. A replayed run with the same key is not counted twice.
- Trigger Automation only starts an automation that is switched on and has a published version.
- Create Community Badge needs a badge group in the community first.
Searches
Find Member, Find Member by Email, Get Member by ID, List Member Course Progress, Get Member Reward Balance, Get Member Affiliate Claim, Find Contact, Get Contact by ID, Find Conversation, Find Ticket, Find Automation, Find Global Field, Get Global Field.
Searches are what you put in front of an action that needs an existing record. The common pair is Find Member by Email, then an action on whoever came back. A search that finds nothing stops the steps behind it unless you tell Zapier to carry on, so those steps only see people who are really there.
Find Member also matches part of a name or an address and returns the first hit. When you know the email address, Find Member by Email is the safer choice.
Zapier's built-in "create it if the search finds nothing" option is not available for MemberArea yet. A Zap that has to handle new and returning people in one run is covered in fixing problems with a Zap.
Picking things from a list
Fields that need a member, a tag, a group, a custom field, a role, a contact, a badge, a community area or forum, a ticket, a conversation, a global field or an automation offer a dropdown filled from your own workspace, so you choose the real thing by name instead of copying an ID. The dropdowns are filled from your workspace and show the first 100 entries.
Some fields take an ID instead:
- The member in Add Member to Group and Remove Member From Group, and the badge in Update Community Badge and Delete Community Badge, are plain text fields. Map the ID from an earlier step.
- In the current version of the app, the lists of courses, lessons, events and products do not load and show "Missing scope: courses:read." or a similar message. Map the ID from an earlier step instead, for example from Course Completed, List Member Course Progress or New Event Registration.
When something is not on the list
The Custom API Request action sends any call to our API from inside a Zap: you give it a method, a path and a body, and it returns whatever the API returns. It covers anything not wrapped as its own step. The endpoints are documented at api.memberarea.io/api/v1/docs.
The other direction: a webhook to Zapier
There is a second, smaller path that has nothing to do with the app in the Zapier directory. In Settings, then Integrations, a Zapier entry can hold a Zapier Catch Hook address, and automations in your memberarea can then send data to it. Use it when you have an automation here that should hand something over to Zapier. For everything else the triggers above are simpler and faster.