Skip to main content

Enrich Airtable company phones from website, LinkedIn, Google Maps, and Claude

Workflow preview

Workflow preview
100%
Enrich Airtable company phones from website, LinkedIn, Google Maps, and Claude preview
Open on n8n.io

1. Workflow Overview

️ Self hosted only — This template uses a community node (Firecrawl) and cannot run on n8n Cloud. Add a workflow screenshot at the top of this listing. Who it's for This workflow is for sa...

Best for

  • Lead Generation automation workflows
  • AI Summarization automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.manualtrigger, n8n-nodes-base.airtable, @mendable/n8n-nodes-firecrawl.firecrawl, @n8n/n8n-nodes-langchain.outputparserstructured, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.if, n8n-nodes-base.httprequest

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Allan Vaccarizi.

Original n8n.io source

1.1 Workflow description

Title
Enrich Airtable company phones from website, LinkedIn, Google Maps, and Claude
Workflow name
Enrich Airtable company phones from website, LinkedIn, Google Maps, and Claude

⚠️ Self-hosted only — This template uses a community node (Firecrawl) and cannot run on n8n Cloud.

> 📸 Add a workflow screenshot at the top of this listing.

Who it's for

This workflow is for sales teams, lead generation agencies, and growth operators who maintain a company database in Airtable and need to automatically enrich records with phone numbers from multiple web sources.

How it works

  1. A manual trigger fetches all Airtable records where the phone number field is empty.
  2. Records are processed one by one through a loop.
  3. Each company's website is scraped using Firecrawl, and the raw markdown is cleaned with a custom code node.
  4. A Claude Sonnet AI agent analyzes the cleaned content and attempts to extract a phone number using a structured output parser.
  5. If the AI finds no phone, the workflow falls back to an Apify LinkedIn scraper, first checking whether the company profile exists.
  6. If LinkedIn also yields nothing, a second fallback calls an Apify Google Maps scraper to search by company name and location.
  7. Whichever source returns a phone number, a code node normalizes the data and writes it back to Airtable. If no source finds a phone, the record is marked as unavailable.

How to set up

  • Connect your Airtable credentials and set the correct base and table in the Search Airtable Records, Update Airtable Phone Found, and Update Airtable Phone Not Found nodes
  • Add your Firecrawl API key to the Scrape Company Website node
  • Add your Anthropic API key to the Claude Sonnet Model sub-node inside AI Phone Finder Agent
  • Add your Apify API token to both the Fetch LinkedIn Phone via Apify and Fetch Google Maps Phone via Apify nodes
  • Review the Clean Scraped Markdown and Refine and Merge Phone Data code nodes to ensure field names match your Airtable schema

Requirements

  • Airtable account with a company database
  • Firecrawl API key
  • Anthropic API key (Claude Sonnet)
  • Apify account with access to the LinkedIn Company Scraper and Google Maps Scraper actors

How to customize

  • Swap out either fallback source (LinkedIn or Google Maps) by bypassing the corresponding branch if you only have access to one Apify actor.
  • Tune the AI system prompt inside the Claude Sonnet model to extract other contact details such as email addresses or physical addresses in addition to phone numbers.
  • Replace the manual trigger with a scheduled trigger to run the enrichment automatically on a daily or weekly basis.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 4 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 6 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 7 - Sticky Note6

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 8 - When Workflow Runs Manually

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 9 - Search Airtable Records

Type / Role
n8n-nodes-base.airtable - airtable
Config choices
Version 2.2

Block 10 - Scrape Company Website

Type / Role
@mendable/n8n-nodes-firecrawl.firecrawl - firecrawl
Config choices
Version 1

Block 11 - Parse Structured Phone Output

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.3

Block 12 - Update Airtable Phone Found

Type / Role
n8n-nodes-base.airtable - airtable
Config choices
Version 2.2

Block 13 - Update Airtable Phone Not Found

Type / Role
n8n-nodes-base.airtable - airtable
Config choices
Version 2.2

Block 14 - AI Phone Finder Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 3.1

Block 15 - If AI Found Phone

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.3

Block 16 - Fetch LinkedIn Phone via Apify

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 17 - Fetch Google Maps Phone via Apify

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.4

Block 18 - If Google Maps Phone Found

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.3

Block 19 - Refine and Merge Phone Data

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 20 - Clean Scraped Markdown

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 21 - If Company Exists in LinkedIn

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.3

Block 22 - Claude Sonnet Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatAnthropic - lmChatAnthropic
Config choices
Version 1.3

Block 23 - Sticky Note13

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 24 - Sticky Note16

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Showing the first 24 of 26 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Enrich Airtable company phones from website, LinkedIn, Google Maps, and Claude
Complexity advanced
Nodes 26
Categories Lead Generation, AI Summarization
Author Allan Vaccarizi
Published 12 May 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15650/15650.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Enrich Airtable company phones from website, LinkedIn, Google Maps, and Claude do?

️ Self hosted only — This template uses a community node (Firecrawl) and cannot run on n8n Cloud. Add a workflow screenshot at the top of this listing. Who it's for This workflow is for sa...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Lead Generation, AI Summarization use case.