Resources · Zapier integration

Membership.io Zapier integrationAutomate Membership.io with Zapier.

The Membership.io Zapier integration gives you 12 triggers, 16 actions and 1 search. It covers your audience, hub access, files and playlists. One trigger is instant; the other 11 are checked on your plan's interval, 15 minutes on the free plan.

See the 29 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Membership.io Zapier integration does for a creator

The Membership.io Zapier integration connects the platform where you run your membership site to your other tools. Zapier can react to new audience members, files, playlists and hubs, and it can grant or remove hub access, tag people, hand out achievements and file new content for you.

Three results come up most for a creator running a members' area. An onboarding follow-up: Hub Onboarding Completed tags the member with Add Audience Tag or tells your team in chat. Access driven by your sales tool: when someone buys elsewhere, Add or Update Audience then Add Hub Access let them in, and Remove Hub Access closes the door when they leave. A content pipeline: Add File pulls a file from a link into a folder, then File Processed tells you when it is ready to go into a playlist.

The most useful thing to know: of the 12 triggers, Hub Onboarding Completed is the only instant one. It reacts straight away even on the free plan, while the 11 others wait for the plan's interval. Neither zapier.com nor the help center points this out.

What Zapier does not do here. No action creates a hub, a playlist or a folder: they must already exist. No action deletes a file. The only search finds an audience member, so a file or a playlist cannot be looked up mid-Zap. And no Zap goes back over members or files that existed before it was switched on. If you are still weighing the tools, see our n8n vs Zapier comparison.

Vocabulary

Zapier vocabulary in one minute

Eight words you will meet in the editor, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, such as a new playlist in Membership.io.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, like granting hub access.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those and nothing else.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps what it has not seen. 11 of the 12 here.
Instant trigger
A trigger the app reports itself, the moment the event happens, so nothing waits for the next check. Here, only Hub Onboarding Completed.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
Search step
A step that looks up something that already exists in an app, such as an audience member, so later steps can use it.
Cost

What a Membership.io Zap really costs

Membership.io is not a premium app on Zapier: it works on the free plan. The trigger never costs a task; only an action that succeeds is counted, and a failed one is not.

  • Premium appNo, free plan works
  • Free plan100 tasks a month, two-step Zaps
  • Instant triggers1 of 12
  • Trigger cost0 tasks

The free plan gives 100 tasks a month and unlimited Zaps, each capped at two steps: one trigger, one action. Add a second action, a filter or the Find Audience search and the Zap becomes multi-step, which needs a paid plan. Checking for new items costs nothing, however often Zapier looks. The grid below sets how often the 11 polling triggers are checked; Hub Onboarding Completed is instant and ignores it.

Connect

Connect Membership.io to Zapier in 3 steps

  1. 01

    Open your connections

    In Zapier, open the Apps page of your account and click + Add connection. A connection is your Membership.io account linked to Zapier once, then reused by every step that needs it.

  2. 02

    Find Membership.io

    Search for Membership.io in the dialog, pick it, then click Add connection. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.

  3. 03

    Sign in and allow access

    Sign in to Membership.io in the tab that opens and grant Zapier access to the account. Every step that uses Membership.io can then reuse this connection.

First Zap

Your first Zap: tag members who finish onboarding and tell the team

GoalWhen a member completes onboarding in a hub, add a tag to them in Membership.io and post a note in your team chat.

  1. 01

    Build: set the trigger

    Create a Zap, choose Membership.io and the Hub Onboarding Completed event, then your connection. Pick the hub to watch: the Hub field is required.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of your account, so the mapping is done on a real one. Read what the step carries.

  3. 03

    Add the tag

    Add the Add Audience Tag action. In Audience, map the member's email from the trigger (check it is there at test), then choose the tag to add.

  4. 04

    Add the chat message

    Add your team chat as a second action and write a short note from the fields the trigger brought back at test. Two actions make this a multi-step Zap, so it needs a paid plan.

  5. 05

    Test, then publish

    Test each step once and read what came back, then click Publish. To build this kind of Zap with guidance, see our Zapier training.

Triggers

The 12 Membership.io triggers

12 events start a Zap when something happens in Membership.io, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

File Processed

Polling trigger

In Zapier“Triggers when a file has been processed.”

Starts the Zap once a file has finished processing in Membership.io. It is the signal that an upload is usable, not just that it arrived.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
after Add File in another Zap, wait for this event before dropping the file into a playlist.
Watch out
files processed before the Zap was switched on are never picked up.
2

Hub Onboarding Completed

Instant trigger

In Zapier“Triggers when any audience member completes hub onboarding.”

Fires when any audience member completes onboarding in the hub you pick. It marks the moment a new member has actually settled in.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
tag the member, send a first lesson from your email tool, or alert whoever looks after new members.
Watch out
the Hub field is required, so pick the hub at setup and confirm at test which hub the event comes from.
3

New Audience

Polling trigger

In Zapier“Triggers when a new audience is created.”

Reacts to a new audience member being created in your account. In Membership.io, the audience is your list of people, whatever the hub.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
copy each new person to your CRM or mailing list.
Watch out
as a general rule, a Zap that writes where its own trigger watches can set itself off again; check at test what your actions write.
4

New Audience Activity

Polling trigger

In Zapier“Triggers when a new audience activity is created.”

Goes off when a new activity is recorded for the audience member you choose. It follows one person rather than the whole account.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
keep an eye on a key member, a test account or a pilot user, and log what they do.
Watch out
the Audience field is required, so the trigger is tied to that single member; what an activity contains is something to check at test.
5

New Audience Tag

Polling trigger

In Zapier“Triggers when a new audience tag is created in the account.”

Triggers when a new audience tag is created in the account. This is about the tag itself appearing in your list of tags, not about a person receiving one.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
mirror your Membership.io tags in another tool so both keep the same vocabulary.
Watch out
do not build a tagging workflow on it expecting one run per tagged member.
6

New File

Polling trigger

In Zapier“Triggers when a new file is added in searchie.”

Picks up each new file added to your Membership.io library. It reports the upload; processing has a trigger of its own.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
keep a content inventory in a spreadsheet, one row per upload.
Watch out
if the next step needs a processed file, File Processed is the trigger made for that.
7

New File to Playlist

Polling trigger

In Zapier“Triggers when file(s) are added to a playlist.”

Notices when one or more files are added to the playlist you select. It watches the arrangement of your content, not the uploads.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
let the people following that playlist know new content is in.
Watch out
the Playlist field is required, so the trigger watches one playlist only.
8

New Folder

Polling trigger

In Zapier“Triggers when a new folder is created.”

Runs when a new folder is created in Membership.io. Folders are where files land, so this is the earliest sign of a new batch of content.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
open a matching folder or task in your project tool, so production follows the library.
Watch out
no Zapier action creates folders, so this trigger only sees folders made in the app.
9

New Hub

Polling trigger

In Zapier“Triggers when a new Hub is created.”

Fires when a new hub is created. A hub is the members' space you give access to, so a new one usually means a new offer.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
log every hub in a shared sheet, so the team knows which spaces exist.
Watch out
hubs created before the Zap was published will not come through.
10

New Playlist

Polling trigger

In Zapier“Triggers when a new playlist is created.”

Kicks in when a playlist is created in your account. Playlists order your files into something a member follows from start to end.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
create a launch checklist in your task tool for every new playlist.
Watch out
playlists that existed before the Zap was published will not come through.
11

New Playlist to Hub

Polling trigger

In Zapier“Triggers when playlist(s) are added to a hub.”

Catches one or more playlists being added to the hub you choose. That is the moment content actually becomes visible to that hub's members.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
email the hub's members that a new module is waiting for them.
Watch out
the Hub field is required; check at test that the event comes from the hub you picked.
12

New Widget or Plugin

Polling trigger

In Zapier“Triggers when a new widget or plugin is created.”

Responds to a new widget or plugin being created in Membership.io. It is the most technical trigger of the list, aimed at whoever builds the site.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
keep a record of every widget a teammate adds, so nothing ends up on the site unnoticed.
Watch out
check at test what the step carries before mapping it anywhere.
Actions

The 16 Membership.io actions

Membership.io gives you 16 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Achievement

Action

In Zapier“Add manual achievements to audience members.”

Hands manual achievements to an audience member, by email or Hash ID. Useful for rewarding something that happens outside the platform.

When to use it
a member attends a live session tracked in another tool and earns a badge for it.
Watch out
both the Audience and the Achievements fields are required.
2

Add or Update Audience

Action

In Zapier“Adds audience to a Searchie account.”

Adds a person to your audience from an email address. If someone with that email already exists, it updates them instead of creating a duplicate.

When to use it
a buyer from your checkout tool should exist in Membership.io before getting hub access.
Watch out
Remove Existing Tags? wipes all of the person's tags, permanently. Leave it off unless that is exactly the goal.
3

Add Audience Tag

Action

In Zapier“Adds an Audience Tag”

Puts one or more tags on an audience member, found by email or Hash ID. Tags are how you sort people inside Membership.io.

When to use it
mark members who finished onboarding, or who came from a given campaign.
Watch out
check at test that the email you map matches an existing member.
4

Add File

Action

In Zapier“Add file to a Folder.”

Adds a file to a folder from a URL. You also set Auto Processs?, a required choice about processing the file once it lands.

When to use it
a file saved in another tool should go straight into your library.
Watch out
the folder must already exist, as no action creates one.
5

Add File Tag

Action

In Zapier“Adds a tag to a file.”

Tags a file in your library, with the File field as its one requirement. It keeps content searchable once the library grows.

When to use it
label each new file by topic once File Processed reports it.
Watch out
check at test which file reference the previous step passes along.
6

Add File(s) to Playlist

Action

In Zapier“Adds file(s) to a playlist.”

Places one or more files into a playlist. Both the files and the playlist are required, so the previous step has to pass along which files go in.

When to use it
push processed files into the series they belong to, without opening the app.
Watch out
the playlist must already exist, as no action creates one.
7

Add Folder(s) to Playlist

Action

In Zapier“Adds folder(s) to a playlist.”

Drops whole folders into a playlist in one go, with playlist and folders as required fields.

When to use it
a finished batch of files, gathered in a folder, becomes a playlist module.
Watch out
the playlist must exist beforehand.
8

Add Hub Access

Action

In Zapier“Adds a Hub access to an audience.”

Opens one or more hubs to an audience member, identified by email or Hash ID. A switch can also email them the hub login link.

When to use it
right after a payment, to let the buyer into the hub they paid for.
Watch out
to be sure the person exists, put Add or Update Audience before it.
9

Add Tag(s) to Playlist

Action

In Zapier“Adds tag(s) to a playlist.”

Attaches one or more tags to a playlist, so playlists can be sorted the same way files and people are.

When to use it
mark a playlist by level or theme once it is published to a hub.
Watch out
playlist and tags are both required.
10

Delete Audience

Action

In Zapier“Deletes an Audience”

Deletes an audience member, picked by email or Hash ID. This is the strongest action of the list.

When to use it
a deletion request from your support tool should remove the person from Membership.io too.
Watch out
if you only want to close access, Remove Hub Access is the lighter option.
11

Remove Achievement(s) From an Audience

Action

In Zapier“Removes achievement(s) from an audience”

Withdraws one or more achievements from an audience member. Both the member and the achievements to remove are required, so the Zap has to know exactly which badge goes.

When to use it
correct a badge granted by mistake by another Zap.
Watch out
run the test and read what comes back before switching the Zap on.
12

Remove Audience Tag

Action

In Zapier“Remove an Audience Tag”

Strips one or more chosen tags from an audience member, by email or Hash ID, and leaves the others alone.

When to use it
a trial ends and the trial tag should go.
Watch out
this is the targeted way; the switch inside Add or Update Audience removes every tag.
13

Remove File(s) From a Playlist

Action

In Zapier“Removes file(s) from a playlist”

Pulls one or more files out of a playlist, the reverse of Add File(s) to Playlist.

When to use it
retire an outdated lesson from a series.
Watch out
playlist and files are both required, so the files must be identified upstream.
14

Remove Folder(s) From a Playlist

Action

In Zapier“Removes folder(s) from a playlist”

Detaches whole folders from a playlist, the reverse of adding them, with playlist and folders required.

When to use it
swap an old batch of files for a newer one.
Watch out
run it on a test playlist first to see the result.
15

Remove Hub Access

Action

In Zapier“Removed a Hub access for an audience”

Takes away access to one or more hubs from an audience member, by email or Hash ID, and needs the list of hubs to close.

When to use it
a subscription ends in your billing tool and the hub should close for that person.
Watch out
pick the hubs carefully, since the Zap applies it without asking.
16

Remove Tag(s) From a Playlist

Action

In Zapier“Removes tag(s) from a playlist”

Removes chosen tags from a playlist, the reverse of Add Tag(s) to Playlist. The playlist and the tags are both required, so name them precisely.

When to use it
clear a temporary label once a promotion ends.
Watch out
check at test that the tag names match exactly.
Searches

The Membership.io search

1 search step looks for data that already exists in Membership.io, so a later step can use it.

A search step sits at the bottom of the action list, under the SEARCH heading of Action event. It finds an existing record so later steps can use it, and some fields offer + Add search step to insert one just before. Adding it makes the Zap multi-step.

1

Find Audience

SearchFind or create

In Zapier“Finds an Audience”

Looks up an audience member from an email address, its one required field. The editor also lists Find or Add Audience: it is this same search with the create box ticked, not a separate operation.

When to use it
check whether a buyer already exists before granting hub access.
Watch out
whether it wants the exact email or something close is decided by Membership.io; test with a real address.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that relied on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking this box turns the search into find-or-create: the setting above disappears and the step asks for the fields needed to create the missing item.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or hand all of them on at once.
When it breaks

When a Membership.io Zap breaks

Zapier attaches no help article to Membership.io and lists no rate limit for it. What breaks comes from Zapier's general rules and from a couple of fields.

  • No catch-up on the past

    A Zap only reacts to what happens after it is switched on. Members, files and playlists created before stay out; moving that backlog is a separate job.

  • A Zap that sets itself off

    A Zap that writes into the place its own trigger watches can start itself again and again and burn through your tasks. Check any such pair at test.

  • Flood protection after an import

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

  • Seen once, never twice

    On the 11 polling triggers, Zapier keeps track of what it has already seen, so the same file or member does not start the Zap twice.

  • Every tag gone at once

    Remove Existing Tags? in Add or Update Audience removes all of the person's tags, and the change is permanent. Leave it off by default.

  • A hub, playlist or folder missing

    Most actions need a hub, playlist or folder that already exists. No action creates one, so build them in Membership.io first.
Need help

Need help automating Membership.io with Zapier?

A person reads every message.

FAQ

Membership.io Zapier integration: frequent questions

01Is the Membership.io Zapier integration free?
Yes, for Zaps of two steps. Membership.io is not a premium app on Zapier, so the free plan can use it. That plan gives 100 tasks a month and an unlimited number of Zaps, each with one trigger and one action. A Zap that tags members after Hub Onboarding Completed fits. Add a second action, a filter or the Find Audience search, for example to check a buyer exists before Add Hub Access, and the Zap turns multi-step and needs a paid plan.
02How many tasks does a Membership.io Zap use?
One task for each action that succeeds, nothing for the trigger, and nothing for Zapier checking for new items. A Zap that runs Add or Update Audience then Add Hub Access costs two tasks per buyer. A Zap that logs each New File in a spreadsheet costs one per file. An action that fails is not counted. On a busy library, file and playlist triggers are the ones to watch, because each new item runs the Zap again.
03Does Membership.io trigger Zaps in real time?
Only one trigger does: Hub Onboarding Completed is instant, so Membership.io tells Zapier the moment a member finishes onboarding, whatever your plan. The 11 others, from New Audience to New Widget or Plugin, are polling triggers. Zapier checks them on your plan's interval: every 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. If speed matters, build around the onboarding trigger, or plan for that delay in what you promise members. A lightning bolt in the editor marks the instant one.
04What does it take to connect Membership.io to Zapier?
An account on Membership.io, plus read or write access on anything you do not own yourself and want the Zap to touch. You connect it once from the Apps page of Zapier with + Add connection, pick Membership.io, sign in in the tab that opens and allow access. Before building, create the hubs, playlists and folders your actions will point to, since none of the 16 actions can create them. Every step that uses Membership.io then reuses this one connection.
05Why did all the member's tags disappear?
Because Remove Existing Tags? was switched on in Add or Update Audience. That option removes all existing tags from the person, and the removal is permanent. It is easy to tick while mapping fields and forget. To take away a single tag, use Remove Audience Tag instead, which only removes the tags you name. Before publishing any Zap that updates audience members, open that step and check the switch is off unless you really want a clean slate.
06What if the Membership.io operation you need is not listed?
Then Zapier cannot do it with this app, and no setting will add it. See first whether two steps cover it: Find Audience followed by an action, for instance, replaces a missing lookup inside the action. Creating hubs, playlists or folders and deleting files are not offered, and the only search looks up audience members. The Membership.io page on Zapier shows the current list of operations, so check it there before planning a Zap around something missing.
07Zapier, Make or n8n for Membership.io?
Decide on your flow, not on a ranking. Write it down step by step. If it is one event and one action, such as tagging members after onboarding, Zapier runs it on the free plan. If it chains Find Audience, Add or Update Audience and Add Hub Access, it is multi-step on Zapier and needs a paid plan. Then look at timing: 11 of the 12 triggers here wait for an interval. Price that same written flow on each tool before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations