Member365 Zapier integrationAutomate Member365 with Zapier.
The Member365 Zapier integration gives you 5 triggers, 1 action and 0 searches. All five triggers are instant and four of them follow event tickets, so the integration is mostly about pushing registrations out of Member365 into your other tools.
Verified Trustpilot reviews · AI, automation & growth agency
What the Member365 Zapier integration actually does
Member365 is a membership management CRM that handles membership renewals, payments and events. Through Zapier, its contacts and event registrations can start work in other tools, and one action lets another tool mark attendance at an event. It is a mostly one-way integration: Member365 speaks, the rest of your stack listens.
A clean attendee list. Event Registration Paid fires only once the registration invoice is paid. Send each one to a spreadsheet and the list you print for the door holds paying attendees, not half-finished sign-ups.
Tickets that follow the person. Transfer Ticket and Withdraw Ticket report when a ticket changes hands or is pulled back. Your badge printer or seating plan stays in step with who is really coming.
Attendance recorded from the door. Mark Attendance writes check-ins back into Member365 from whatever tool you use at the entrance, matched on the event name and the attendee's email.
What Zapier does not do here: there is no action to create a contact, a registration or an invoice, and no search step to look one up. Event Registration Paid does not fire on refunds and on registrations going from paid back to unpaid. And a Zap never picks up registrations made before it was switched on.
Weighing other tools for this? See our n8n vs Zapier page, or our Zapier review.
Zapier words, in plain English
Seven terms come back across this page. Here they are once, then used without reminders.
- Zap
- The automation you build: one trigger, then one or more actions that run each time that trigger's event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event to happen.
- Action
- What the Zap does after it starts: the step that writes, sends or updates something for you in an app.
- Task
- The unit Zapier bills. One task is one action your Zap finished successfully, and your plan counts those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, so nothing waits.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and stops it otherwise.
- Connection
- Your Member365 account linked to Zapier once, then reused by every step that talks to Member365.
What it really costs
Member365 is not reserved for paid plans: it works on the free plan.
- Free plan100 tasks a month, unlimited two-step Zaps
- Paid plans onlyFilters, second actions
- This appAvailable on the free plan
The trigger never costs a task, and waiting for new registrations costs nothing either. Each action that succeeds counts once, so a three-action Zap uses three times what a one-action Zap does, and a failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each capped at two steps. A second action or a filter makes it a multi-step Zap, which needs a paid plan.
The grid below is how often Zapier checks a polling trigger on each plan. All five Member365 triggers are instant, so it does not apply to them.
Connect your Member365 account
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. You need an account on Member365, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick Member365
Type Member365 in the search box of the dialog, select it, then click Add connection. A new tab opens on the Member365 sign-in page, separate from your Zapier window.
- 03
Sign in and allow access
Log in to Member365 in that tab and grant Zapier access to the account. From then on, every Zap that uses Member365 can reuse that same connection from your Apps page.
Your first Zap: a confirmation for paid registrations only
GoalEvery paid registration for the event you choose sends a confirmation from your email tool, but only when it passes your filter.
- 01
Create the Zap
Start a new Zap and choose Member365 as the app that starts it. Select the connection you created earlier when Zapier asks which account to use.
- 02
Set the trigger
Pick Event Registration Paid and fill the required Event Name. Test it: Zapier brings back the three most recent items of the account, so you map on a real registration.
- 03
Add the filter
Click the plus icon, choose Filter and fill the three boxes: the field to look at, the rule, the value. A number rule only works on numbers, so pick the type that matches.
- 04
Add the email
Add your email tool as the next step and map the attendee's details from the trigger. Which details arrive is visible in the test result, so check them there.
- 05
Test, then publish
Run each step once and read what came back. Then click Publish. With the filter, this is a multi-step Zap, so it needs a paid plan.
Member365 triggers: 5 events, all instant
5 events start a Zap when something happens in Member365, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.
New Contact
Instant triggerIn Zapier“Triggers when contact is created in Member365.”
A contact was created in Member365, and that new record is what starts the Zap. It is the only trigger of the app that is not about event tickets, so it is the one to reach for when your other tools need to know about every new person in the CRM, member or not.
Event Registration With Assigned Ticket
Instant triggerIn Zapier“Triggers when an event registration is completed regardless of payment status. When a contact has an event ticket assigned to them this trigger will send the contact information and event registration details.”
Fires when an event registration is completed and a ticket is assigned to a contact, whether or not the registration has been paid. It sends the contact's details along with the registration, so the next step knows both who registered and for what.
Event Registration Paid
Instant triggerIn Zapier“Triggers when an event registration's invoice is marked as paid, including free registrations (unless you set a minimum invoice amount). Unlike "Event Registration With Assigned Ticket", this only fires once payment is complete. Does not trigger for refunds or paid-to-unpaid changes.”
Waits for the invoice of a registration to be marked as paid. Free registrations count too, unless you set a minimum invoice amount. Refunds and registrations going from paid back to unpaid never fire it.
Transfer Ticket
Instant triggerIn Zapier“Triggers when an existing event ticket is transferred. When an event ticket is transferred this trigger will update the registration to the new contact.”
An existing ticket moved from one contact to another, and Member365 updates the registration to the new holder. The Zap starts on that hand-over, which is easy to miss when it happens close to the event.
Withdraw Ticket
Instant triggerIn Zapier“Triggers when an existing event ticket is withdrawn. When an event ticket is withdrawn this trigger will remove the registration from the contact.”
A ticket was withdrawn, and Member365 removes the registration from the contact. This is the trigger that tells your other tools someone is no longer coming.
Member365 action
Member365 gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Mark Attendance
ActionIn Zapier“Marks Attendance on a Ticket in Events”
Records attendance on an event ticket in Member365. It needs two things: the Event Name and the Email Address of the attendee, both required.
When it breaks
Zapier links no help article to Member365, so the cases below come from Zapier's general limits and from what the triggers say about themselves.
The tricky cases here are Zaps that run on the wrong registrations, or keep running after a change of plan. Check these four before publishing; for anything else, see our Zapier troubleshooting page.
Past registrations are not picked up
A Zap only reacts to events after it is switched on. Contacts and registrations that already existed are left out; moving them is a separate job.A Zap that restarts itself
As a general precaution, a Zap that writes into the place its own trigger watches can set itself off again and burn through your task count.A big import is held back
After a bulk import of contacts or registrations, a trigger that suddenly sends a huge batch can be held back by Zapier's flood protection.Refunds go unreported
Event Registration Paid does not fire for refunds or paid-to-unpaid changes. What a Zap did on payment stays done, so plan the clean-up by hand.
Need help automating Member365 with Zapier?
A person reads every message.
