MessengerPeople.dev Zapier integrationAutomate MessengerPeople.dev with Zapier.
The MessengerPeople.dev Zapier integration gives you 1 trigger, 2 actions and 0 searches. One instant trigger catches every incoming message, and two actions send either a typed reply or a notification built from a template your account already had approved.
Verified Trustpilot reviews · AI, automation & growth agency
What the MessengerPeople.dev Zapier integration does
MessengerPeople.dev is a messaging service that sends and receives messages over channels such as WhatsApp Business, Telegram and Facebook Messenger. Plugged into Zapier, it lets a Zap (the automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens) react to a message that comes in, or push one out without anybody typing it.
A reply that leaves on its own. Pair Incoming Message Webhook with Outgoing Message, then swap sender and recipient as the app itself suggests: whoever writes in gets your text back, and nobody has to watch the inbox for it.
A confirmation the buyer actually sees. Send Notification pushes a template you already had approved, a purchase confirmation for instance, to one recipient. The Zap can start from another tool, so the message goes out when that tool records the event.
A copy of each message somewhere else. The same trigger can feed a new row in your spreadsheet, which keeps a trace of incoming messages outside the messaging inbox.
Know the limits too. A new incoming message is the only event that can start a Zap. With no search step, a Zap never pulls up an earlier conversation. And Send Notification only picks a template that is already approved, so templates are prepared in your account before you build. For more, see our Zapier review.
Zapier words in one minute
Eight terms come back on every line of this page. Here they are in plain words.
- 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 in an app that starts the Zap. Here it is a new message reaching your MessengerPeople.dev account.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, such as a reply.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan counts tasks, not Zaps or triggers.
- Instant vs polling trigger
- An instant trigger is reported by the app the moment the event happens; a polling trigger is checked by Zapier on a timer. This app's trigger is instant.
- 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 or a filter makes one, and it then needs a paid plan.
- Connection
- Your MessengerPeople.dev account linked to Zapier once, then reused by every step that uses the app.
What it really costs you
Zapier bills in tasks. Listening for new messages is free: the trigger itself never costs a task, however many messages arrive.
- Trigger0 tasks
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo, works on the free plan
Each Outgoing Message or Send Notification that goes through counts as one task, and a send that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps. Add a filter or a second action and you have a multi-step Zap, which needs a paid plan. MessengerPeople.dev is not a premium app, so it works from the free plan. The grid below is the polling interval by plan; it does not apply to this app's instant trigger.
Connect your MessengerPeople.dev account
- 01
Open Apps and add a connection
In your Zapier account, open the Apps page and click + Add connection. Type MessengerPeople.dev in the search box of the dialog, pick it, then click Add connection.
- 02
Sign in and grant access
A new tab opens on MessengerPeople.dev. Sign in there and grant Zapier access to the account. 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.
- 03
Reuse it everywhere
The account is now linked to Zapier once. Every step that uses MessengerPeople.dev relies on that same connection: Incoming Message Webhook, Outgoing Message and Send Notification alike.
Your first Zap: an automatic reply behind a filter
GoalAnswer incoming messages with a fixed text, but only those that meet a condition you choose.
- 01
Build the trigger
Start a new Zap, choose MessengerPeople.dev as the app that starts it and Incoming Message Webhook as the event, then select your connection.
- 02
Test it on a real item
Run the trigger test once. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real message, not a guess.
- 03
Add the filter
From the plus icon, add Filter and fill its three boxes: the field to look at, the rule, the value to compare with. Pick a text rule for a text field. The filter makes this a multi-step Zap, so a paid plan.
- 04
Add the reply
Add Outgoing Message. Take the sender and recipient from the trigger step and switch them, so the answer goes back to the person who wrote, then type your words in Text.
- 05
Test and publish
Test the action once and read what came back, then publish the Zap to switch it on. Each reply sent counts as one task. If you want a guided start, see our Zapier training.
The trigger
1 event starts a Zap when something happens in MessengerPeople.dev, and one of them is instant: the app calls Zapier straight away, whatever your plan.
Incoming Message Webhook
Instant triggerIn Zapier“Triggers when a new message is received.”
Starts your Zap each time a new message is received on your MessengerPeople.dev account, whichever of your channels it came through.
The actions
MessengerPeople.dev gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Outgoing Message
ActionIn Zapier“Send a response / outgoing message to a user. If you want to reply to an incoming message received with the "Incoming Message Webhook" trigger, just use sender and recipient from the previous step and switch them.”
Sends a free text from one of your channels to a single recipient, for instance to answer someone who just wrote in.
Send Notification
ActionIn Zapier“Sends a notification to the user (e.g. a purchase confirmation)”
Pushes a message built from a template your account already had approved, such as a purchase confirmation, to one recipient.
When it breaks
Zapier links no help article to MessengerPeople.dev. What follows is how every Zap behaves, plus the conditions the actions spell out themselves.
Four cases are worth checking before you blame the app. If a Zap still misbehaves, see our Zapier troubleshooting guide.
Nothing from before the Zap
A Zap only reacts to messages received after you switch it on. Older conversations are never 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 again, and burn through your task count. Check where each action writes.A sudden flood held back
After a bulk import or a migration, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection.Template and language mismatch
Send Notification needs a template approved in the language you chose, in the account that owns the sending channel. If either point is off, the action does not work.
Need help automating MessengerPeople.dev with Zapier?
A person reads every message.
