Resources · Zapier integration

Membrain Zapier integrationAutomate Membrain with Zapier.

Membrain Zapier integration: 24 triggers, 21 actions, 22 searches. Prospects, sales projects, tickets, flows and contacts can each start a Zap (an automation built on Zapier), be created or updated by one, or be looked up along the way.

See the 67 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Membrain Zapier integration does for you

The Membrain Zapier integration ties your sales CRM to the rest of your tools. Twenty-four events in Membrain can start an automation, twenty-one actions write into it, and twenty-two searches find an existing record so a later step can update it. Every trigger here is checked on a timer, not pushed.

A won deal handed straight to delivery. Sales Project Won fires when a project closes. The Zap creates the matching entry in the tool your delivery team works in, so nobody has to forward the deal by hand.

Web leads that land as prospects. A new entry in your form tool goes to Create Prospect. Its Company field takes a company name or the Id (GUID) of an existing company.

Support requests that become tickets. Create Ticket opens a ticket in the process you choose, and Ticket Resolved can later tell the requester's side that it is closed.

What Zapier doesn't do here. No trigger is instant: Zapier checks Membrain at the interval of your plan, so nothing starts the moment a record changes. No action deletes anything. Every update action needs the Id (GUID) of the record, which means a search step first whenever the trigger doesn't carry it. And there is no find-or-create variant, so a missing record means a separate Create step.

For the setup work, open our Zapier agency page. If a Zap stops behaving, see our Zapier troubleshooting guide.

Vocabulary

Zapier words, in plain English

Eight words carry this page. Below, each one is used 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. Once the Zap is on, Zapier waits for it. Membrain offers twenty-four.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance of your plan is a count of these.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items and keeping only the unseen ones. All Membrain triggers work this way.
Instant trigger
A trigger the app reports itself the moment the event happens, with no check to wait for. Membrain has none of these.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up a record that already exists, so the steps after it can use what it found, such as an Id.
Cost

What Membrain costs you in Zapier tasks

The trigger never costs a task, and Zapier checking Membrain for new records costs nothing either, however often it looks. Only a completed action is billed, one task each; an action that fails isn't counted.

  • Trigger and checks0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

Membrain isn't a premium app, so it runs on the free plan: 100 tasks a month, unlimited Zaps, two steps each. A filter, a second action or a search step turns the Zap into a multi-step Zap, which needs a paid plan. An update Zap that has to find its record first carries a search, so it is multi-step. The grid below sets how often Zapier checks each Membrain trigger, by plan. On paid plans, that interval can be changed.

Connect

Connect Membrain to Zapier in three steps

  1. 01

    Open Apps and add a connection

    In your Zapier account, open the Apps page and click + Add connection. A dialog with a search box opens: type Membrain and pick it from the list of results.

  2. 02

    Sign in to Membrain

    Click Add connection. Membrain opens in a new tab: sign in with the account the Zaps should act as. You need an account on the app, plus read or write access to records you don't own yourself.

  3. 03

    Grant access

    Sign in to Membrain in the tab that opens and grant Zapier access to the account. The connection is saved once; every Membrain step in every Zap then picks it from a list.

First Zap

Your first Zap: a won deal goes to delivery

GoalWhen a sales project is won in Membrain, create a project in the tool your delivery team uses, with a filter that keeps only the deals you pick.

  1. 01

    Create the Zap on Sales Project Won

    Create a Zap, pick Membrain as the trigger app and Sales Project Won as the event. The connection you set up earlier appears in the account list.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent won projects of the connected account, so the mapping is done on a real deal, not on a blank example.

  3. 03

    Add the filter

    From the plus icon, add a filter and fill its three boxes: the field to look at, the rule, the value. Use a text rule on text, a number rule on numbers. The filter makes the Zap multi-step.

  4. 04

    Add the project step

    Pick your project tool and its create action. Map the deal details coming from Membrain into its fields, checking in the test result which values really arrive.

  5. 05

    Test, then publish

    Test the action and look at the new project. Then publish the Zap to switch it on. Deals won before that moment are not picked up.

Triggers

The 24 Membrain triggers

24 events start a Zap when something happens in Membrain. Zapier checks for them at the interval your plan allows.

1

Account Growth Project Archived

Polling trigger

In Zapier“Triggers when an Account Growth Project is archived”

Starts a Zap when an account growth project is archived in Membrain, so the tools that follow that project can close their side as well.

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
a project tracker or report should drop the account once the growth project is put away.
Watch out
only projects archived after the Zap is on count; older ones are not picked up.
2

Account Growth Project Created

Polling trigger

In Zapier“Triggers when a new Account Growth Project is created”

Picks up every new account growth project created in Membrain, whoever opened it and in whichever process.

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
the account manager needs a task, a message or a line in a shared sheet each time an expansion effort opens.
Watch out
it fires for new projects in every process; add a filter if only one process matters, knowing that it makes the Zap multi-step.
3

Account Growth Project Moved to Stage

Polling trigger

In Zapier“Triggers when an Account Growth Projects is moved to a specific Stage”

Reacts when an account growth project reaches the stage you pick. Each stage of your process can lead to its own follow-up outside Membrain.

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
one stage, such as a proposal step, should hand something to another team.
Watch out
the Stage field is required, so one Zap follows one stage.
4

Account Growth Project Won

Polling trigger

In Zapier“Triggers when an Account Growth Project is won”

Fires on account growth projects marked as won, which turns a result recorded in Membrain into a signal for your other tools.

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
a win should reach finance, delivery or a team channel without anyone copying the details.
Watch out
wins recorded before the Zap was published stay out of it.
5

Activity Created

Polling trigger

In Zapier“Triggers when a new Activity is created in Membrain. An Activity can be any of an Email, Call, Note, Appointment or Task”

Catches every new activity in Membrain, and an activity can be an email, a call, a note, an appointment or a task. That makes it the broadest trigger of the list.

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
you want a log of sales activity in a spreadsheet or reporting tool.
Watch out
since five kinds of activity arrive here, add a filter if only one kind matters.
6

Company Created

Polling trigger

In Zapier“Triggers when a new Company is created”

Runs your Zap each time a company is added to Membrain, which keeps the list of accounts in step with the tools around the CRM.

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
your accounting tool or address book should know every new company account.
Watch out
several Create actions can add a company from a name they don't recognise, so check at the test step what reaches this trigger.
7

Content Hub Item Created

Polling trigger

In Zapier“Triggers when a Content Hub Item Created.”

Watches the Content Hub of Membrain and starts a Zap for each new item placed there.

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
the sales team should hear about new material in their chat or email.
Watch out
items added before the Zap is switched on are never sent.
8

Flow Archived

Polling trigger

In Zapier“Triggers when a Flow is archived”

Signals that a flow has been archived. A flow lives in a Membrain process, and this trigger tells other tools that it has been put away.

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
a mirror of your flows elsewhere should close the matching entry.
Watch out
nothing archived before publishing is replayed.
9

Flow Created

Polling trigger

In Zapier“Triggers when a new Flow is created”

Hands Zapier every new flow created in a Membrain process, whether a person or another automation made it.

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
each new flow should open a task or a line in a planning sheet.
Watch out
flows that existed before the Zap is published stay out; moving them is a separate job.
10

Flow Moved to Stage

Polling trigger

In Zapier“Triggers when a Flow has moved to a specific Stage”

Follows a flow into the stage you choose. Moving a flow forward in Membrain becomes the cue for work in another tool.

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
a given stage needs a document, a message or a handover.
Watch out
Stage is required; plan one Zap per stage you want to watch.
11

Flow Won

Polling trigger

In Zapier“Triggers when a Flow is won”

Reports flows that end as won, so a successful outcome in any process can travel beyond Membrain.

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
a win in a process other than sales projects should be announced or recorded somewhere else.
Watch out
test with a recently won flow so the mapping uses real values.
12

Contact Created

Polling trigger

In Zapier“Triggers when a new Contact is created”

Sends each new contact person from Membrain to your Zap. These are the people attached to companies in Membrain.

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
a mailing list or another address book must stay in step with the CRM.
Watch out
contacts that existed before the Zap was published are not sent.
13

Prospect Disqualified

Polling trigger

In Zapier“Triggers when a prospect has been disqualified.”

Fires when a prospect is disqualified. Losing a lead is information too, and this trigger lets other tools act on it.

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
a disqualified lead should leave a nurturing sequence or land in a review list.
Watch out
the editor shows Prospect Disqualified; search for that label, not for archived.
14

Prospect Created

Polling trigger

In Zapier“Triggers when a new Prospect is created”

Brings every new prospect into your Zap, from whichever prospecting process it was created in.

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
a new lead should get a welcome email or a slot in someone's task list.
Watch out
prospects created before the Zap is published are not sent.
15

Prospect Moved to Stage

Polling trigger

In Zapier“Triggers when a Prospect is moved to a specific Stage”

Watches one stage of your prospecting process and starts the Zap when a prospect enters it.

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
qualification steps should trigger a call task, an email or a note to a manager.
Watch out
the Stage field is required, so one Zap tracks one stage.
16

Prospect Won

Polling trigger

In Zapier“Triggers when a Prospect is converted to a Sales Project.”

Triggers when a prospect is converted into a sales project, which is what won means for a prospect in Membrain.

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
the move from lead to real opportunity should be counted or announced elsewhere.
Watch out
test with a recent conversion, since only conversions after publishing are sent.
17

Sales Project Archived

Polling trigger

In Zapier“Triggers when a Sales Project is archived”

Lets a Zap react when a sales project is archived, so whatever tracks the deal outside Membrain can be updated.

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
a forecast sheet or a team channel should drop the deal once it is put away in Membrain.
Watch out
archives done before publishing are not replayed.
18

Sales Project Created

Polling trigger

In Zapier“Triggers when a new Sales Project is created”

Collects every new sales project in Membrain, whatever process it belongs to and whoever created it.

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
each new opportunity needs a folder, a quote draft or a line in a pipeline sheet.
Watch out
add a filter if only some processes matter to this Zap.
19

Sales Project Moved to Stage

Polling trigger

In Zapier“Triggers when a Sales Project is moved to a specific Stage”

Tracks sales projects entering a chosen stage of your sales process, so each step of the pipeline can call for its own action.

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
a negotiation or contract stage should alert legal, finance or a manager.
Watch out
Stage is required; a project moved through several stages fires only for the one you picked.
20

Sales Project Won

Polling trigger

In Zapier“Triggers when a Sales Project is won”

A natural start for a handover: it starts a Zap for every sales project marked as won.

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
delivery, invoicing or onboarding should start from the closed deal.
Watch out
deals won before the Zap goes live stay out; moving them is a separate job.
21

Ticket Archived

Polling trigger

In Zapier“Triggers when a Ticket is archived”

Notices tickets that are archived in Membrain and passes them on, so support records elsewhere can be closed in turn.

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
a helpdesk copy or a report should mark the ticket as finished.
Watch out
archived and resolved are two different triggers; pick the one that matches your process.
22

Ticket Created

Polling trigger

In Zapier“Triggers when a new Ticket is created”

Opens a Zap run for every new ticket, whether it was typed in Membrain or created by another automation.

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
new tickets should reach a team chat or an on-call list.
Watch out
map fields on a real ticket, picked among the three most recent ones the trigger test brings back.
23

Ticket Moved to Stage

Polling trigger

In Zapier“Triggers when a Ticket is moved to a specific Stage”

Keeps an eye on one stage of your ticket process and reports each ticket that reaches it.

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
an escalation stage should page someone or open a task in another tool.
Watch out
the Stage field is required, so add one Zap per stage you care about.
24

Ticket Resolved

Polling trigger

In Zapier“Triggers when a Ticket is Resolved”

Announces resolved tickets, so the person or team waiting on the answer can hear about it outside Membrain.

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
a satisfaction survey or a closing message should follow each fix.
Watch out
the editor label is Ticket Resolved; look for that name in the event list.
Actions

The 21 Membrain actions

Membrain gives you 21 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Account Growth Project

Action

In Zapier“Creates a new Account Growth Project”

Opens an account growth project for an existing customer, inside the process you choose.

When to use it
a won deal or a renewal date elsewhere should start an expansion effort.
Watch out
Process, Name, Company and Owner are required; the Owner must be an existing Membrain user, while an unknown company name is created for you.
2

Create Completed Task

Action

In Zapier“Creates a new Completed Task shown in the Activity Stream”

Records a task that is already done, so it shows in the activity stream as history rather than as something to do.

When to use it
work finished in another tool should leave a trace on the company.
Watch out
Company Name and Contents are required, and a company name Membrain doesn't know is created automatically.
3

Create Appointment

Action

In Zapier“Creates an Appointment in Membrain”

Puts an appointment in Membrain with a title, a start and an end.

When to use it
meetings booked through a scheduling tool should appear in the CRM.
Watch out
From Date and To Date are in UTC, so convert local times before mapping them.
4

Create Call

Action

In Zapier“Create a Call in Membrain”

Logs a call in Membrain from text you pass in, such as a summary from your phone system.

When to use it
calls made outside Membrain should still show up in the record.
Watch out
Contents is required and takes plain text only, over several lines if needed.
5

Create Company

Action

In Zapier“Creates a new Company”

Adds a company to Membrain from just its name, the one required field.

When to use it
a new customer in your billing or signup tool should exist in the CRM.
Watch out
check at the test step how Membrain handles a name it already holds; Find Company by Name can run first.
6

Create Contact

Action

In Zapier“Creates a new Contact”

Creates a contact person attached to a company.

When to use it
a form, an event list or a meeting tool brings in people who should be in Membrain.
Watch out
Company Name and Contact Name are both required, so every contact needs a company to belong to.
7

Create Content Hub Item

Action

In Zapier“Creates a new Content Hub Item”

Adds an item to the Content Hub, the place where Membrain keeps material for the sales team.

When to use it
new documents published elsewhere should be offered to sellers in Membrain.
Watch out
Type and ContentType are required; pick them from the lists at the test step.
8

Create Flow

Action

In Zapier“Creates a new Flow in a specific Process”

Starts a new flow in a specific Membrain process, with the name you give it.

When to use it
a request arriving in another tool should begin a tracked process.
Watch out
Process and Name are required, so the process must exist before the Zap runs.
9

Create Note

Action

In Zapier“Creates a Note in Membrain”

Writes a plain note in Membrain from any text a previous step carried.

When to use it
comments, form answers or chat messages should be kept on the record.
Watch out
Contents is required and text only; for formatted text, use the rich text note below.
10

Create Prospect

Action

In Zapier“Creates a new Prospect”

Creates a prospect in the prospecting process you choose, tied to a company.

When to use it
leads from forms, ads or events should enter Membrain without retyping.
Watch out
Process and Company are required; Company takes a name or the Id (GUID) of an existing company.
11

Create Read Only Rich Text Note

Action

In Zapier“Creates a Read Only Rich Text Note”

Adds a formatted note that can't be edited afterwards in Membrain.

When to use it
a summary or report should be stored on the record exactly as it was produced.
Watch out
Contents must contain HTML formatting to be accepted; plain text alone is refused.
12

Create Sales Project

Action

In Zapier“Creates a new Sales Project”

Opens a sales project, the Membrain record for an opportunity, in the sales process you pick.

When to use it
a qualified request in another tool should become a deal in the pipeline.
Watch out
Process, Opportunity Name, Company and Owner are required; the Owner must already be a Membrain user.
13

Create Task

Action

In Zapier“Creates a Task in Membrain”

Puts a task to do in Membrain, written from the text you pass in.

When to use it
an event elsewhere means someone in sales has a follow-up to make.
Watch out
Contents is required and takes plain text over several lines.
14

Create Ticket

Action

In Zapier“Creates a new Ticket”

Raises a ticket in a chosen Membrain process, attached to a company.

When to use it
requests from a support form or inbox should be tracked in Membrain.
Watch out
Process, Name and Company are required; an unknown company name is created automatically.
15

Update Account Growth Project

Action

In Zapier“Updates an Account Growth Project in Membrain”

Changes an existing account growth project in place.

When to use it
new information from another tool should refresh a project you already track.
Watch out
the Account Growth Project Id (GUID) is required, so put one of the Find Account Growth Project searches before it.
16

Update Company

Action

In Zapier“Update an existing Company”

Edits the details of a company already in Membrain.

When to use it
addresses or account data change in your billing tool and the CRM should follow.
Watch out
Company Id (GUID) is required; get it from Find Company by Name or by External Identifier.
17

Update Flow

Action

In Zapier“Updates a Flow in Membrain”

Rewrites fields on a flow you already have in a process.

When to use it
progress recorded in another tool should be reflected on the flow.
Watch out
Flow Id (GUID) is required, which a Find Flow search can provide.
18

Update Sales Project

Action

In Zapier“Updates a Sales Project in Membrain”

Updates a sales project, the deal record of Membrain.

When to use it
a signed quote or a payment elsewhere should change the deal.
Watch out
Sales Project Id (GUID) is required; place Find Sales Project by Key or by Name before this step.
19

Update Contact

Action

In Zapier“Update an existing Contact”

Edits an existing contact person in Membrain.

When to use it
someone updates their details in a form or a newsletter tool.
Watch out
Contact Id (GUID) is required; Find Contact by Primary Email Address can provide it from the address a form sends.
20

Update Prospect

Action

In Zapier“Updates a Prospect in Membrain”

Changes a prospect already in a prospecting process.

When to use it
engagement measured in another tool should be written back to the lead.
Watch out
Prospect Id (GUID) is required, so search the prospect by key or name first.
21

Update Ticket

Action

In Zapier“Updates a Ticket in Membrain”

Modifies a ticket that already exists in Membrain.

When to use it
a reply or a fix logged in another tool should update the ticket.
Watch out
Ticket Id (GUID) is required; use Find Ticket by Key or by Name in the step before.
Searches

The 22 Membrain searches

22 search steps look for data that already exists in Membrain, so a later step can use it.

A search step looks up a record that already exists in Membrain and hands what it found to the steps after it. Here, that is mostly how a Zap gets the Id (GUID) that every update action asks for. The searches sit at the bottom of the action-event list, under their own SEARCH heading. Each one makes the Zap multi-step.

1

Find Account Growth Project by Id

Search

In Zapier“Find an Account Growth Project by its Id”

Fetches one account growth project when you already hold its Id, the long identifier rather than the readable AGP-123 key.

When to use it
an earlier step stored the Id and you need fresh details before acting.
Watch out
Id is the only field and it is required.
2

Find Account Growth Project by Key

Search

In Zapier“Find an Account Growth Project by its Key”

Looks a project up by its readable key, the kind shown as AGP-123.

When to use it
people quote the key in emails or forms, and the Zap must find the project from it.
Watch out
Key is required; check at the test step that the format you pass matches.
3

Find Account Growth Project by Name

Search

In Zapier“Find an Account Growth Project by its Name”

Searches account growth projects by name, the friendliest handle when no key travels with the data.

When to use it
another tool only knows the project title.
Watch out
two projects can share a name; set what happens with several results.
4

Find Company by External Identifier

Search

In Zapier“Find a Company by its External Identifier”

Finds a company through the identifier another system gave it, stored on the Membrain record.

When to use it
your billing or ERP tool is the reference and sends its own customer number.
Watch out
External Identifier is required, so the company must carry it in Membrain.
5

Find Company by Id

Search

In Zapier“Returns all data for a Company”

Returns all the data of one company from its Company Id (GUID).

When to use it
a trigger gave you the Id but not every field you need downstream.
Watch out
the Company Id (GUID) is required; a name won't work here.
6

Find Company by Name

Search

In Zapier“Find a Company by its Name”

Matches a company on its name, useful when an outside tool only knows the name.

When to use it
before Update Company, or before deciding whether to create a new one.
Watch out
whether the name must match exactly is decided by Membrain; test with a real spelling.
7

Find Flow by Id

Search

In Zapier“Find a Flow by its Id”

Retrieves a single flow from its Id.

When to use it
the Id came from a trigger or a stored value and you need the current state of the flow.
Watch out
Id is required and nothing else is accepted.
8

Find Flow by Key

Search

In Zapier“Find a Flow by its Key”

Locates a flow from a key in the F-123 style.

When to use it
a requester mentions the flow key and a later step must update it.
Watch out
Key is required; feed it as people write it, then confirm at the test step.
9

Find Flow by Name

Search

In Zapier“Find a Flow by its Name”

Searches flows by their name.

When to use it
the other tool knows the flow title but not its key or Id. Name is the only field it asks for.
Watch out
similar names can return several results; choose first, stop or all.
10

Find Sales Project by Id

Search

In Zapier“Find a Sales Project by its Id”

Pulls up a sales project from its Id, not from the SP-123 key people quote.

When to use it
you need the latest values of a deal whose Id an earlier step carried.
Watch out
Id is required; without it, use the key or name search.
11

Find Sales Project by Key

Search

In Zapier“Find a Sales Project by its Key”

Finds a deal from its key, in the SP-123 form, and hands its Id to Update Sales Project.

When to use it
quotes or contracts carry the key and should update the right deal.
Watch out
Key is required; test with a key copied from Membrain itself.
12

Find Sales Project by Name

Search

In Zapier“Find a Sales Project by its Name”

Looks a sales project up by its name.

When to use it
before Update Sales Project, when only the deal title travels.
Watch out
two deals can share a name, and whether the match must be exact is decided by Membrain; decide what several results should do.
13

Find Contact by Company Name and Name

Search

In Zapier“Find a Contact by the name of the Company that Contact belongs to and the Contacts full name”

Combines the company name and the full name of the person to find one contact.

When to use it
no email is available, but you know who and where. The person must belong to that company in Membrain.
Watch out
Company and Name are both required.
14

Find Contact by Primary Email Address

Search

In Zapier“Finds a Contact by its Email Address”

Identifies a contact from their main email address.

When to use it
a form or a mailing tool sends an email, and Update Contact must follow with the Id the search returns.
Watch out
Email Address is required; only the primary address is searched.
15

Find Contact by External Identifier

Search

In Zapier“Find a Contact by its External Identifier”

Reaches a contact through the identifier another system gave them.

When to use it
a member or customer number from another tool is the shared reference.
Watch out
External Identifier is required and must already be stored in Membrain, so set it on the contact before the Zap relies on it.
16

Find Contact by Id

Search

In Zapier“Find a Contact by its Id”

Brings back one contact from its Id, with the details Membrain holds on that person right now.

When to use it
a trigger handed over the Id and you want the full, current contact.
Watch out
Id is required; with only an email at hand, use Find Contact by Primary Email Address instead.
17

Find Prospect by Id

Search

In Zapier“Find a Prospect by its Id”

Retrieves one prospect from its Id, not from its readable P-123 key.

When to use it
a stored Id must turn back into a full prospect before an update.
Watch out
Id is required; the key and name searches cover the other cases.
18

Find Prospect by Key

Search

In Zapier“Find a Prospect by its Key”

Finds a prospect from a key written like P-123.

When to use it
sellers pass the prospect key around and a Zap should act on it.
Watch out
Key is required; test with a key copied from a real prospect, then let Update Prospect use the Id it returns.
19

Find Prospect by Name

Search

In Zapier“Find a Prospect by its Name”

Searches prospects by name when the data carries neither a P-123 key nor an Id.

When to use it
the other tool only knows the prospect title, ahead of Update Prospect.
Watch out
Name is required, and several matches follow the multiple-results setting.
20

Find Ticket by Id

Search

In Zapier“Find a Ticket by its Id”

Reads one ticket from its Id, the long identifier that Update Ticket also asks for.

When to use it
you need the current state of a ticket before replying or updating.
Watch out
Id is required; a T-123 key goes to Find Ticket by Key instead.
21

Find Ticket by Key

Search

In Zapier“Find a Ticket by its Key”

Locates a ticket from a key in the T-123 format, the one customers can quote back.

When to use it
replies arrive with the ticket key and must update the right ticket.
Watch out
Key is required; test with a key taken from Membrain.
22

Find Ticket by Name

Search

In Zapier“Find a Ticket by its Name”

Searches tickets by their name, with no key or Id needed.

When to use it
no key or Id is available, only the ticket title.
Watch out
titles repeat easily; set what happens with several results, and whether the Zap stops when none matches.

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 there and the steps that depend on it are skipped. Switched on, the Zap carries on without a result.
  2. Create X if it doesn't exist yet?
    Ticking it turns a search into a find-or-create. Zapier lists no such variant for Membrain, so don't count on it here: check at the test step whether the box shows up at all, and plan a separate Create step for a missing record.
  3. If multiple search results are found?
    Three ways out when several records match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks

When a Membrain Zap breaks

Zapier documents no rate limit or error message specific to Membrain. What goes wrong comes from the general rules of Zapier and from the way the Membrain actions are built.

Six cases worth knowing before a Zap goes live: three come from Zapier itself, three from the required fields of Membrain.

  • Nothing from before the Zap

    A Zap only reacts to what happens after you switch it on. Deals won or tickets created earlier are not picked up; 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 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.

  • Updates without an Id

    Every Membrain update action requires the Id (GUID) of the record. When the trigger doesn't carry it, put a search step before the update to find it.

  • Owner must exist

    Create Sales Project and Create Account Growth Project need an Owner who is an existing Membrain user, given by name, email or Id.

  • Rich text note refused

    Create Read Only Rich Text Note only accepts contents that contain HTML formatting. Plain text from an earlier step is not enough.
Need help

Need help automating Membrain with Zapier?

A person reads every message.

FAQ

Membrain and Zapier: questions people ask

01Is the Membrain Zapier integration free?
Yes. Membrain isn't a premium app, so its triggers, actions and searches all work on the free plan of Zapier. That plan gives 100 tasks a month and an unlimited number of Zaps, each limited to two steps: one trigger and one action. Sales Project Won followed by a single action fits. A search, a filter or a second action makes the Zap multi-step and needs a paid plan, which matters here because an update needs the Id of the record, and a search is how a Zap finds it when the trigger doesn't carry it.
02How many tasks does a Membrain Zap use?
One per action that completes. The trigger costs nothing, and the checks Zapier runs on Membrain cost nothing either, however often they happen. A Zap that creates a ticket uses one task per run. A Zap that searches a contact and then updates it is billed for the update; read the task count after your first test to see how the search step is counted on your account. An action that fails is not counted.
03Is Membrain on Zapier real time?
No. All 24 Membrain triggers are polling triggers: Zapier asks Membrain for new records at a fixed interval, then keeps only what it hasn't seen. That interval depends on your plan: every 15 minutes on Free, every 2 on Professional, every minute on Team and Enterprise. The type is set by Membrain and can't be changed in the editor. On paid plans, the interval can be adjusted and a check can be run by hand from the editor.
04What does it take to connect Membrain to Zapier?
A Membrain account, plus read or write access to the records you don't own yourself. On the Apps page of Zapier, click + Add connection, search for Membrain, click Add connection, sign in in the tab that opens and grant access. The connection is saved and reused by every Membrain step. Before building, make sure the processes and stages you will pick exist, and that the Owner you assign to new projects is an existing Membrain user.
05Why does a Membrain update action need a search step first?
Because every update action asks for the Id (GUID) of the record: Update Company, Update Contact, Update Sales Project, Update Prospect, Update Ticket, Update Flow and Update Account Growth Project. Outside tools don't necessarily carry that Id. A search such as Find Contact by Primary Email Address or Find Sales Project by Key turns what you do have into the Id, and the update maps it. That extra step makes the Zap multi-step, so plan for a paid plan.
06What if the Membrain operation you want isn't on Zapier?
Then it isn't part of this integration today. The Membrain page on Zapier shows the current list of operations, so check it before building around a gap. As listed here, none of the 67 operations deletes a record or creates a Membrain user. If what's missing is a lookup, scan the 22 searches first: companies, contacts, prospects, sales projects, tickets, flows and account growth projects each have several ways in. If nothing fits, that step stays a manual one in Membrain.
07Zapier, Make or n8n for Membrain?
Choose on criteria, not on a ranking. On Zapier, Membrain brings a wide catalogue, works on the free plan, and every trigger is polled at the interval of your plan. On Make or n8n, first check whether a Membrain connector exists and what it covers. Then compare how each tool counts usage, how many search-then-update chains your flows need, since each one adds a step on Zapier, and who will maintain the automations over time.
Same platform

Other docs you might need on this stack.

Browse all integrations