- Home
- Resources
- Integrations
- Local Falcon
Local Falcon Zapier integrationAutomate Local Falcon with Zapier.
The Local Falcon Zapier integration gives you 6 triggers, 0 actions and 13 searches. New scan, keyword, location, trend and Falcon Guard reports can start a Zap, and searches pull a report's details so another app receives them, ready to use.
Verified Trustpilot reviews · AI, automation & growth agency
What the Local Falcon Zapier integration actually does
It carries your local ranking reports out of Local Falcon and into the tools where you share or archive them. A Zap (the automation you build on Zapier) starts when Local Falcon has a new report, then a search step can fetch the details of a report before another app writes them down.
A competitor list per scan. New Scan Report starts the Zap, then Get Competitor Report retrieves the competitors found for that scan, from its Report Key, so they can be logged elsewhere.
A trend archive that grows by itself. New Trend Report fires each time a trend report is created, and the next step files it in a spreadsheet or document of your choice.
Campaign follow-up for the team. New Campaign reacts to campaigns created or updated, which keeps a shared tracking sheet in line with Local Falcon.
What Zapier does not do with Local Falcon: there is no action at all. A Zap cannot launch a scan, create a campaign or change anything in Local Falcon; it can only read. None of the 6 triggers is instant either: each one waits for Zapier's next check. And every search that targets a single report needs its Report Key, or a Place ID for Falcon Guard.
This site has no Local Falcon page for Make or n8n; see our Make vs Zapier comparison.
Zapier vocabulary in one minute
Eight words come back throughout this page. Here they are once, in plain language.
- Zap
- The automation itself: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event that starts the Zap, such as a new scan report. 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. Local Falcon offers none.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan counts these and nothing else.
- Polling vs instant
- A polling trigger is checked on a timer; an instant one is reported by the app at once. All Local Falcon triggers poll.
- Search step
- A step that looks up something that already exists in an app, so the steps after it can use what it found.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter, a search or a second action makes one, and it needs a paid plan.
What a Local Falcon Zap really costs
Local Falcon is not a premium app, so it works on the free plan, within that plan's two-step limit.
- Free plan100 tasks a month, unlimited Zaps
- Free plan limitTwo steps: one trigger, one action
- Premium appNo, works on the free plan
- Search in the ZapMulti-step Zap, paid plan
The trigger never costs a task, however often Zapier checks Local Falcon for new reports. Only an action that succeeds is billed, and here that action always belongs to another app. A new report copied into one other app is a two-step Zap, fine on Free. As soon as you add a search, such as Get Competitor Report, the Zap becomes multi-step and needs a paid plan. All 6 triggers poll, so the grid below sets how soon a report is picked up.
Connect Local Falcon to Zapier in 3 steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a Local Falcon account first, plus access to any reports you do not own yourself but want the Zap to read.
- 02
Pick Local Falcon
Type Local Falcon in the search box of the dialog, select it and click Add connection. A new tab opens on the Local Falcon side so you can sign in there.
- 03
Sign in and grant access
Log in to Local Falcon in that tab and allow Zapier to use the account. The connection then appears on your Apps page, and every Local Falcon step reuses it.
Your first Zap: log the competitors of each new scan
GoalEach new scan report triggers a lookup of its competitor list, which is then written as a row in your spreadsheet.
- 01
Create the Zap and pick the trigger
Start a new Zap, choose Local Falcon and the New Scan Report event, then your connection. It is a polling trigger: Zapier checks Local Falcon on your plan's interval.
- 02
Test it on a real report
Run the test. Zapier brings back the three most recent scan reports of the connected account, so you can pick a real one and see which fields it carries.
- 03
Add Get Competitor Report
Add a Local Falcon step and pick Get Competitor Report under the search heading. Map the scan's Report Key into the required field, then test the step on that report.
- 04
Add the spreadsheet step
Add your spreadsheet app with its add-row action and map the competitor data found by the search into the columns you want. Test it and check the row.
- 05
Publish
Click Publish to switch the Zap on. The search makes it multi-step, so a paid plan is required. Each new scan report then runs the whole chain once.
The 6 Local Falcon triggers
6 events start a Zap when something happens in Local Falcon. Zapier checks for them at the interval your plan allows.
New Campaign
Polling triggerIn Zapier“Triggers when a new campaign is created or updated.”
Starts your Zap when a campaign appears in Local Falcon, and also when an existing one changes. The campaign record then flows to the next steps.
New Falcon Guard Report
Polling triggerIn Zapier“Triggers when a new Falcon Guard report is created or updated.”
Reacts to a Falcon Guard report being created or updated. Your Zap receives the report at Zapier's next check.
New Keyword Report
Polling triggerIn Zapier“Triggers when a new keyword report is generated.”
Fires when Zapier spots a new keyword report generated by Local Falcon. It is the entry point for anything you want to do with keyword results outside the app.
New Location Report
Polling triggerIn Zapier“Triggers when a new Location report is generated.”
Runs when a new location report is generated. Each run hands the following steps a report tied to one of your locations.
New Scan Report
Polling triggerIn Zapier“Triggers when a new scan report is generated.”
Watches for a newly generated scan report, the basic output of Local Falcon.
New Trend Report
Polling triggerIn Zapier“Triggers when a new trend report is created.”
Starts a Zap when a trend report is created. Unlike the campaign and Falcon Guard triggers, the source only mentions creation, not updates.
The 13 Local Falcon searches
13 search steps look for data that already exists in Local Falcon, so a later step can use it.
A search step reads something that already exists in Local Falcon and hands it to the steps after it. In the editor, these sit at the bottom of the Action event list, under SEARCH. Local Falcon offers no find-or-create variant: nothing here can create a report. Three settings decide what happens when a search comes back empty or crowded.
Get All Campaigns
SearchIn Zapier“Retrieves all campaign reports”
Retrieves every campaign report on the account, with no key to supply.
Get All Falcon Guard Reports
SearchIn Zapier“Retrieve all Falcon Guard reports”
Brings back all the Falcon Guard reports of the account in one go, without a Place ID.
Get All Scan Reports
SearchIn Zapier“Retrieves all scan reports.”
Lists all scan reports stored in Local Falcon. No field is required to run it.
Get Campaign Report
SearchIn Zapier“Retrieves the details of a campaign”
Fetches the details of one campaign from its Report Key, the only required field.
Get Competitor Report
SearchIn Zapier“Retrieves the list of competitors for a scan”
Returns the list of competitors found for a given scan, identified by its Report Key.
Get Falcon Guard Report
SearchIn Zapier“Retrieves the details of a Falcon Guard Report”
Reads one Falcon Guard report. Unlike the other single-report searches, it asks for a Place ID instead of a Report Key.
Get Keyword Report
SearchIn Zapier“Retrieve details of a Keyword Report.”
Looks up a single keyword report from the Report Key you map in, and passes its details on.
Get All Keyword Reports
SearchIn Zapier“Retrieves all keyword reports.”
Pulls every keyword report on the account into the Zap, with no field to fill.
Get Location Report
SearchIn Zapier“Retrieve details of a location report.”
Retrieves the details of one location report, located by its Report Key.
Get All Location Reports
SearchIn Zapier“Retrieves all location reports.”
Gathers all location reports in one step, without any key.
Get Scan Report
SearchIn Zapier“Retrieves details of a report.”
Reads one scan report in detail, from its Report Key. It is the single-scan counterpart of Get All Scan Reports.
Get Trend Report
SearchIn Zapier“Retrieves details of a Trend Report.”
Returns the details of one trend report, once you give it the Report Key.
Get All Trend Reports
SearchIn Zapier“Retrieves all trend reports.”
Collects every trend report of the account, no key required.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and the steps that relied on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this turns a search into a find-or-create. Local Falcon exposes no such variant, so its searches only ever read.
- If multiple search results are found?Three ways out when several items match: keep the first, which is the default, stop the Zap, or hand all of them on at once.
When a Local Falcon Zap breaks
Zapier attaches no help article to Local Falcon, and the source gives no app-specific limit. The surprises come from how Zapier itself works.
Four situations account for most of them. If one hits you, see our Zapier troubleshooting page.
Old reports are never picked up
A Zap only reacts to reports that appear after you switch it on. Everything generated before stays in Local Falcon; moving that history is a separate job.A flood of reports is held back
If Local Falcon suddenly returns a huge batch, after a bulk import for example, Zapier's flood protection can hold those items back.The same report does not fire twice
On a polling trigger Zapier remembers what it has already seen, so the same report never starts the Zap a second time.A search that finds nothing stops the Zap
With the default setting, an empty search ends the run and skips the steps after it. A Report Key that matches no report can be the cause.
Need help automating Local Falcon with Zapier?
A person reads every message.



