Audit Google Maps branch listings with HasData and Google Sheets
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 12 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Google Sheets and Hasdata (community).
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Settings (Edit Fields (Set)): sets 3 fields: spreadsheet_id, max_items, country_calling_code
- Validate settings (Code): runs custom JavaScript code
- Read input (Google Sheets): read (sheet)
- Validate input batch (Code): runs custom JavaScript code
- Prepare queue read (Code): runs custom JavaScript code
- Read Results (Google Sheets): read (sheet)
- Check saved keys (Code): runs custom JavaScript code
- Fetch search evidence (Has Data): place (google maps)
- Attach search context (Code): runs custom JavaScript code
- Build review rows (Code): runs custom JavaScript code
…plus 1 more step. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @hasdata/n8n-nodes-hasdata is verified or supports 3.0 (used in Fetch search evidence).
Nodes used (5)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - Google Sheets
n8n-nodes-base.googleSheets - Has Data
@hasdata/n8n-nodes-hasdata.hasData
From the author
Quick overview Check whether your branches' Google Maps listings match your approved names, addresses, phone numbers and websites. This workflow saves differences and missing fields to Google Sheets, then identifies previously different fields that match on…