Resources · Zapier integration

OneLocal LocalReviews Zapier integrationAutomate OneLocal LocalReviews with Zapier.

The OneLocal LocalReviews Zapier integration gives you 2 triggers, 1 action and 0 searches. New reviews and survey answers flow out to your other apps, and feedback requests go out by text or email without anyone opening LocalReviews.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the OneLocal LocalReviews Zapier integration does for you

Zapier is a service that runs automations between apps for you, with no code. Plugged into OneLocal LocalReviews, it watches your account for fresh reviews and survey answers and passes them on. It also works the other way: another app can ask LocalReviews to send a feedback request to a customer.

Three results people usually build. A team channel that shows every new review, built on New Review. A spreadsheet or CRM record that grows with each survey answer, built on New Survey Response. And feedback requests that leave by text message or email when a job is closed in another tool, built on Request Feedback.

Now the limits, because they shape what you can plan. There is no search step, so a Zap cannot look up an existing review or contact inside LocalReviews. Neither trigger is instant: a review shows up in the Zap at Zapier's next check, not the second it is posted. And no action answers, edits or deletes a review. The one thing a Zap can do inside LocalReviews is send a feedback request.

The Zapier editor offers exactly these three operations for the app, so what you read here is what you will find there.

That is a narrow catalog, which makes the tool choice worth a minute. Two pages to keep at hand: Make vs Zapier and n8n vs Zapier.

Vocabulary

Zapier words, in plain English

Eight terms come back on every line of this page. Here is each one in a sentence.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run every single time the trigger event happens.
Trigger
The event that starts a Zap. With LocalReviews, that is a new review or a new survey response arriving in your account.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, like a feedback request.
Task
The unit Zapier bills: one action completed successfully. The allowance on your plan is a monthly count of those.
Polling vs instant
Polling: Zapier checks the app on a timer and keeps only what is new. Instant: the app reports the event itself. Both LocalReviews triggers poll.
Filter
A step that lets the Zap continue only when the incoming item meets the condition you set, and stops it right there otherwise.
Search step
A step that looks up something already stored in an app. LocalReviews offers none, so any lookup has to happen in another app.
Connection
Your LocalReviews account linked to Zapier once, then reused by every step of every Zap that touches LocalReviews.
Cost

What it really costs

Zapier bills tasks, and only actions that work count. Checking LocalReviews for new reviews is free, however often it happens.

  • Trigger check0 tasks
  • Successful action1 task each
  • Failed actionNot counted
  • Free plan100 tasks a month, two-step Zaps
  • LocalReviews on freeYes

The free plan gives you 100 tasks a month, unlimited Zaps and a check every 15 minutes. LocalReviews is not reserved for paid plans, so it runs there. The catch is the step count: on free, a Zap is one trigger plus one action, nothing more. Add a filter, a second action or a search step and you have a multi-step Zap, which needs a paid plan. A failed action is not counted; a Zap with three actions uses three times what a one-action Zap uses.

Connect

Connect your LocalReviews account

  1. 01

    Open Apps and start a connection

    In your Zapier account, go to the Apps page and click + Add connection. A dialog opens with a search box: type OneLocal LocalReviews and pick it from the results.

  2. 02

    Sign in to LocalReviews

    Click Add connection. A new tab opens on the LocalReviews sign-in. Log in with the account that holds your surveys and reviews, since every Zap built on this connection reads from it and sends through it.

  3. 03

    Grant access

    Allow Zapier to access the account. The connection is saved and reused by every step that uses LocalReviews. If a colleague owns some of the surveys, make sure you have read or write access to them before you build.

First Zap

Your first Zap: new reviews in the team channel

GoalEvery new review that meets your condition lands in the channel your team reads.

  1. 01

    Pick the trigger

    Build a new Zap. Choose OneLocal LocalReviews as the app that starts it and New Review as the event, then select the connection you just made.

  2. 02

    Test it on a real review

    Run the trigger test. Zapier brings back the three most recent reviews of your account. Pick one of them, so everything you map later is based on real data.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then fill the three boxes: the field to look at, the rule, the value to compare with. A text rule only works on text, a number rule only on numbers.

  4. 04

    Add the message

    Add the action step: your chat app and its message event. Map what the review carries into the message, so the channel shows who wrote it and what they said.

  5. 05

    Test, then publish

    Test each step and read what came back before moving on. Then click Publish to switch the Zap on. With the filter it is a multi-step Zap, so it runs on a paid plan.

Triggers

OneLocal LocalReviews triggers

2 events start a Zap when something happens in OneLocal LocalReviews. Zapier checks for them at the interval your plan allows.

1

New Survey Response

Polling trigger

In Zapier“Triggers when you receive a new survey response.”

Starts your Zap each time a customer answers one of your LocalReviews surveys, and hands that answer to the steps that follow, ready to be copied, sorted or forwarded wherever your team works.

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 owner wants every survey answer logged in a shared sheet, where trends are easier to spot than in the LocalReviews dashboard.
Watch out
only answers given after the Zap is published come through; older responses stay where they are, and moving them is a separate job.
2

New Review

Polling trigger

In Zapier“Triggers when you receive a new review.”

Picks up each review that lands in your LocalReviews account and passes it down the Zap, so a good word or a complaint reaches people who can act on it.

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 store manager wants fresh reviews posted to the team chat instead of checking another dashboard between customers.
Watch out
the plan sets the delay. A review can wait up to 15 minutes on Free, and 1 minute on Team or Enterprise.
Actions

OneLocal LocalReviews actions

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

1

Request Feedback

Action

In Zapier“Sends a feedback request to a phone number or email address”

Sends one of your surveys to a contact by text message or email, so the ask goes out without anyone logging in to LocalReviews.

When to use it
a job is closed or a sale is marked won in your CRM, and the customer should then get a feedback request.
Watch out
Survey, Preferred Delivery Method and Contact Name are all mandatory. The delivery method decides which channel wins when the contact has both an email and a mobile number.
When it breaks

When it breaks

Zapier attaches no help article to LocalReviews, and no limit specific to the app is documented. What can go wrong comes from how Zapier itself works.

  • Older reviews never show up

    A Zap only reacts to what happens after you switch it on. Reviews and survey answers already in LocalReviews are not picked up; moving that backlog is a separate job.

  • A Zap that keeps setting itself off

    If a Zap writes back into the very place its trigger watches, it fires again and again and burns through your monthly task count fast.

  • A sudden flood gets held back

    After a bulk import or a migration, a trigger can return a huge batch at once. Zapier's flood protection may then hold those items back.

  • Duplicates are filtered for you

    On a polling trigger, Zapier remembers what it has already seen, so the same review or response never starts the Zap twice.
Need help

Need help automating OneLocal LocalReviews with Zapier?

A person reads every message.

FAQ

OneLocal LocalReviews and Zapier: common questions

01Is the OneLocal LocalReviews Zapier integration free?
Yes. LocalReviews is not one of the apps Zapier keeps for paid plans, so it works on the free plan. That plan gives you 100 tasks a month, as many Zaps as you like, and a check for new items every 15 minutes. The limit is the shape of the Zap: one trigger and one action, nothing more. Add a filter, a second action or a search step, the Zap becomes multi-step and needs a paid plan. Plan figures change often, so check them on Zapier before you commit.
02How many tasks does a LocalReviews Zap use?
One per successful action, and nothing for the trigger. Zapier can check LocalReviews for new reviews as often as your plan allows without costing you a single task. Each time Request Feedback, or any action in another app, completes, that is one task. An action that fails is not counted. In a Zap with several actions, every action that succeeds counts on its own, so a Zap with three actions uses three times what a one-action Zap does. A few apps and actions take more than one task, so read the step in the editor.
03Do new reviews reach Zapier in real time?
No. Both LocalReviews triggers, New Review and New Survey Response, work by polling: Zapier asks the app for new items at a fixed interval. That interval depends on the plan: 15 minutes on Free, 2 minutes on Professional, 1 minute on Team and Enterprise. On paid plans the interval can be changed, and a check can be run by hand from the editor. The type of a trigger comes from the app itself and cannot be switched from the editor, so there is no instant option to turn on here.
04What do you need to connect a LocalReviews account?
An account on LocalReviews, plus read or write access to anything you do not own yourself and want the Zap to touch. The connection then takes three moves. Open the Apps page of your Zapier account and click + Add connection. Search for OneLocal LocalReviews and pick it. Click Add connection, sign in to LocalReviews in the tab that opens, and grant Zapier access. The connection is saved once and every Zap that uses LocalReviews reuses it, so you do not repeat the sign-in for each new Zap.
05Why can't Request Feedback send anything?
Start with the mandatory fields. The action needs three things: a Survey, a Preferred Delivery Method and a Contact Name. Without a finished survey in your LocalReviews account, the Survey field has nothing to offer, so build one first. The delivery method matters when the contact comes with both an email and a mobile number: it decides whether the request leaves by text or by email. Test the step once with a real record from your trigger app, and read what came back before you publish.
06What if the LocalReviews operation you want is not listed?
Then Zapier does not offer it for this app. The editor shows three operations: New Survey Response and New Review as triggers, and Request Feedback as the only action. There is no search step and no action to edit, answer or delete a review. The usual workaround is to let LocalReviews do what it can, then hand the rest to another app in the same Zap, such as a spreadsheet, a CRM or a chat tool. If the missing piece is central to the project, that is a good reason to compare automation tools before building.
07Zapier, Make or n8n for OneLocal LocalReviews?
Decide on criteria rather than reputation. First, coverage: on Zapier this app has two triggers and one action, so check that each tool lists the operations your scenario needs. Second, delay: on Zapier both triggers poll, so a review waits up to 15 minutes on Free and 1 minute on Team or Enterprise; see whether that suits your team. Third, the shape of your workflow: a single trigger and action stays on the free plan, while filters or extra steps push you to a paid one. Weigh those three points against your budget and skills.
Same platform

Other docs you might need on this stack.

Browse all integrations