Google Sheets + Dumpling AI, local leads on tap

Building local lead lists the “normal” way is brutal. You search Google Places, open a dozen tabs, copy names and phone numbers, then still end up cleaning a messy sheet.

Digital marketers feel it when campaigns need fresh targets fast. A lead gen specialist gets stuck doing the same lookup work every week. Even a busy owner trying to fill a pipeline can use this local leads automation to keep outreach moving without hiring more hands.

This workflow pulls Google Places listings through Dumpling AI and logs them into Google Sheets with consistent fields. You’ll learn what it does, what you need, and how to run it reliably.

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: Google Sheets + Dumpling AI, local leads on tap

Click to explore

flowchart LR

    subgraph sg0["Run Every Day at 1 PM Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "Run Every Day at 1 PM", pos: "b", h: 48 }
        n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/> Scrape Google Places with D.."]
        n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Split Resulting Places List", pos: "b", h: 48 }
        n3@{ icon: "mdi:database", form: "rounded", label: " Save Scraped Data to Sheet", pos: "b", h: 48 }
        n4@{ icon: "mdi:database", form: "rounded", label: "Fetch Search Terms from Sheet", pos: "b", h: 48 }
        n0 --> n4
        n2 --> n3
        n4 --> n1
        n1 --> n2
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n0 trigger
    class n3,n4 database
    class n1 api
    classDef customIcon fill:none,stroke:none
    class n1 customIcon

Why This Matters: Google Places lead lists are slow to build

Manual Google Places research looks easy until you do it at scale. You search “dentists in Dallas,” open listing pages one by one, and copy details into a spreadsheet that never stays consistent. Some listings show a website, others don’t. Phone numbers come in different formats. Addresses are full of quirks. Then you realize you need 200 more leads for a second city, and suddenly your “quick task” becomes your whole afternoon. Honestly, the worst part is the mental load: you’re doing repetitive work while trying not to miss the one field that matters for outreach.

The friction compounds. Here’s where it usually breaks down.

You spend about 2 hours just collecting 50 businesses, and the sheet still isn’t ready to use.
Fields come back inconsistent, so your email or cold call process turns into constant cleanup.
Lead quality drifts because each person on the team copies different details in different formats.
Refreshing a list weekly becomes unrealistic, which means you outreach to stale or closed businesses.

What You’ll Build: a daily Google Places lead list that stays clean

This n8n workflow runs on a schedule (daily at 1 PM by default) and turns a simple list of search terms into a structured lead database. You keep your targeting logic in a Google Sheet as plain text phrases like “coffee shops in Atlanta” or “roofers in Phoenix.” When the workflow runs, it reads each term, sends it to Dumpling AI’s Google Places search endpoint, and receives back a batch of local listings. Then it splits that batch into individual businesses, formats the fields you care about, and appends each business as a new row in an output Google Sheet. By the end, you have a fresh list you can filter, dedupe, and hand to outreach without spending your day copying and pasting.

The workflow starts from a scheduled trigger and pulls your search terms from Google Sheets. Dumpling AI returns the listings, which n8n processes one business at a time. Finally, everything lands in your output sheet with consistent columns, ready for your next campaign.

What You’re Building

What Gets Automated

What You’ll Achieve

Reading a list of “service + city” search terms from Google Sheets each day.
Sending each term to Dumpling AI’s /search-places endpoint via HTTP Request.
Splitting each response into single business entries for clean processing.
Appending title, address, rating, category, phoneNumber, and website into a lead sheet.

Turn about 2 hours of manual lookup into a daily automated refresh.
Get consistent columns that are ready for filters, dedupe, and outreach tools.
Build a repeatable process your team can run without “how do we format this?” debates.
Refresh leads by city or niche by updating one input sheet, not rebuilding lists.
Spend your time on messaging and follow-up instead of collection and cleanup.

Expected Results

Say you track 20 search terms (like “plumbers in Miami”) and you want 20 businesses per term. Manually, pulling 400 listings at even 1 minute each is roughly 6 to 7 hours, and that’s before formatting. With this workflow, you spend about 10 minutes adding or updating search terms in Google Sheets, then let the daily run collect and log everything automatically. The lead sheet is already structured, so your time goes to qualification and outreach, not data entry.

Before You Start

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Google Sheets for your input terms and output log.
Dumpling AI to fetch Google Places listings by keyword.
Dumpling AI API key (get it from your Dumpling AI dashboard)

Skill level: Beginner. You’ll connect accounts, paste an API key, and map a few spreadsheet columns.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

A daily schedule kicks things off. The workflow runs every day at 1 PM, so your lead list keeps updating without anyone remembering to do it.

Search terms are pulled from Google Sheets. Each row is a simple phrase like “dentists in Dallas.” This becomes the “source of truth” for what markets and niches you’re actively targeting.

Dumpling AI fetches Google Places results. n8n sends one request per search term to Dumpling AI’s /search-places endpoint using an HTTP Request node. The response includes businesses with details such as name, rating, category, phone number, address, and website (when available).

Results are split and appended into your lead sheet. n8n processes each business as its own item (so one listing equals one row), then saves it to an output Google Sheet with consistent columns.

You can easily modify the schedule (daily to weekly, or multiple times per day) to fit your outreach rhythm. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Schedule Trigger

Set the workflow to run on a daily schedule using the trigger node.

Add and open Daily Schedule Trigger.
Set the schedule rule to run daily at 13 hours (triggerAtHour).
Connect Daily Schedule Trigger to Retrieve Search Terms.

Step 2: Connect Google Sheets

Configure the input sheet that supplies search terms and the output sheet that stores results.

Open Retrieve Search Terms and select the document Google places.
Set the Sheet Name to Sheet1.
Credential Required: Connect your googleSheetsOAuth2Api credentials for Retrieve Search Terms.
Open Append Places to Sheet and select the document Google places.
Set the Sheet Name to Sheet 2 and the Operation to append.
Credential Required: Connect your googleSheetsOAuth2Api credentials for Append Places to Sheet.

Step 3: Set Up Dumpling Places Request

Send each search term to Dumpling AI and parse the results for individual places.

Open Dumpling Places Request and set the URL to https://app.dumplingai.com/api/v1/search-places.
Set Method to POST and Send Body to true.
Set Body Content Type to json and use the JSON body ={ "query": "{{ $json['places '] }}" }.
Credential Required: Connect your httpHeaderAuth credentials for Dumpling Places Request.
Open Separate Place Entries and set Field to Split Out to places.
Connect Retrieve Search Terms → Dumpling Places Request → Separate Place Entries.

⚠️ Common Pitfall: The query field in Dumpling Places Request references $json['places '] with a trailing space. Ensure your source column name in Retrieve Search Terms matches this exactly, or update the expression to your actual column name.

Step 4: Configure the Output Mapping

Map each place attribute into the Google Sheet output columns.

In Append Places to Sheet, confirm the column mappings use expressions:
Set title to {{ $json.title }}, rating to {{ $json.rating }}, and address to {{ $json.address }}.
Set website to {{ $json.website }}, category to {{ $json.category }}, and phoneNumber to {{ $json.phoneNumber }}.
Connect Separate Place Entries to Append Places to Sheet.

Step 5: Test and Activate Your Workflow

Run a manual test to confirm data flows correctly and then activate the workflow for daily operation.

Click Execute Workflow to run a manual test from Daily Schedule Trigger.
Verify that Dumpling Places Request returns a places array and Separate Place Entries outputs individual items.
Check Append Places to Sheet to confirm new rows appear in Sheet 2 with mapped fields.
Once successful, toggle the workflow Active to enable daily runs at 13:00.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

Dumpling AI credentials can expire or have quota limits. If requests start failing, check your Dumpling AI dashboard for API key status and usage first.
If you’re using Wait-like timing (or your Dumpling AI responses are slow), processing times vary. If the workflow tries to append before data is present, rerun the failed execution or reduce batch size so responses arrive consistently.
Google Sheets “append row” issues are often a sheet structure problem, not n8n. Make sure your output sheet has the exact columns you expect (title, address, rating, category, phoneNumber, website) and that the n8n Google Sheets connection has edit access.

Quick Answers

What’s the setup time for this local leads automation?

About 30 minutes if your Sheets and Dumpling AI key are ready.

Is coding required for this local lead scraping automation?

No. You’ll connect Google Sheets, add your Dumpling AI API key, and map fields once.

Is n8n free to use for this local leads automation workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Dumpling AI API usage based on how many searches you run daily.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I modify this local leads automation workflow for different use cases?

Yes, and it’s mostly editing the input sheet and the field mapping. Swap the daily schedule to weekly if you only refresh lists for campaigns, or run it multiple times a day during a launch. You can also change what you write to Google Sheets by adjusting the field mapping before the “Append Places to Sheet” step (for example, add a “search_term” column so you know where each lead came from). If you want a different data source later, you’d replace the Dumpling Places HTTP Request with another provider, then keep the same split-and-append structure.

Why is my Dumpling AI connection failing in this workflow?

Usually it’s an invalid or expired API key, or you’ve hit a usage limit. Regenerate the key in Dumpling AI, paste it into the HTTP Request node, and rerun one search term to confirm the response. If the key is fine, check that your request includes the exact endpoint and required headers, because a tiny mismatch can return an empty result. Also watch for rate limiting if you’re running a large batch of search terms at once.

What volume can this local leads automation workflow process?

On n8n Cloud Starter, you’re typically fine for small daily batches, and higher plans handle larger volumes. If you self-host, there’s no execution limit (it depends on your server). Practically, the bottleneck is usually the Dumpling AI request rate and how many search terms you run per day, not Google Sheets.

Is this local leads automation better than using Zapier or Make?

Often, yes, because this workflow benefits from batching, splitting results into items, and handling structured field mapping without paying extra for every branch. n8n is also easier to extend when you want logic like “only save listings with a website” or “skip anything under 4 stars.” Zapier or Make can still work if you keep it simple, but complex list handling tends to get expensive or awkward. The big deciding factor is how often you run it and how many terms you process. Talk to an automation expert if you want a recommendation based on your volume.

Once this is running, fresh local leads show up in your sheet like clockwork. Set it up, tweak the search terms as you grow, and move on to the work that actually brings in revenue.

Google Sheets + Dumpling AI, local leads on tap

How This Automation Works

n8n Workflow Template: Google Sheets + Dumpling AI, local leads on tap

Why This Matters: Google Places lead lists are slow to build