Resources · Zapier integration

OneLocal LocalMessages Zapier integrationAutomate OneLocal LocalMessages with Zapier.

The OneLocal LocalMessages Zapier integration gives you 8 triggers, 4 actions and 0 searches. Six triggers are instant: messages, calls, opened or closed conversations and tags. Two poll for opt-ins and opt-outs. The actions send a text, assign a conversation and manage its tags.

See the 12 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the OneLocal LocalMessages Zapier integration does

It plugs the business texting inbox of OneLocal LocalMessages into Zapier. Messages, phone calls and conversation changes can start automations in your other tools, and those tools can send texts, assign conversations to employees and tag them in LocalMessages.

Three results stand out. No customer text left unanswered: Conversation Opened or New Message starts a Zap, and Assign Conversation hands the thread to the right employee. Calls and texts logged where your team works: Incoming Phone Call and Conversation Closed push each event into a CRM or a shared sheet. Tags that drive the rest: Conversation Tag Added starts a follow-up elsewhere, while Add Conversation Tag and Remove Conversation Tag keep labels in step with your other tools.

The detail that matters most: six of the eight triggers are instant, so they start the Zap straight away even on the free plan. The two consent triggers, Phone Number Opt-In and Phone Number Opt-Out, are polling triggers, and they wait for Zapier's next check, every 15 minutes on Free.

What the integration does not do: there is no search step, so no Zap can look up a conversation on its own; every conversation action needs its Conversation ID from an earlier step. There is no action to close a conversation or to change a customer's consent either.

For a broader view, compare Make vs Zapier and n8n vs Zapier.

Vocabulary

Zapier vocabulary, in plain words

Eight words come back throughout this page. Here they are, once.

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, such as a new text or a missed call. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, like sending a text.
Task
The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. The two opt-in and opt-out triggers poll.
Instant trigger
A trigger the app reports itself, the moment the event happens, with no wait for a check. Six LocalMessages triggers are instant.
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, a filter or a search makes it one, and it needs a paid plan.
Cost

What a LocalMessages Zap really costs

OneLocal LocalMessages is not a premium app, so it works on the free plan. The trigger never costs a task: a message received or a call answered is free to watch.

  • Any of the 8 triggers0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, Zaps of 2 steps
  • Instant triggers6 of 8, no plan interval

Each action that succeeds counts as one task, and a failed one is not counted. A Zap that assigns and then tags a conversation uses two tasks per run. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps, one trigger and one action. The interval grid only touches the two opt-in and opt-out triggers; the six instant ones fire straight away on every plan, Free included.

Connect

Connect LocalMessages to Zapier in 3 steps

  1. 01

    Open your connections

    Go to the Apps page of your Zapier account and click + Add connection. A connection is your LocalMessages account linked to Zapier once, then reused by every step that works with it.

  2. 02

    Pick LocalMessages

    Search OneLocal LocalMessages in the dialog, select it, then click Add connection. A tab opens on the OneLocal side: sign in with the account that runs your business texting.

  3. 03

    Grant access

    Let Zapier use that account. On top of the account itself, you need read or write rights on any conversation or inbox you do not own and still want a Zap to touch.

First Zap

Your first Zap: route every new conversation

GoalWhen a customer opens a conversation, assign it to the right employee and tag it so the team knows where it came from.

  1. 01

    Pick the trigger

    Choose OneLocal LocalMessages as the app that starts the Zap, then Conversation Opened as the event, and select your connection.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the connected account, so the next steps are mapped on a real conversation.

  3. 03

    Assign the conversation

    Add Assign Conversation, map the Conversation ID from the trigger and choose the employee. Nothing to type for the ID, you pick it from the test result.

  4. 04

    Tag it

    Add Add Conversation Tag with the same Conversation ID and the tag of your choice. This second action makes the Zap multi-step, so it needs a paid plan.

  5. 05

    Test, then publish

    Run each step once and read what came back before going further. When it all looks right, click Publish to switch the Zap on.

Triggers

The 8 LocalMessages triggers

8 events start a Zap when something happens in OneLocal LocalMessages, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Conversation Closed

Instant trigger

In Zapier“Triggers when a conversation is closed.”

Fires when a conversation is closed in LocalMessages. It marks the end of an exchange, which makes it the right moment to log the outcome somewhere else or to start what comes after the chat.

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 dental practice wants each closed conversation recorded in its patient CRM so nobody has to copy the thread by hand.
Watch out
conversations closed before the Zap was switched on are not picked up afterwards.
2

Conversation Opened

Instant trigger

In Zapier“Triggers when a conversation is opened.”

Starts the Zap when a conversation opens, the first sign that a customer is waiting for an answer. It is the trigger for routing: deciding who handles the thread before anyone has to read it.

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 car dealership wants every new conversation assigned to the salesperson on duty and flagged in the team chat.
Watch out
routing on this trigger needs Assign Conversation as the next step, and its employee must exist in your OneLocal account.
3

Conversation Tag Added

Instant trigger

In Zapier“Triggers when a conversation tag is added to the conversation.”

Reacts to a label: the Zap starts when a tag is added to a conversation. Tags then work as buttons your team presses inside LocalMessages to set something off in another tool.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an agent tags a thread as a quote request, and a Zap opens the matching deal in your CRM.
Watch out
a Zap that ends with Add Conversation Tag on the same conversations can set itself off again and again.
4

Conversation Tag Removed

Instant trigger

In Zapier“Triggers when a conversation tag is removed from the conversation.”

The mirror of the previous one: it starts the Zap when a tag is taken off a conversation. Removing a label becomes a signal too, for example that a case is no longer pending.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the team removes a waiting tag once the customer has replied, and the task in your project tool gets closed.
Watch out
pairing it with Remove Conversation Tag in the same Zap can create a loop on the conversations it touches.
5

Incoming Phone Call

Instant trigger

In Zapier“Triggers when an incoming call is answered or missed.”

Covers the phone side: it starts the Zap when an incoming call is answered or missed. That puts calls in the same automations as texts, without anyone writing them down.

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 plumbing company wants every missed call to create a callback task for the office manager.
Watch out
answered and missed calls both start the Zap; add a filter if only one of them matters, which makes the Zap multi-step.
6

New Message

Instant trigger

In Zapier“Triggers when a message is received and/or sent.”

The trigger Zapier puts forward for this app: a message received, sent, or both, depending on the message type you choose. It turns every text into an event your other tools can react to.

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 salon wants each incoming text copied into the customer's file in its booking tool.
Watch out
the message type is required. Set to sent messages, a Zap that ends with Send Message will start itself again.
7

Phone Number Opt-In

Polling trigger

In Zapier“Triggers when a phone number is opted in to receive messaging.”

Follows consent: it picks up phone numbers that have opted in to receive messages. A Zap can then add those customers to a list in another tool or note the consent in your CRM.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
the marketing lead wants each new opt-in reflected in her texting campaign list.
Watch out
unlike the six conversation and message triggers, this one is not instant, so its speed depends on your plan.
8

Phone Number Opt-Out

Polling trigger

In Zapier“Triggers when a phone number is opted out of receiving messages.”

The other side of consent: it picks up numbers that have opted out of receiving messages, so your other tools can stop contacting them too.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a customer opts out by text, and the same number should leave your email or CRM campaign lists.
Watch out
between two checks the other tools still hold the number, so a campaign sent in that gap can reach someone who just opted out.
Actions

The 4 LocalMessages actions

OneLocal LocalMessages gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Assign Conversation

Action

In Zapier“Assign a conversation to an employee.”

Hands a conversation to one of your employees, so the thread lands with the person meant to answer it.

When to use it
new conversations should reach whoever covers that location or that service, without a manager sorting them.
Watch out
both the Conversation ID and the employee are required, and the ID can only come from an earlier step, usually a LocalMessages trigger.
2

Add Conversation Tag

Action

In Zapier“Add a conversation tag to a conversation”

Puts a tag on a conversation from outside LocalMessages, so the label reflects what happened in another tool.

When to use it
a payment clears in your billing tool and the matching conversation should show it at a glance.
Watch out
the tag is chosen from those that exist in your account; create it in OneLocal first, then pick it in the step.
3

Remove Conversation Tag

Action

In Zapier“Remove a conversation tag from a conversation”

Takes a tag off a conversation, which lets another tool clear a label once the situation behind it is resolved.

When to use it
a waiting tag should disappear when the related order ships.
Watch out
it needs the Conversation ID and the tag to remove, and with no search available, that ID has to travel from a LocalMessages trigger earlier in the Zap.
4

Send Message

Action

In Zapier“Sends a new message to a chosen recipient.”

Sends a new text from LocalMessages to the recipient you choose, with content mapped from earlier steps. It is the action Zapier puts forward for this app.

When to use it
a booking is confirmed in another tool and the customer should get a text right after.
Watch out
paired with New Message set to sent messages, this action can start its own Zap again and burn through tasks.
When it breaks

When a LocalMessages Zap breaks

Zapier attaches no help article of its own to OneLocal LocalMessages, and no limit specific to the app is documented. These cases come from Zapier's general rules, applied to texts, calls and tags.

  • Past messages never come back

    A Zap only reacts to what happens after it is switched on. Texts, calls and conversations from before stay out; moving that history is a separate job.

  • The text that answers itself

    New Message set to sent messages, followed by Send Message, starts the Zap again with every text it sends. Check the message type before publishing.

  • Tags that chase each other

    Conversation Tag Added plus Add Conversation Tag on the same conversations makes a Zap that writes where it watches. It loops and eats tasks fast.

  • A burst gets held back

    When a trigger suddenly returns a huge batch, for instance after a migration of numbers or a bulk import, Zapier's flood protection can hold the runs back.

  • Consent changes arrive later

    The opt-in and opt-out triggers poll on your plan's interval, 15 minutes on Free. Anything relying on them lags behind the instant triggers.

  • An opt-out seen once

    On polling triggers Zapier remembers what it has seen, so one number does not start the Zap twice. That spares you double runs, but it never brings back a change made before the Zap was on.
Need help

Need help automating OneLocal LocalMessages with Zapier?

A person reads every message.

FAQ

OneLocal LocalMessages and Zapier: frequent questions

01Is the OneLocal LocalMessages Zapier integration free?
Yes. LocalMessages is not a premium app on Zapier, so it works on the free plan, which includes 100 tasks a month and unlimited Zaps. The constraint is the size of each Zap: on the free plan, one trigger and one action, nothing more. New Message followed by Assign Conversation fits. Assigning and then tagging in the same Zap, or adding a filter to keep only missed calls, makes the Zap multi-step and needs a paid plan. You also need your own LocalMessages account.
02How many tasks does a LocalMessages Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that assigns each new conversation costs one task per conversation. A Zap that assigns and tags costs two. Watching messages, calls or tags is free however many events occur; only completed actions are billed, and a failed action is not counted. With 100 tasks a month on the free plan, a busy texting inbox can use them up quickly, so count your monthly conversations before choosing a plan.
03Is LocalMessages on Zapier real time?
Mostly yes. Six of the eight triggers are instant: New Message, Incoming Phone Call, Conversation Opened, Conversation Closed, Conversation Tag Added and Conversation Tag Removed. OneLocal tells Zapier the moment they happen, and the Zap starts straight away on every plan, with a lightning bolt in the editor. The two exceptions are Phone Number Opt-In and Phone Number Opt-Out, which are polling triggers: Zapier checks them every 15 minutes on Free, 2 minutes on Professional and 1 minute on Team and Enterprise.
04What do you need to connect LocalMessages to Zapier?
A OneLocal LocalMessages account, plus read or write access on any conversation you do not own and want a Zap to touch. Start from the Apps page of Zapier with + Add connection, search the app, sign in on the OneLocal side and grant access. Then prepare your account: Assign Conversation picks an employee and the tag actions pick a conversation tag, both from what already exists in OneLocal. Create the employees and tags you need before building the Zap.
05Why does a LocalMessages Zap keep sending texts?
Because it is probably starting itself. If New Message is set to sent messages and the Zap ends with Send Message, each text the Zap sends counts as a new sent message, which starts the Zap again. Each loop uses a task. The fix is in the trigger: set the required message type to received messages only, or add a filter that stops the texts your Zap sends. The same pattern applies to tags, with Conversation Tag Added followed by Add Conversation Tag.
06What if the LocalMessages operation you need does not exist on Zapier?
Then the integration does not cover it. On Zapier, LocalMessages offers eight triggers and four actions: Send Message, Assign Conversation, Add Conversation Tag and Remove Conversation Tag. There is no search step, no action to close a conversation, and no action to change a customer's consent. Some needs can be rebuilt from what exists, for instance a tag that another Zap reacts to. For the rest, the options are asking OneLocal for the operation or using a different automation tool for that part.
07Zapier, Make or n8n for LocalMessages?
Pick on criteria rather than reputation. For LocalMessages on Zapier, the facts are: six instant triggers that fire straight away even on the free plan, two consent triggers that poll, four actions, no search, and a free plan capped at two-step Zaps. So check three things in each tool: whether messages and calls arrive instantly, whether you can find a conversation without its ID, and what a routing scenario of three steps costs at your monthly message volume.
Same platform

Other docs you might need on this stack.

Browse all integrations