Google Sheets + Clearbit: enriched leads in Notion
Your sales team should not be googling every company five minutes before a call. But that’s what happens when lead info lives in a messy Sheet, and “research” means opening 12 tabs and hoping you found the right logo.
This lead enrichment automation hits Sales Ops first (because they own the process), but SDRs and account managers feel it too. When every record is missing firmographics, brand details, or even a clean domain, you lose time and show up less prepared.
This workflow pulls leads from Google Sheets, enriches them through Clearbit, then writes a complete profile into Notion (and ClickUp), with a log back in Sheets. You’ll see what it automates, what results to expect, and what you need to run it reliably.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Sheets + Clearbit: enriched leads in Notion
flowchart LR
subgraph sg0["Manual Execution Start Flow"]
direction LR
n0@{ icon: "mdi:code-braces", form: "rounded", label: "Derive Domain From Email", 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/>Fetch Company Logo"]
n2["<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/>Retrieve Firm Enrichment"]
n3@{ icon: "mdi:code-braces", form: "rounded", label: "Combine Enrichment Details", pos: "b", h: 48 }
n4@{ icon: "mdi:database", form: "rounded", label: "Update Enriched Leads Sheet", pos: "b", h: 48 }
n5["<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/clickup.svg' width='40' height='40' /></div><br/>Generate ClickUp Task"]
n6@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Validate Unbooked Status", pos: "b", h: 48 }
n7@{ icon: "mdi:database", form: "rounded", label: "Retrieve Sheet Rows", pos: "b", h: 48 }
n8@{ icon: "mdi:play-circle", form: "rounded", label: "Manual Execution Start", pos: "b", h: 48 }
n9["<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/merge.svg' width='40' height='40' /></div><br/>Merge Data Streams"]
n10["<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/notion.dark.svg' width='40' height='40' /></div><br/>Create Notion Record"]
n9 --> n3
n1 --> n9
n6 --> n0
n7 --> n6
n3 --> n10
n3 --> n5
n10 --> n4
n0 --> n1
n0 --> n2
n2 --> n9
n8 --> n7
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 n8 trigger
class n6 decision
class n4,n7,n10 database
class n1,n2 api
class n0,n3 code
classDef customIcon fill:none,stroke:none
class n1,n2,n5,n9,n10 customIcon
The Problem: Lead research steals selling time
Lead spreadsheets are great for collecting names and emails. They’re terrible at giving reps the context they actually need to run a strong first call. So people improvise. Someone copy-pastes a company name into Google, grabs a random logo, guesses the industry, and hopes the domain is right. Multiply that by a few new leads a day and you get a quiet time sink that never shows up on a dashboard, but absolutely shows up in missed follow-ups and weaker conversations.
It adds up fast. Here’s where it breaks down in real life.
- A rep spends about 10 minutes per lead hunting for the domain, logo, and basic company facts.
- Details end up inconsistent across tools, so Notion says one thing while your tasks say another.
- Manual copying introduces small errors (wrong company, wrong brand, wrong website), and those are embarrassing on calls.
- There’s no reliable “enriched” status trail in Sheets, which makes reporting and handoffs a guessing game.
The Solution: Google Sheets → Clearbit → Notion (with ClickUp)
This workflow turns your lead sheet into a living, enriched lead system. It starts by pulling rows from Google Sheets, then checking whether each lead qualifies for enrichment (for example, still “unbooked” or in the right status). Once a row passes the check, n8n derives the company domain from the email address and uses that domain to call Clearbit endpoints for company enrichment and logos. The workflow merges those responses into a single, clean “lead profile,” then creates a record in Notion and generates a ClickUp task so the next action is obvious. Finally, it updates your “Enriched Leads” sheet so you have a log, history, and a simple way to prevent duplicate work.
The flow begins in Google Sheets and uses an If check to decide what gets processed. Clearbit handles the enrichment and brand assets, then Notion becomes the source of truth while ClickUp becomes the work queue. Sheets stays in the loop as the audit trail.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say your team qualifies 20 new leads a week in Google Sheets. Manually, if a rep spends about 10 minutes per lead pulling a logo, finding the right domain, and grabbing basic company details, that’s roughly 3 hours of research time. With this workflow, the “work” is basically reviewing the Sheet and letting n8n run: a couple minutes to spot-check outputs, then Clearbit and n8n do the rest. You get those hours back, and the lead profile is already waiting in Notion and ClickUp.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets for the lead intake and enrichment log.
- Clearbit to fetch logos and company enrichment.
- Notion + ClickUp to store profiles and create follow-up work.
- Clearbit API key (get it from your Clearbit dashboard).
Skill level: Intermediate. You’ll connect a few accounts, add API keys, and map fields between Sheets, Notion, and ClickUp.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A manual or scheduled run pulls rows from Google Sheets. The workflow starts with a trigger and immediately retrieves lead rows, then processes them in a controlled way so you don’t overload your tools.
A quick filter decides what gets enriched. An If check validates status (for example, “unbooked”), so you’re not enriching leads that shouldn’t be touched yet. Simple, but it saves money and noise.
The workflow derives the domain and fetches enrichment. n8n extracts the company domain from the email, then sends HTTP requests to Clearbit to retrieve firmographics plus brand assets like logos (and related metadata where available).
Notion and ClickUp get updated, then Sheets is logged. A merged, formatted profile is written into Notion as a clean record and into ClickUp as a task. After that, the enriched lead is appended/updated in Google Sheets so you can track what happened and when.
You can easily modify the enrichment trigger rules to match your pipeline, so it runs when a meeting is booked or when a rep is assigned. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
Start the workflow with a manual run so you can validate enrichment logic before activating.
- Add or confirm the Manual Execution Start node as the trigger.
- Connect Manual Execution Start to Retrieve Sheet Rows to begin reading leads.
- Keep the Flowpast Branding sticky note for documentation (optional, no configuration required).
Step 2: Connect Google Sheets for Lead Input and Updates
Configure the Google Sheets nodes to read raw leads and write enrichment results.
- Open Retrieve Sheet Rows and set the spreadsheet and range that contain your inbound leads.
- Credential Required: Connect your Google Sheets credentials in Retrieve Sheet Rows.
- Open Update Enriched Leads Sheet and select the same spreadsheet (or a destination sheet) where enrichment results should be written.
- Credential Required: Connect your Google Sheets credentials in Update Enriched Leads Sheet.
Step 3: Set Up Lead Filtering and Domain Extraction
Filter out booked leads and derive company domains for enrichment.
- In Validate Unbooked Status, add the condition that identifies leads that should proceed (e.g., “Unbooked” flag).
- Connect Validate Unbooked Status to Derive Domain From Email for domain extraction.
- Implement the parsing logic inside Derive Domain From Email to extract the domain from each lead’s email.
Step 4: Configure Enrichment Data Fetch and Merge
Run enrichment requests in parallel and merge the results into a unified record.
- Confirm that Derive Domain From Email outputs to both Fetch Company Logo and Retrieve Firm Enrichment in parallel.
- Configure Fetch Company Logo with the logo API endpoint and map the derived domain into the request.
- Configure Retrieve Firm Enrichment with the firm enrichment API endpoint and map the derived domain into the request.
- Connect both enrichment nodes into Merge Data Streams and then into Combine Enrichment Details.
- In Combine Enrichment Details, combine logo and firm data into a single output object.
Step 5: Configure Output Destinations
Send the enriched record to Notion and ClickUp, then update the lead sheet.
- Ensure Combine Enrichment Details outputs to both Create Notion Record and Generate ClickUp Task in parallel.
- In Create Notion Record, choose the destination database and map enriched fields.
- Credential Required: Connect your Notion credentials in Create Notion Record.
- In Generate ClickUp Task, select the workspace/list and map the enrichment fields into the task details.
- Credential Required: Connect your ClickUp credentials in Generate ClickUp Task.
- Confirm Create Notion Record connects to Update Enriched Leads Sheet to record results back in Google Sheets.
Step 6: Test and Activate Your Workflow
Run a full test to confirm enrichment, creation, and updates are all working as expected.
- Click Execute Workflow on Manual Execution Start to run a test with sample leads.
- Verify that Fetch Company Logo and Retrieve Firm Enrichment return data and that Combine Enrichment Details outputs a complete record.
- Confirm that a new record appears in Notion via Create Notion Record and a task is created in ClickUp via Generate ClickUp Task.
- Check that Update Enriched Leads Sheet writes enriched fields back to Google Sheets.
- When ready for production, toggle the workflow to Active.
Common Gotchas
- Google Sheets permissions can be the quiet culprit. If updates fail, check the connected Google account in n8n credentials and confirm it still has edit access to the target spreadsheet.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Clearbit can rate limit or return partial matches, especially if the domain extraction is off. When results look wrong, inspect the HTTP response in the execution log and verify the derived domain first.
Frequently Asked Questions
About an hour if your APIs and databases are ready.
No. You’ll mostly map fields and paste API keys into the right credential screens.
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 Clearbit API costs, which depend on your plan and usage.
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.
Yes, but you’ll want to remove or disable the “Create Notion Record” node and adjust the mapping so “Generate ClickUp Task” becomes the primary output. Common customizations include changing the status filter in the If node, writing back an “Enriched = Yes” flag to Sheets, and adding a Slack message when enrichment completes.
Most of the time it’s an API key issue or an account plan limitation. Regenerate your Clearbit key, update the HTTP Request headers in n8n, and re-run a single test item. If the domain is malformed (like “gmail.com” or a typo), Clearbit will return weak or empty results, so check the “Derive Domain From Email” output too. Rate limiting can also show up when you enrich a big batch at once.
On n8n Cloud Starter, most teams can handle thousands of executions a month, and self-hosting has no execution cap (it mainly depends on your server). In practice, the limit is usually Clearbit rate limits and how aggressively you batch items in n8n.
Often, yes. This workflow has branching, merging, batching, and multi-destination updates (Notion plus ClickUp plus Sheets), and that gets expensive or awkward in Zapier once you go beyond simple two-step zaps. n8n also makes it easier to inspect raw HTTP responses from Clearbit, which matters when you’re debugging mismatched domains. If you self-host, you can run a lot of enrichments without watching a task counter. Zapier or Make can still be a good fit if you only need “new row → create Notion page” and you never plan to expand it. Talk to an automation expert if you want help choosing.
Once this is running, lead research becomes a background process instead of a daily scramble. Your reps get the context. You get the consistency.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
