MerrenIO Zapier integrationAutomate MerrenIO with Zapier.
MerrenIO Zapier integration: 0 triggers, 1 action, 0 searches. Zapier can ask MerrenIO to send one of your published surveys to a phone number each time something happens in another app. MerrenIO never starts the automation itself, so the starting event comes from elsewhere.
Verified Trustpilot reviews · AI, automation & growth agency
What the MerrenIO Zapier integration does for you
The MerrenIO Zapier integration lets another app decide when a survey goes out. MerrenIO runs customer experience surveys over WhatsApp. When an event happens elsewhere, Zapier hands MerrenIO a phone number and the survey to use, and MerrenIO sends it. One action, one clear job.
Three results people build on the single Send Survey action. A survey for every new contact: a row with a phone number lands in a spreadsheet, and that person receives the survey you picked. A team that knows it went out: a step after the survey posts a message in your team chat, so everyone can see that it went out and to whom. A different survey for a different moment: you build one Zap per event, each pointing at its own published survey, so the questions match what just happened.
Now the limits. Zapier offers no trigger for MerrenIO, so nothing that happens inside MerrenIO can start a Zap. There is no search either, so a Zap cannot look up a survey or a contact in MerrenIO. And Zapier does not build surveys: the action sends a survey that is already published in MerrenIO, so writing the questions stays on the MerrenIO side.
Still comparing tools? See our Zapier alternatives page or our n8n vs Zapier comparison.
Zapier words in one minute
Eight words come back all over this page. Here is what each means, in plain terms.
- Zap
- The automation you build on Zapier: one event that starts it, then one or more steps that run every time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. MerrenIO has none, so yours comes from another app.
- Action
- What the Zap does once it has started: the step that writes, sends or changes something for you. Here, Send Survey is the only one.
- Task
- The unit Zapier bills. One task is one action the Zap completed successfully, and the number on 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 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.
- Search step
- A step that looks up something already stored in an app so later steps can use it. MerrenIO offers none on Zapier.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter, a search or a second action makes it one, and it then needs a paid plan.
What a MerrenIO Zap really costs
MerrenIO is not a premium app, so it works on the free plan. Zapier bills in tasks, and only the survey step counts.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps
- Billed per run1 task per successful Send Survey
- Trigger checksFree, never counted
The trigger in the other app never costs a task, however often Zapier checks it. Each Send Survey that goes through is one task, and a failed run is not counted. Add a team chat message after it and every run costs two tasks. The free plan gives 100 tasks a month and unlimited Zaps, each capped at two steps, so that extra message needs a paid plan. The interval grid below concerns the starting app only, and only if its trigger is a polling one.
Connect MerrenIO to Zapier in three steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your MerrenIO account linked once, then reused by every MerrenIO step.
- 02
Pick MerrenIO
Type MerrenIO in the search box of the dialog, select it, then click Add connection. A new tab opens on the MerrenIO side; keep it open until you are done.
- 03
Sign in and allow access
Log in to MerrenIO in that tab and grant Zapier access. You need a MerrenIO account, plus read or write access on anything you do not own yourself and want the Zap to touch.
Your first MerrenIO Zap, step by step
GoalSend a survey to each new person in a spreadsheet, then tell your team in chat that it went out.
- 01
Create the Zap and set the trigger
Start a new Zap and pick your spreadsheet app with its new-row event. The Zap has to begin there, because MerrenIO has no trigger of its own.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent rows from the connected account, so you map the phone number on real data rather than a guess.
- 03
Add Send Survey
Add MerrenIO, choose Send Survey, pick the published survey, and map the Phone Number field to the matching column of the row.
- 04
Add the chat message
Add a team chat step and include the phone number or name from the row in the message. This third step makes the Zap multi-step, so it needs a paid plan.
- 05
Test, then publish
Test each step with a number you control and read what came back. When it looks right, click Publish to switch the Zap on.
The MerrenIO action
MerrenIO gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Send Survey
ActionIn Zapier“Send a published survey to phone number”
Sends one of your published MerrenIO surveys to the phone number your trigger brought in. You pick which survey in the step, and the number comes from the earlier app.
When a MerrenIO Zap breaks
Zapier lists no help article for MerrenIO, and no limit specific to the app has been recorded. What goes wrong comes from how Zaps behave in general.
Four general situations are worth knowing. They sit on the trigger side and in Zapier's own rules, so start there when a survey did not go out.
Earlier contacts are skipped
A Zap only reacts to what happens after you switch it on. People already in the sheet never get the survey; reaching them is a separate job.A Zap that triggers itself
As a general precaution, a Zap that writes into the very place its own trigger watches can set itself off again and again, and burn through your tasks.Bulk imports get held back
When the starting app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those items back.No duplicates from polling
On a polling trigger, Zapier remembers what it has already seen, so the same row does not start the Zap twice.
Need help automating MerrenIO with Zapier?
A person reads every message.
