Automation library · Lead generation

Google Maps Lead Gen & Email Deduplication Pipeline

Started by an event in a connected app, and works across Airtable and Gmail. 10 steps, 3 branches: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
3Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Logic 4Service 5

The steps in the order they run, from what starts it.

  1. 1Manual triggerManual triggerStarts it
  2. 2Scrape Google MapsHttp RequestService
  3. 3Has website?IfLogic
  4. 4Fetch website HTMLHttp RequestService
  5. 5Extract email from HTMLCodeLogic
  6. 6Has email?IfLogic
  7. 7Save lead to AirtableAirtableService
  8. 8Already emailed?IfLogic
  9. 9Send outreach emailGmailService
  10. 10Mark as emailedAirtableService

How it's built

Starts on
An event in a connected app
Steps
10, with 3 branches
Size
Medium: a working afternoon
Connects to
Airtable, Gmail
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Airtable and Gmail accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 10 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 10 steps before you point it at anything that matters.