Resources · Zapier integration

MemberSuite Zapier integrationAutomate MemberSuite with Zapier.

MemberSuite Zapier integration: 0 triggers, 1 action, 0 searches. MemberSuite can't start a Zap (an automation built on Zapier), but it can receive one: another app fires, and Zapier creates the person in your MemberSuite CRM.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MemberSuite Zapier integration does for you

The MemberSuite Zapier integration lets another app hand people over to MemberSuite. It has a single action, Create Individual in CRM, and no trigger, so the automation always starts somewhere else. Zapier then writes the person into the CRM with an email, a name, a company, a phone number type and a status.

A member record straight from a signup form. Someone fills in your membership form. The Zap passes their email, first and last name and company to Create Individual in CRM, and the individual lands in MemberSuite without anyone retyping it.

Members who arrive already labeled. Individual Status and Phone Number Type are required on every new record. Set them once in the Zap and every member created that way arrives with the same status, ready to be sorted inside MemberSuite.

One contact list instead of two. MemberSuite is built to hold members, donors and prospects in one place. Each person the form collects goes there too, so nobody keeps a side list that drifts out of date.

What Zapier doesn't do here. It can't start a Zap from MemberSuite: no trigger is offered, so a change made in the CRM sends nothing anywhere. It can't look an individual up, and it can't edit one that already exists. The only move is creating someone new.

Before you build, read our Zapier review. If the setup grows past a single action, open our Zapier agency page.

Vocabulary

Zapier words, in plain English

Eight words cover everything on this page. Each one is used below exactly as defined here.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. MemberSuite offers none, so yours always comes from another app you connect.
Action
What the Zap does once it has started. Here it is Create Individual in CRM, which writes a new person into MemberSuite.
Task
The unit Zapier bills: one action completed successfully. The monthly allowance of your plan is a count of these.
Polling vs instant
Polling: Zapier asks the app for new items on a timer. Instant: the app tells Zapier itself the moment the event happens.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it needs a paid plan.
Connection
Your MemberSuite account linked to Zapier once, then reused by every step that uses MemberSuite in any Zap.
Cost

What MemberSuite costs you in Zapier tasks

The trigger never costs a task, and Zapier checking for new data costs nothing either. Only a completed action is billed: each individual created in MemberSuite counts as one task, and an action that fails isn't counted.

  • Trigger0 tasks
  • Create Individual in CRM, successful1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

MemberSuite isn't a premium app, so it runs on the free plan: 100 tasks a month and unlimited Zaps, two steps each. A filter, a second action or a search turns the Zap multi-step, which needs a paid plan. The grid below only concerns the trigger of the other app, and only when that trigger is a polling one. If it is instant, the app reports each event itself and no interval applies. A few apps and actions take more than one task when they complete, so read the count after your first test.

Connect

Connect MemberSuite to Zapier in three steps

  1. 01

    Open Apps and add a connection

    In your Zapier account, go to the Apps page and click + Add connection. A dialog opens with a search box: type MemberSuite and pick it from the results.

  2. 02

    Sign in to MemberSuite

    Click Add connection. A new tab opens on MemberSuite: sign in with the account that should own the records. You need an account on the app, plus read or write access on anything you don't own yourself and want the Zap to touch.

  3. 03

    Grant access, then reuse it

    Grant Zapier access to the account. The connection is saved once, and from then on every step that uses MemberSuite picks it from a list instead of asking you to sign in again.

First Zap

Your first Zap: a form entry becomes a member

GoalTurn each new membership form entry into an individual in MemberSuite, with a filter that lets through only the entries you choose.

  1. 01

    Start on the form side

    Create a Zap and pick your form tool as the trigger app, with its new-entry event. MemberSuite has no trigger of its own, so the Zap always starts in the other app.

  2. 02

    Test the trigger

    Run the trigger test. Zapier brings back the three most recent entries of the connected account, so you map fields on a real entry rather than on a blank.

  3. 03

    Add the filter

    Add a filter from the plus icon and fill its three boxes: the field to look at, the rule, the value. Pick a text rule for text. This step makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add Create Individual in CRM

    Choose MemberSuite and Create Individual in CRM. Map Email Address, First Name, Last Name and Company Name from the entry, then set Phone Number Type and Individual Status.

  5. 05

    Test, then publish

    Test the action once and read what MemberSuite sent back. If the individual looks right, publish the Zap to switch it on. Entries sent before that moment are not picked up.

Actions

The MemberSuite action on Zapier

MemberSuite gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Individual in CRM

Action

In Zapier“Creates a new Individual in MemberSuite CRM.”

Adds a new person to your MemberSuite CRM, with contact details, company, a phone number type and a status set from the first second the record exists.

When to use it
whenever someone joins, gives or shows interest through another tool and should exist in MemberSuite too.
Watch out
six fields are required, and Email Address must be unique in the association, so test with an address you know is new.
When it breaks

When the MemberSuite Zap breaks

Zapier documents no limit specific to MemberSuite. What can go wrong comes from the general rules of Zapier, and they apply to this Zap like to any other.

Read these four cases before you switch the Zap on: two are about what Zapier picks up, two about what it does with it once it has it.

  • Nothing from before the Zap

    A Zap only reacts to what happens after you switch it on. People already in your form tool stay there; moving that backlog is a separate job.

  • A Zap that sets itself off

    A Zap that writes into the very place its own trigger watches can start itself again and burn through your tasks. Keep the trigger and the target apart.

  • Bulk imports held back

    A trigger that suddenly returns a huge batch, after a bulk import or a migration, can be held back by the flood protection of Zapier.

  • No double starts on polling

    On a polling trigger, Zapier keeps track of what it has already seen, so the same item from the other app does not start the Zap twice.
Need help

Need help automating MemberSuite with Zapier?

A person reads every message.

FAQ

MemberSuite and Zapier: questions people ask

01Is the MemberSuite Zapier integration free?
Yes, on the free plan of Zapier. MemberSuite isn't a premium app, so Create Individual in CRM works without paying. The free plan gives 100 tasks a month and an unlimited number of Zaps, but each Zap stops at two steps: one trigger, one action. That covers the basic case of sending each new contact to MemberSuite. Once you want a filter, a search or a second action in the same Zap, it becomes a multi-step Zap and needs a paid plan.
02How many tasks does a MemberSuite Zap use?
One per individual created. The trigger costs nothing, and Zapier checking the other app for new data costs nothing either. Each time Create Individual in CRM completes, one task is counted; when it fails, nothing is counted. Add a second action to the same Zap and each successful one counts on its own, so the bill grows with the number of actions that work, never with the number of checks Zapier runs.
03Is MemberSuite on Zapier real time?
It depends on the other app, because MemberSuite offers no trigger. The Zap starts on the trigger of that other app. If it is instant, the app tells Zapier the moment the event happens and no interval applies. If it is a polling one, Zapier checks on a timer: every 15 minutes on Free, every 2 on Professional, every minute on Team and Enterprise. A Zap built on an instant trigger shows a lightning bolt in the editor, which is the quickest way to tell.
04What does it take to connect MemberSuite to Zapier?
An account on MemberSuite, plus read or write access on anything you don't own yourself and want the Zap to touch. On the Apps page of Zapier, click + Add connection, search for MemberSuite, click Add connection, sign in in the tab that opens and grant access. The connection is then saved and reused by every MemberSuite step. Before the first Zap, have your values for Phone Number Type and Individual Status ready, since both fields are required by the action.
05Why does MemberSuite want a unique email for each individual?
Because Create Individual in CRM requires an Email Address that is unique within your association. It is mandatory, alongside First Name, Last Name, Company Name, Phone Number Type and Individual Status. Someone who signs up twice with the same address is the case to plan for. Test the Zap with an address MemberSuite already holds and read what comes back, so you know how the action behaves on a repeat before the Zap is live.
06What if the MemberSuite operation you want isn't there?
Then Zapier can't do it for MemberSuite today. The integration offers one action, Create Individual in CRM, with no trigger, no search and no update. A Zap can't read MemberSuite, find an existing member or change a status afterwards. What it can do is prepare the data upstream, for instance by holding entries back with a filter, so only the people worth creating reach MemberSuite. Anything beyond creating a new individual sits outside this integration.
07Zapier, Make or n8n for MemberSuite?
Pick on criteria, not on a ranking. Start with availability: is MemberSuite offered on the other platform, and with which operations? If it isn't, there is nothing to compare. If it is, look at volume next. Zapier bills one task per individual created, and a plain trigger-plus-action Zap runs on the free plan. Then ask who will keep the flow alive once it grows extra steps, because that person's comfort with the tool matters more than any feature list.
Same platform

Other docs you might need on this stack.

Browse all integrations