Resources · Zapier integration

MyMobileAPI Zapier integrationAutomate MyMobileAPI with Zapier.

The MyMobileAPI Zapier integration gives you 2 actions, 0 triggers and 0 searches. Another app starts the Zap, and MyMobileAPI sends a text message to one phone number, either right away or at a date and time you set, up to three months ahead.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MyMobileAPI Zapier integration does for you

MyMobileAPI is a business messaging platform built around bulk SMS. On Zapier, it becomes the last step of a Zap (the automation you build on Zapier): something happens in another app, and MyMobileAPI texts one phone number with a message you wrote, now or later.

Three results you can set up with its two actions. A confirmation text: Send SMS replies to each new form response with a message to the number the person gave. A reminder on a set date: Schedule an SMS queues a text for a date and time taken from the triggering record, up to three months ahead. An internal alert: Send SMS texts your own phone each time a row lands in a shared spreadsheet.

What Zapier does not do here. MyMobileAPI has no trigger, so a reply, a delivery receipt or any other event on the MyMobileAPI side cannot start a Zap. There is no search either, so a Zap cannot look up a contact or a past message. Each action sends to one number per run: a list of recipients means one run per recipient, coming from the trigger. And the text itself is capped at 490 characters, with every 140 characters credited by MyMobileAPI as a single message.

Still comparing tools? See our Zapier review.

Vocabulary

Zapier words, in plain English

Seven terms come back on this page. Here they are, before you meet them in the editor.

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. MyMobileAPI has none, so another app starts things.
Action
What the Zap does once started: the step that writes, sends or moves something. Here, sending or scheduling a text.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan is a count of those.
Polling vs instant
A polling trigger is checked by Zapier at a fixed interval. An instant trigger is reported by the app the moment the event happens.
Filter
A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
Connection
Your MyMobileAPI account linked to Zapier once, then reused by every step that sends through MyMobileAPI.
Cost

What a MyMobileAPI Zap really costs

Two meters run side by side here. Zapier counts tasks, and MyMobileAPI credits messages. They are not the same thing.

  • Free plan100 tasks a month, unlimited Zaps, two steps each
  • MyMobileAPI premium?No, it works on the free plan
  • Message length490 characters at most
  • MyMobileAPI creditsEvery 140 characters count as one message

On Zapier, the trigger never costs a task, and checking for new data costs nothing either. Each completed action counts as a task; one that fails is not counted. MyMobileAPI is not a premium app, so it runs on the free plan: 100 tasks a month, unlimited Zaps, two steps each. A trigger plus Send SMS fits; a filter or a second action makes it a multi-step Zap, which needs a paid plan. The interval grid below applies to the trigger of the other app when it is a polling one.

Connect

Connect MyMobileAPI to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page and click + Add connection. You need a MyMobileAPI account, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Choose MyMobileAPI

    Search for MyMobileAPI in the dialog, pick it, then click Add connection. A new browser tab then opens on the MyMobileAPI side, where the sign-in happens.

  3. 03

    Sign in and grant access

    Sign in to MyMobileAPI in that tab, then grant Zapier access to the account. Both actions, Send SMS and Schedule an SMS, then use this one connection in every Zap.

First Zap

Your first MyMobileAPI Zap: a text after each form response

GoalEach new form response gets a confirmation SMS, only when the response matches the condition you set.

  1. 01

    Build: start from the form

    Create a Zap and choose your form app with its new-response event as the trigger. MyMobileAPI cannot start a Zap, so the form comes first.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent responses of the connected account, so you map the phone number from a real one.

  3. 03

    Add a filter (paid plan)

    From the plus icon, add a Filter step and set the field, the rule and the value. A filter makes this a multi-step Zap, so it needs a paid plan.

  4. 04

    Add Send SMS

    Pick MyMobileAPI, then Send SMS. Map the number to Destination, in international format, and write the Message, keeping it under 490 characters.

  5. 05

    Test, then publish

    Run the action test once and read what came back before going further. Then click Publish to switch the Zap on. Earlier responses are not picked up.

Actions

The two MyMobileAPI actions

MyMobileAPI gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Schedule an SMS

Action

In Zapier“Schedule a single SMS message to be sent to the specified number on the specified date and time.”

Queues a single text for a set date and time instead of sending it now. Besides the number and the message, it asks for when, in UTC, at most three months ahead.

When to use it
a reminder tied to a date that the trigger already carries.
Watch out
the field expects UTC, so check the date and time you map against that during the test.
2

Send SMS

Action

In Zapier“Send a single SMS message to the specified number.”

Texts one phone number with the message you wrote, the moment the action runs in your Zap. You give it a destination number and the text, with fields from earlier steps if you like.

When to use it
a confirmation or an alert that should go out right after the trigger.
Watch out
the message is capped at 490 characters, and MyMobileAPI credits every 140 characters as one message.
When it breaks

When a MyMobileAPI Zap breaks

Zapier attaches no help article to MyMobileAPI and documents no limit specific to it. The cases below come from how Zapier itself works.

  • Past records get no text

    A Zap only reacts to what happens after you switch it on. Records already in the trigger app get no SMS, and catching up on them 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 the task count fast.

  • A sudden huge batch

    When the trigger app suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.

  • The same record twice

    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

Need help automating MyMobileAPI with Zapier?

A person reads every message.

FAQ

MyMobileAPI Zapier integration: FAQ

01Is the MyMobileAPI Zapier integration free?
Yes. The integration works from the free plan of Zapier, because MyMobileAPI is not a premium app. That plan gives you 100 tasks a month and an unlimited number of Zaps, each made of two steps: one trigger and one action. A form response followed by Send SMS fits exactly. Add a filter, or send a second message in the same Zap, and it becomes a multi-step Zap, which requires a paid plan.
02How many tasks does a MyMobileAPI Zap use?
Zapier bills each action that completes successfully as a task, so a Zap that sends one text per trigger event uses one task per event when it goes through. The trigger in the other app costs nothing, and so does Zapier checking for new data, however often it looks. An action that fails is not counted. A Zap with Send SMS and then Schedule an SMS counts each successful action on its own.
03Does MyMobileAPI work in real time with Zapier?
MyMobileAPI has no trigger, so the timing depends on the app that starts the Zap. If that app has an instant trigger, it tells Zapier itself and the plan interval does not apply. If its trigger is a polling one, Zapier checks at a fixed interval: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. Send SMS then goes out when the action runs, and Schedule an SMS waits for the date you set.
04What do you need to connect MyMobileAPI to Zapier?
A MyMobileAPI account, plus read or write access on anything you do not own yourself and want the Zap to touch. Then, on the Apps page of Zapier, click + Add connection, search for MyMobileAPI, click Add connection, sign in to MyMobileAPI in the tab that opens and grant Zapier access. Both actions reuse that single connection in every Zap you build afterwards. The Destination field then expects numbers in international dialling format, so check how your source app stores them.
05Why does a long MyMobileAPI message cost more than expected?
Because MyMobileAPI credits every 140 characters of a message as a single message, and the field accepts up to 490 characters. A long text can therefore count as several messages on your MyMobileAPI account, while Zapier still sees one action. Keep the message short when the cost matters, and check the length of any field you map into it, since mapped values add characters you did not type. Run the action test and read what came back before you publish.
06What if the MyMobileAPI operation you need is not there?
Then Zapier cannot do it today. This integration has two actions, Send SMS and Schedule an SMS, and nothing else: no trigger for replies or delivery events, no search, no way to cancel a scheduled text. The MyMobileAPI page on zapier.com shows the current list of operations, so check it before you plan a Zap around anything else. Within a Zap, the two actions can still follow any trigger from another app that carries a phone number.
07Zapier, Make or n8n for MyMobileAPI?
Judge on criteria, not a ranking. Coverage: on Zapier, MyMobileAPI offers two sending actions, Send SMS and Schedule an SMS, and no trigger; for Make or n8n, look at each tool's own app list. Billing: Zapier counts each successful action as a task, and MyMobileAPI credits every 140 characters of a text as one message, so two meters apply. Timing: the delay before a text goes out depends on the trigger of the app in front, instant or polling. Plan: on Zapier, a filter before the text already needs a paid plan.
Same platform

Other docs you might need on this stack.

Browse all integrations