LocalImpact Zapier integrationAutomate LocalImpact with Zapier.
The LocalImpact Zapier integration gives you 1 trigger and 1 action. LocalImpact works on the free plan. This page covers what the review trigger and the review request do, what they cost in tasks, how often new reviews are picked up and what breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the LocalImpact Zapier integration does for you
The integration links your LocalImpact account to Zapier, so a new review can set off work in your other tools, and those tools can ask LocalImpact to send review requests. You build a Zap (one automation: an event that starts it, then the steps that follow) and Zapier runs it each time that event happens.
Reviews your team actually sees. New Review is the trigger (the event that starts the Zap). Each review LocalImpact receives can be posted in your team chat, so the people who should react read it without logging in.
Review requests that go out on their own. Request Review is the action (the step that writes, sends or moves something for you). It sends a review request by email or SMS from the business you pick. Start the Zap from your CRM and every new customer record can trigger a request.
A log of what came in. Send each new review to a spreadsheet and you keep a history you can sort, filter and share with anyone, outside LocalImpact.
What Zapier does not do here: two steps, and that is all. You cannot reply to a review, edit one or fetch older ones from a Zap, and there is no search step. A Zap also starts from the day you publish it: reviews that came in before are never picked up. When the catalog is this short, the n8n vs Zapier comparison is worth a look before you decide.
The Zapier words used on this page
Seven terms, one line each. With these, nothing below needs a second read.
- Zap
- The automation you build: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier simply waits for that event to come in.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something in another app for you.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The allowance of your plan counts those.
- Polling vs instant
- Zapier checks a polling trigger on a timer and keeps only what is new. An instant trigger is reported by the app itself.
- Filter
- A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your LocalImpact account linked to Zapier once, then reused by every step of every Zap that works with it.
What a LocalImpact Zap costs you in tasks
Zapier bills completed actions, not events. The trigger costs nothing, and the checks Zapier runs on LocalImpact are free however often they happen.
- Trigger0 tasks
- Each successful action1 task
- Free plan100 tasks a month, 2-step Zaps
- Premium appNo, works on the free plan
Each action that succeeds counts once, so a three-action Zap uses three times what a one-action Zap uses. An action that fails is not counted. LocalImpact is not a premium app, so it works on the free plan: 100 tasks a month, unlimited Zaps, two steps per Zap. A filter or a second action makes the Zap multi-step, which needs a paid plan. New Review is a polling trigger, so how fast a review reaches your Zap follows the grid below.
Connect your LocalImpact account to Zapier
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. You need a LocalImpact account first, plus access to any business you do not own but want the Zap to use.
- 02
Find LocalImpact in the dialog
Type LocalImpact in the search box of the dialog, select it and click Add connection. A new tab opens on the LocalImpact side so you can sign in with the account that holds your businesses.
- 03
Allow access
Sign in to LocalImpact in that tab and grant Zapier access to the account. The connection then shows up in your Apps list, and every Zap that uses LocalImpact picks it from there.
Your first Zap: share selected reviews with your team
GoalEvery new LocalImpact review that passes your filter lands in your team chat, so the right people read it.
- 01
Create the Zap and set the trigger
Start a new Zap, choose LocalImpact and New Review as the event, then pick your connection. It is a polling trigger, so how often it is checked depends on your plan.
- 02
Test it on real reviews
Run the test. Zapier brings back the three most recent reviews of your account. Pick one: it is the sample you will map fields from in the next steps.
- 03
Add the filter
Click the plus icon, choose Filter and fill the three boxes: the field to look at, the rule and the value. A number rule only works on numbers.
- 04
Add the chat message and test
Add the action of your team chat and map the review text into the message. With a filter the Zap is multi-step, so it needs a paid plan. Test each step once.
- 05
Publish
Click Publish to switch it on. Only reviews received from then on go through. If the editor feels new, the Zapier training is a good next step.
The LocalImpact trigger in Zapier
1 event starts a Zap when something happens in LocalImpact. Zapier checks for them at the interval your plan allows.
New Review
Polling triggerIn Zapier“Triggers when a new review is received.”
Starts your Zap when LocalImpact receives a new review, and passes the review on to the following steps so they can share it, log it or act on it.
The LocalImpact action
LocalImpact gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Request Review
ActionIn Zapier“Send a review request via email or SMS.”
Sends a review request by email or SMS on behalf of the business you select, addressed to the person whose details your Zap carries.
When a LocalImpact Zap breaks
Zapier links no help article to LocalImpact and documents no limit of its own for the app. What goes wrong comes from how Zapier works and from the required fields.
These are the cases to know before you publish. For an error that is not listed here, the Zapier troubleshooting page is the place to start.
Older reviews are never replayed
A Zap only reacts to what happens after you switch it on. Reviews received before that are ignored, and moving them is a separate job.A request with no first name
Request Review needs a First Name. When the step before it brings an empty one, the action fails, and that failed run costs no task.A wave of reviews held back
When the trigger suddenly returns a huge batch, after an import for instance, Zapier's flood protection can hold the Zap back.A request loop
A Zap that writes into the place its own trigger watches sets itself off again and again. Keep the request Zap and the review Zap apart.
Need help automating LocalImpact with Zapier?
A person reads every message.
