Resources · Zapier integration

MOBIT Zapier integrationAutomate MOBIT with Zapier.

The MOBIT Zapier integration gives you 1 trigger, 1 action and 0 searches. The trigger is instant and fires when a contact reaches a campaign goal; the action creates or updates a contact. It all runs on the free plan, as long as the goal is set up to show in Zapier.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MOBIT Zapier integration does for you

It connects MOBIT, a mobile marketing platform for SMS and MMS campaigns, to Zapier, the tool that chains automations between apps. When a contact reaches a goal you set in a MOBIT campaign, other tools can react, and those tools can in turn create or update contacts in MOBIT.

A record of every goal reached. Goal Achieved starts the Zap the moment a contact hits the goal you picked, and an action in your spreadsheet adds a row. Your campaign results land somewhere you can sort and share.

A MOBIT contact list fed by your other tools. A person appears in another app, and Create or Update Contact writes them into MOBIT, matched by mobile number, email or contact ID. No copy and paste between tools.

Fresh details on people already in MOBIT. The same action, with Update Existing Contacts set to yes, refreshes a contact that already exists instead of failing on it.

What Zapier does not do here: there is one trigger and one action, and nothing else. No search step can look up a contact before acting, and the only event that starts a Zap is a goal reached in a campaign that is turned on. Before you settle on a tool for this, see our n8n vs Zapier comparison and our Zapier review.

Vocabulary

Zapier words in one minute

Eight words come back on every Zapier screen. Here they are in plain terms, before you build your first automation.

Zap
The automation you build: 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 that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something in an app on your behalf.
Task
The unit Zapier bills: one action that your Zap completes successfully. The number on your plan counts these.
Instant trigger
A trigger the app reports itself: it calls Zapier the moment the event happens, so nothing waits for a check.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval and keeping only unseen ones.
Filter
A step that lets the Zap continue 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 needs a paid plan.
Cost

What a MOBIT Zap really costs

MOBIT is not a premium app on Zapier, so it is available on the free plan. You spend tasks, and only actions spend them.

  • Premium appNo, works on the free plan
  • Tasks on the free plan100 per month
  • Steps per Zap on the free plan2 (one trigger, one action)
  • Cost of a trigger0 tasks

Goal Achieved never costs a task. Each Create or Update Contact that goes through counts as one, and a failed run is not counted. A Zap with two actions spends two tasks every time a goal is reached. The free plan gives 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 interval grid below is for polling triggers: it does not apply to the instant trigger of this app.

Connect

Connect MOBIT to Zapier

  1. 01

    Open your connections

    In Zapier, open the Apps page of your account and click + Add connection. A connection is your MOBIT account linked once, then reused by every Zap step that works with MOBIT.

  2. 02

    Find MOBIT

    Search MOBIT by name in the dialog, select it and click Add connection. 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.

  3. 03

    Sign in and allow access

    MOBIT opens in a new tab. Sign in, then grant Zapier access to the account. The connection is then offered in the account menu of every step that uses MOBIT, in this Zap and in the next ones.

First Zap

Your first Zap: log selected goals in a spreadsheet

GoalEach time a contact reaches a MOBIT campaign goal, add a row to your spreadsheet, but only when the contact meets a condition you choose.

  1. 01

    Set the trigger

    Create a Zap, pick MOBIT and the Goal Achieved event, then your connection. In the Goal field, choose the goal to watch. It is an instant trigger, so there is no interval to set.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the connected account, so you map the next steps on real data. Check at test which details the trigger returns.

  3. 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. A filter makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the spreadsheet row

    Add your spreadsheet app with its new row action, and map the contact details into the columns you want. Test the step and read what came back before going further.

  5. 05

    Publish

    Click Publish to switch the Zap on. From then on, every goal reached that passes the filter adds one row, and each row written counts as one task.

Triggers

MOBIT triggers

1 event starts a Zap when something happens in MOBIT, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

Goal Achieved

Instant trigger

In Zapier“Triggers when a contact achieves a designated goal in a campaign.”

Starts your Zap when a contact reaches the goal you picked in a MOBIT campaign, and passes that contact on to the steps that follow. One Zap watches one goal, chosen in the Goal field.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a campaign result, a goal reached, should be recorded or acted on in another tool without anyone watching the MOBIT dashboard.
Watch out
the Goal list only offers goals whose campaign is turned on and whose Show in Zapier box is ticked; if the list is empty, check both settings in MOBIT.
Actions

MOBIT actions

MOBIT gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create or Update Contact

Action

In Zapier“Creates or updates a contact given their mobile number, email or contact ID.”

Writes a contact into MOBIT from data an earlier step brought in, and can refresh one that is already there. Unique Identifier tells MOBIT how to recognise the person: mobile number, email or contact ID.

When to use it
people show up in another tool and must exist in MOBIT for your SMS campaigns.
Watch out
with Update Existing Contacts set to no, the Zap fails when the contact already exists in MOBIT.
When it breaks

When a MOBIT Zap breaks

Zapier attaches no help article to MOBIT, and no rate limit is published for it. What breaks is what breaks on any Zap, plus the two required settings of the action.

Four cases cover most of the surprises on this app. If a Zap still misbehaves after them, see our Zapier troubleshooting guide.

  • Goals reached before publishing are lost

    A Zap only reacts to what happens after it is switched on. Goals reached earlier are never picked up; moving that backlog is a separate job.

  • The contact already exists

    Create or Update Contact fails on an existing contact when Update Existing Contacts is set to no. Set it to yes if updates are expected.

  • The Zap keeps restarting itself

    A Zap that writes into the very place its own trigger watches can set itself off again and again, and burns through the task count fast.

  • A big batch gets held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back.
Need help

Need help automating MOBIT with Zapier?

A person reads every message.

FAQ

MOBIT Zapier integration: FAQ

01Is the MOBIT Zapier integration free?
Yes, it runs on the free plan, since Zapier does not class MOBIT as a premium app. That plan gives you 100 tasks a month and as many Zaps as you want, each one capped at two steps: a trigger and an action. Goal Achieved followed by a single row in a spreadsheet fits. Add a filter to keep only some contacts, or a second action, and the Zap becomes multi-step, which takes a paid plan.
02How many tasks does a MOBIT Zap use?
One task per action that succeeds, and none for the trigger. A Zap that logs each goal reached in one spreadsheet costs one task per goal. If the same Zap also writes to a second tool, that is two tasks per goal. A run where the action fails is not counted. Zapier does not bill for waiting on the trigger either, so a quiet campaign costs nothing. On the free plan, the count runs against 100 tasks a month.
03Does MOBIT trigger Zaps in real time?
Yes. Goal Achieved is an instant trigger: MOBIT tells Zapier when a contact reaches the goal, and the Zap starts right away, on the free plan as on the paid ones. The plan interval grid only governs polling triggers, which Zapier checks on a timer, and MOBIT has none. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is a quick way to confirm it.
04What do you need to connect a MOBIT account?
An account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch. You connect once, from the Apps page of your Zapier account with + Add connection, then sign in to MOBIT in the tab that opens and grant access. For the trigger, you also need at least one campaign turned on with a goal marked Show in Zapier, or the Goal list stays empty.
05Why does Create or Update Contact fail on a known contact?
Because of Update Existing Contacts. This setting is required, and when it is set to no, the Zap fails if the contact already exists in MOBIT. Set it to yes when the people coming in may already be in your account. The other required setting, Unique Identifier, decides how MOBIT recognises an existing person: by mobile number, by email or by contact ID. Pick the one your incoming data actually carries, and check it at test.
06What if the MOBIT operation you want is not there?
Look at the MOBIT page on Zapier: it shows the current list of triggers and actions, and the editor offers nothing beyond it. Today that is one trigger, Goal Achieved, and one action, Create or Update Contact, with no search step. If the event or the action you have in mind is missing from that page, no Zap setting will add it. The way forward is to shape the workflow around these two, or to look at another automation tool.
07Zapier, Make or n8n for MOBIT?
Choose on criteria rather than on a ranking. The first one is simple: does the other tool connect to MOBIT at all? Check that before comparing anything. On Zapier, the only trigger is instant, so plan intervals play no part for this app, and a two-step Zap runs on the free plan. After that, count the steps your workflow needs per run, estimate the runs per month, and decide who will keep the automation working over time.
Same platform

Other docs you might need on this stack.

Browse all integrations