MRPLN Zapier integrationAutomate MRPLN with Zapier.
The MRPLN Zapier integration gives you 1 trigger, 3 actions and 1 search. A new customer can start a Zap, other apps can create or update customers, send them a templated email, SMS or WhatsApp message, and find them first. Costs and pitfalls below.
Verified Trustpilot reviews · AI, automation & growth agency
What the MRPLN Zapier integration actually does
MRPLN is an online marketing tool where you plan campaigns, automate them and read the results, with AI built in. Plugged into Zapier, it exchanges customer records with your other apps and can send messages: customers created elsewhere land in MRPLN, and new MRPLN customers can be passed on.
Three results you can build. A welcome message on the right channel: New Customer starts the Zap, then Send Message to Customer sends an approved email, SMS or WhatsApp template. Customers captured once: Create Customer adds the person from a form or a CRM contact, with opt-in choices for each channel. Records that stay current: Find Customer looks the person up by email, SMS number or WhatsApp number, then Update Customer changes the record by its ID.
One detail worth knowing early: in Send Message to Customer, the When to Send field defaults to an immediate send, and its help also mentions scheduling the message for a later date and time.
What Zapier does not do here. Nothing deletes a customer, and templates cannot be written from Zapier: the message action only picks an approved one. The only trigger polls, so nothing on MRPLN starts a Zap instantly. Before choosing a platform, see our Make vs Zapier comparison or our Zapier review.
Zapier words in one minute
Eight words the Zapier editor uses everywhere, in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts a Zap, such as a new customer added in MRPLN. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like sending a message.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of those.
- Polling vs instant
- A polling trigger is checked on a timer for new items; an instant one is reported by the app itself. The MRPLN trigger polls.
- 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 something that already exists in an app, so the steps after it can use what it found.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it then needs a paid plan.
What MRPLN on Zapier really costs
Zapier bills completed actions, not checks. The trigger never costs a task, and looking for new customers is free however often Zapier looks.
- Free plan100 tasks a month, unlimited two-step Zaps
- MRPLN on freeYes, not reserved for paid plans
- Trigger checksNever billed
- Search, filter or second actionPaid plan required
Every action that succeeds counts once; one that fails is not counted. MRPLN is not reserved for paid plans, so it runs on the free plan: 100 tasks a month and unlimited Zaps of two steps each. A filter, Find Customer or a second action turns the Zap into a multi-step one, which needs a paid plan. The grid shows how often Zapier checks the New Customer trigger on each plan. The trigger is the only polling step on this app.
Connect your MRPLN account
- 01
Open Apps and add a connection
Go to the Apps page of your Zapier account and click + Add connection. You need an MRPLN account, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick MRPLN
Type MRPLN in the search box of the dialog, select it and click Add connection. A new tab opens on the MRPLN sign-in screen, where the next step happens.
- 03
Sign in and grant access
Log in to MRPLN in that tab, then grant Zapier access to the account. Every MRPLN step in your Zaps reuses this connection afterwards, so you only do it once.
Your first Zap: greet selected new customers with a template
GoalWhen a new customer is added in MRPLN and passes a filter, send them an approved message template on the channel you choose.
- 01
Set the trigger
Create a Zap, choose MRPLN as the trigger app and
New Customeras the event, then select the MRPLN connection made earlier. - 02
Test the trigger
Run the test. Zapier brings back the three most recent items of the connected account, so you map fields on a real customer rather than a blank one.
- 03
Add the filter
Click the plus icon, choose Filter and set the field to look at, the rule and the value. A filter makes the Zap multi-step, so this step needs a paid plan.
- 04
Add Send Message to Customer
Pick MRPLN again with
Send Message to Customer. Choose the channel, then an approved template of that channel, and set When to Send. Test the step and check what was sent. - 05
Publish
Click Publish to switch the Zap on. Only customers added after this point get the message; existing ones are left alone.
MRPLN trigger
1 event starts a Zap when something happens in MRPLN. Zapier checks for them at the interval your plan allows.
New Customer
Polling triggerIn Zapier“Triggers when a new customer is added.”
Starts a Zap each time a customer is added in MRPLN and hands that record to the next step, so other tools or an MRPLN message can follow without anyone retyping the details.
MRPLN actions
MRPLN gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Customer
ActionIn Zapier“Create/Add new customer.”
Adds a new customer to MRPLN from data that reached another app, such as a form submission or a CRM contact.
Send Message to Customer
ActionIn Zapier“Send an email, SMS, or WhatsApp message to a customer using an approved template”
Sends a customer an email, SMS or WhatsApp message built from an approved template of that channel.
Update Customer
ActionIn Zapier“Updates an existing customer's information.”
Changes the details of a customer already in MRPLN, including the opt-in status of each channel.
Find Customer in front. Opt-in fields left empty keep their current value.MRPLN search
1 search step looks for data that already exists in MRPLN, so a later step can use it.
A search step finds an existing record and passes it on. In the editor it sits at the bottom of the Action event list, under the SEARCH heading, and it makes the Zap multi-step. Three settings decide what happens when the result is not one clean match.
Find Customer
SearchFind or createIn Zapier“Finds an existing customer”
Looks a customer up in MRPLN by email address, SMS phone number or WhatsApp number, and passes the record, ID included, to the next steps.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this box turns the search into a find-or-create: the setting above disappears and the step asks for the fields needed to create the missing item.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When the MRPLN Zap breaks
Zapier lists no limit and no error specific to MRPLN. What can go wrong comes from how every Zap works.
Four cases to know before you publish. If a Zap behaves oddly, our Zapier troubleshooting guide is the next stop.
Existing customers never show up
A Zap only reacts to what happens after it is switched on. Customers that already existed are not picked up; moving that backlog is a separate job.A Zap that keeps setting itself off
A Zap that writes into the very place its own trigger watches can start itself again and again, and burn through your task count fast.A bulk import is held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.The same customer twice? No
On a polling trigger Zapier keeps track of what it has already seen, so the same item does not start the Zap twice.
Need help automating MRPLN with Zapier?
A person reads every message.



