- Home
- Resources
- Integrations
- MPower CS
MPower CS Zapier integrationAutomate MPower CS with Zapier.
The MPower CS Zapier integration gives you 2 triggers, 2 actions and 0 searches. Messages going in and out of MPower CS can start a Zap at once, and any other app can send a WhatsApp message or an approved template through your MPower CS channel.
Verified Trustpilot reviews · AI, automation & growth agency
What the MPower CS Zapier integration does for you
MPower CS is a conversational marketing tool that turns your social and messaging channels into a place to sell. The Zapier integration works both ways: what happens in your conversations can start a Zap, and a Zap can push a WhatsApp message out through MPower CS, from a recipient number and the text you set.
Three results you can build from the four operations. A welcome message: a new signup in your form tool becomes an approved template sent on WhatsApp with Send WhatsApp Template Message, so the first contact goes out without anyone typing it. A conversation log: each message a client sends, caught by Receive New Message, lands as a row in a spreadsheet you can sort and share. A sent-items trail: Send New Message fires when MPower CS sends a message to a client, so your other tools learn about every outgoing reply too.
What Zapier does not do here matters just as much. There is no search: a Zap cannot look up a client, a conversation or a past message in MPower CS. There is no action to create or edit a contact either; the only actions send messages. And both WhatsApp actions need a WhatsApp channel already set up in your MPower CS account, since each one asks you to pick it.
Both triggers are instant, so the plan interval never slows them down. If you are still comparing platforms, see our Make vs Zapier comparison.
Zapier words in one minute
Seven terms carry the rest of this page.
- 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, here a message received or sent.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, like a WhatsApp message.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked 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.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then needs a paid plan.
What it really costs
MPower CS is not a premium app, so you can connect it from the free plan.
- TriggerFree, never counted
- Each WhatsApp message sent1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
The trigger never costs a task, whether a message comes in or goes out. Each action that succeeds counts once: one WhatsApp message sent is one task. An action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, each capped at two steps, one trigger and one action. Add a filter, say to keep only certain messages, or a second action, and the Zap becomes multi-step and needs a paid plan. The grid below is the polling interval by plan; it does not apply to the two instant triggers of MPower CS.
Connect your MPower CS account
- 01
Open the Apps page
In Zapier, go to Apps and click + Add connection. A connection is your MPower CS account linked once, then reused by every Zap and every step that needs it.
- 02
Pick MPower CS
Search MPower CS by name in the dialog, select it, then click Add connection. A new browser tab then opens so you can sign in to your account on the MPower CS side.
- 03
Sign in and grant access
Log in to MPower CS in that tab and allow Zapier into 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.
Your first Zap: turn client messages into support tickets
GoalEach message a client sends in MPower CS gets checked, then opens a ticket in your help desk.
- 01
Build: set the trigger
Create a Zap, pick MPower CS as the app that starts it and
Receive New Messageas the event, then select your MPower CS connection. - 02
Test the trigger
Run the test. Zapier brings back the three most recent items of the connected account, so you map the ticket on a real client message.
- 03
Add a filter (paid plan)
Click the plus icon and add Filter, then fill the three boxes: field, rule, value. A filter makes the Zap multi-step, so it needs a paid plan.
- 04
Add the help desk action
Pick your help desk and its new-ticket action, then map the message details into the ticket fields. Run the test and read what came back.
- 05
Publish
Click Publish to switch the Zap on. Only messages received after that moment open a ticket; earlier conversations are not picked up.
MPower CS triggers
2 events start a Zap when something happens in MPower CS, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
Receive New Message
Instant triggerIn Zapier“Triggers when received a new message from client on MPower CS.”
Starts your Zap whenever a client sends a new message that lands in MPower CS. The incoming message then feeds the steps that follow, so a conversation can reach your spreadsheet, your support queue or your team chat.
Send New Message
Instant triggerIn Zapier“Triggers when sending a new message from MPower CS to client.”
Fires when MPower CS sends a new message to a client, so the outgoing side of your conversations becomes visible to other apps too. Pair it with the inbound trigger to keep a full record of both directions.
MPower CS actions
MPower CS gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Send WhatsApp Message
ActionIn Zapier“Send a WhatsApp message to user.”
Sends a free-text WhatsApp message to one person through your MPower CS channel. You pick the WhatsApp Channel, give the Recipient number and write the Content, which can mix fixed text with values from earlier steps.
E164 format, with the plus sign and country code.Send WhatsApp Template Message
ActionIn Zapier“Send an approved WhatsApp template message to user.”
Sends an approved WhatsApp template rather than free text. Same three required fields as the plain message: WhatsApp Channel, Recipient and Content, where Content has to match the template message.
When it breaks
Zapier links no help article and no specific limit to MPower CS. The cases below come from the required fields of its actions and from Zapier's general limits.
These are the situations to keep in mind when a WhatsApp Zap does not behave as planned. For a method to trace a failing step, see our Zapier troubleshooting guide.
Recipient number in the wrong format
Both WhatsApp actions ask for the Recipient in international format, with a plus sign and the country code. A local number without them is the first thing to check.Content that does not match the template
Send WhatsApp Template Message wants Content that matches the approved template. When a send does not go through, compare the field with the approved wording first.No WhatsApp channel to pick
Both actions require a WhatsApp Channel. Without one set up in MPower CS, the field has nothing to offer and the step cannot run.Messages from before the Zap
A Zap only reacts to what happens after it is switched on. Conversations that came in earlier are not picked up; moving them is a separate job.A Zap that sets itself off
As a general precaution, a Zap that writes into the place its own trigger watches can start itself again and again and use up tasks fast.A sudden batch of messages
If a trigger returns a huge batch at once, after a bulk import for example, Zapier's flood protection can hold it back.
Need help automating MPower CS with Zapier?
A person reads every message.



