Mtalkz Zapier integrationAutomate Mtalkz with Zapier.
The Mtalkz Zapier integration gives you 0 triggers, 1 action and 0 searches. That single action, Send Message (SMS), texts a phone number when an event in another app starts the Zap. Mtalkz can receive the work, but it cannot start a Zap on its own.
Verified Trustpilot reviews · AI, automation & growth agency
What the Mtalkz Zapier integration does for you
The integration turns events in your other apps into text messages. Mtalkz is a cloud platform for SMS campaigns, and on Zapier it exposes one action: Send Message (SMS). Another app supplies the event and the phone number, Mtalkz sends the text, and nobody has to type it by hand.
Three results come out of that one action. A confirmation: someone fills in a form, and the number they gave gets a text that says it arrived. A heads-up for your own team: a new row in a shared sheet triggers an SMS to the person who has to deal with it. A follow-up: a contact moves to a new stage in your CRM, and the action sends the message you prepared for that stage. All three end on action:send_sms; only the first card changes. Whatever starts it, each send needs the same three things: a Sender ID, the destination number and the message itself, or a template your telecom provider approved.
What Zapier does not do here matters as much. Mtalkz has no trigger on Zapier, so nothing that happens inside Mtalkz can start a Zap. It has no searches either, so a later step cannot look up a Mtalkz contact or message. Every Zap reads from another app and ends by sending.
Still choosing a tool? Read our Zapier review, or open our Make vs Zapier comparison.
Zapier words, in plain English
These eight terms come back on the page. Each one is explained once, here.
- 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. With Mtalkz, the trigger always comes from another app.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you. Here, sending an SMS.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Each SMS sent through the Zap is one task.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only what is new.
- Instant trigger
- A trigger the app reports itself: it calls Zapier when the event happens, so nothing waits for the next check.
- 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 filter or a second action makes one, and it then needs a paid plan.
What it really costs
Mtalkz is not one of the apps Zapier keeps for paid plans, so you can use it from the free plan.
- TriggerFree, never counted
- Each SMS sent1 task
- Free plan100 tasks a month, two-step Zaps
- Filter or second actionPaid plan
The trigger from your other app never costs a task. Each Send Message (SMS) that succeeds counts as one task, and an action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger, one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. The grid below is how often Zapier checks a polling trigger; it applies to the trigger of the app that starts your Zap, if that trigger is a polling one.
Connect Mtalkz to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your Mtalkz account linked to Zapier once, then reused by every step that sends through it.
- 02
Pick Mtalkz
Type Mtalkz in the search box of the dialog that opens, select the app in the results, then click Add connection. A new tab opens where you sign in to your Mtalkz account.
- 03
Sign in and grant access
Sign in to Mtalkz in that tab and allow Zapier to access 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: text people who fill in your form
GoalSend an SMS confirmation through Mtalkz to each new form respondent who left a phone number.
- 01
Create the Zap and set the trigger
Start a new Zap and pick your form tool with its new-submission event. Connect the account and choose the form. Then test the trigger and read the sample it brings back.
- 02
Add a filter
Click the plus icon, add Filter, then set the field to check, the rule and the value, here the phone field. A filter makes this a multi-step Zap, so it needs a paid plan.
- 03
Add the Mtalkz action
Add Mtalkz with Send Message (SMS). Fill in the Sender ID, map the phone field from the form into the destination number, and write the message or paste your approved template.
- 04
Test the SMS step
Run the test of the Mtalkz step and read what came back before going further. If something is off, fix the mapping and test the step again.
- 05
Publish
Click Publish to switch the Zap on. From then on, each new response that passes the filter gets its text message, one task each.
The Mtalkz action
Mtalkz gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Send Message (SMS)
ActionIn Zapier“Sending SMS to desired contact number”
Sends a text from your Mtalkz account to the phone number you map from an earlier step, with the wording you write or a template.
{#var#}, and the template itself must be pre-approved by your telecom provider.When the Zap breaks
Zapier attaches no help article of its own to Mtalkz, so the cases below are the general Zapier limits that touch a Zap ending on this action.
When a Zap stops behaving, start from these cases. For a step-by-step method, see our Zapier troubleshooting guide.
Past events get no SMS
A Zap only reacts to what happens after it is switched on. Form responses or rows that existed before you published are not picked up, so they get no text.A big batch gets held back
When the trigger app suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold the trigger back.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 burn through your task count.
Need help automating Mtalkz with Zapier?
A person reads every message.
