Sync and enrich HubSpot leads from Google Sheets and Telegram with Gemini and Lusha

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Best for

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

Tools used

n8n-nodes-base.hubspot, n8n-nodes-base.switch, n8n-nodes-base.telegramtrigger, @n8n/n8n-nodes-langchain.googlegemini, n8n-nodes-base.httprequest, n8n-nodes-base.googlesheetstrigger, n8n-nodes-base.filter, n8n-nodes-base.telegram

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title: Sync and enrich HubSpot leads from Google Sheets and Telegram with Gemini and Lusha
Workflow name: Sync and enrich HubSpot leads from Google Sheets and Telegram with Gemini and Lusha

This workflow automates lead ingestion from Google Sheets and Telegram, leveraging Gemini AI and Lusha for intelligent matching and deep data enrichment. By normalizing incoming data into a standard structure, it uses custom fuzzy logic to identify existing HubSpot records—preventing duplicates and ensuring your CRM stays clean with validated contact and company details.

Key Features:

Agnostic Intake: Seamlessly processes leads from structured Google Sheets or raw Telegram messages parsed by Gemini AI.

Intelligent Matching: Custom JS engine performs two-tier matching (hard & fuzzy) to save Lusha credits and keep CRM data integrity.

Deep Enrichment: Automatically triggers Lusha API to find missing emails and update firmographic data like revenue and industry.

Automated Sync: Closes the loop by notifying the team on Telegram and updating the spreadsheet status once a lead is processed.

Setup Instructions:

Connect your HubSpot, Lusha, Gemini, Google Sheets, and Telegram credentials.
Input your Spreadsheet ID in the 'Trigger' and 'Acknowledge' nodes.
Adjust the similarity threshold in the 'Switch Logic' node (default 80) based on your data needs.

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 - HubSpot: Update Company

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

Block 2 - HubSpot: Create Company

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

Block 3 - Switch Logic

Type / Role: n8n-nodes-base.switch - switch
Config choices: Version 3.4

Block 4 - Telegram Trigger

Type / Role: n8n-nodes-base.telegramTrigger - telegramTrigger
Config choices: Version 1.2

Block 5 - Parse Telegram Message

Type / Role: @n8n/n8n-nodes-langchain.googleGemini - googleGemini
Config choices: Version 1

Block 6 - Get HubSpot data

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

Block 7 - New or Updated row

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

Block 8 - Create or update a contact

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

Block 9 - Add a Note to Hubspot company

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

Block 10 - Identify Telegram triggered flow

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

Block 11 - Update Telegram user

Type / Role: n8n-nodes-base.telegram - telegram
Config choices: Version 1.2

Block 12 - Identify updated row

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

Block 13 - Acknowledge in sheet

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.7

Block 14 - Resolve Company ID

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

Block 15 - Retry ID resolution

Type / Role: n8n-nodes-base.wait - wait
Config choices: Version 1.1

Block 16 - Filter processed lines

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

Block 17 - Lusha Enrichment - email

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

Block 18 - Switch on email field

Type / Role: n8n-nodes-base.switch - switch
Config choices: Version 3.4

Block 19 - Lusha Company Enrichment

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

Block 20 - HubSpot: Update Enriched Company

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

Block 21 - Domain Resolver

Type / Role: @n8n/n8n-nodes-langchain.googleGemini - googleGemini
Config choices: Version 1

Block 22 - Sticky Note3

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

Block 23 - Match Lead to Existing Company

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

Block 24 - Append Resolved Domain to Lead

Type / Role: n8n-nodes-base.merge - merge
Config choices: Version 3.2

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

3. Summary Table

Workflow	Sync and enrich HubSpot leads from Google Sheets and Telegram with Gemini and Lusha
Complexity	advanced
Nodes	39
Categories	Lead Generation, AI Summarization
Author	Danny
Published	14 Jan 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/12708/12708.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
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. 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.

Download workflow JSON Original n8n.io source Lead Generation workflows AI Summarization workflows

Frequently asked questions

What does Sync and enrich HubSpot leads from Google Sheets and Telegram with Gemini and Lusha do?

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.

Danny

1 workflow

Nodes

n8n-nodes-base.hubspot n8n-nodes-base.switch n8n-nodes-base.telegramtrigger @n8n/n8n-nodes-langchain.googlegemini n8n-nodes-base.httprequest n8n-nodes-base.googlesheetstrigger n8n-nodes-base.filter n8n-nodes-base.telegram

Complexity

advanced

Published 14 Jan 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/12708/12708.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Find LinkedIn engagement opportunities with Apify, Gemini, Google Sheets and Slack

## Quick overview Youtube Video: https://youtu.be/ehsagyRmri4 This workflow runs on a schedule to scrape recent LinkedIn posts with Apify, stores and evaluates them in Google Sheets using Google Gemini, then enriches shortlisted authors with Apify profile data, saves profile results to a second Sheet, and sends Slack alerts for comment and connection opportunities. ## How it works 1. Runs on a schedule and sets the Ideal Customer Profile (ICP) text used for evaluation. 2. Scrapes LinkedIn posts from Apify using the configured search query and merges the results with existing rows from a Google Sheets “Linkedin_Outreach_oppurtunities” sheet. 3. Limits processing to two posts, upserts the post details into Google Sheets, and sends each post’s content to Google Gemini to score whether it is a comment opportunity. 4. If the post is marked as an opportunity with a confidence score above 80, the workflow updates the corresponding Google Sheets row with the AI reasoning and suggested comment angle. 5. Aggregates the qualified opportunities, compares their author profile URLs against an existing “Profile_scraper” Google Sheet, and keeps only authors that are not already present. 6. Scrapes each new author profile with an Apify profile scraper, uses Google Gemini to score ICP match, saves the profile details and qualification summary to the “Profile_scraper” Google Sheet, and posts a Slack message with the shortlisted profile link. 7. Separately, a Google Sheets trigger watches the opportunities sheet for row updates and sends a Slack alert containing the post link, reasoning, and comment angle. ## Setup 1. Add Apify credentials and verify the actor IDs and input parameters for the LinkedIn post scraper and the profile scraper. 2. Configure Google Sheets access (service account for read/write nodes and a Google Sheets Trigger OAuth connection) and update the document IDs/sheet tabs for both the opportunities sheet and the profile sheet. 3. Add Google Gemini (Google PaLM) credentials and confirm the selected Gemini model names in both AI evaluation steps. 4. Add Slack credentials, choose the target channel, and adjust the Slack message text if needed. 5. Customize the ICP text and the LinkedIn search query/posted time window to match the audience and volume you want to monitor.

View

Enrich existing HubSpot company records with Veridion

## Quick Overview This workflow manually enriches existing HubSpot companies using Veridion, skipping records already marked as enriched and updating HubSpot with matched company details like industry, location, and key firmographics. ## How it works 1. Runs when you manually execute the workflow. 2. Fetches up to 100 companies from HubSpot and includes key properties such as name, domain, phone, and the custom veridion_enriched flag. 3. Stops with a clear error if the veridion_enriched property is missing, otherwise filters to only companies not yet marked as enriched. 4. Retrieves full details for each selected HubSpot company and sends its name, domain/website, and phone to Veridion for enrichment. 5. Checks whether Veridion returns a match and skips companies without a match. 6. Maps key Veridion fields and updates the HubSpot company record with enriched details and sets veridion_enriched to true. ## Setup 1. Create the HubSpot company custom properties veridion_enriched (boolean/checkbox) and veridion_industry (single-line text). 2. Add HubSpot App Token credentials and ensure the HubSpot company list request includes veridion_enriched, veridion_industry, name, domain/website, phone, and hs_object_id. 3. Add Veridion API credentials and confirm your HubSpot companies have at least a name plus a domain/website or phone for best matching.

View

Identify company decision makers with Coresignal and Google Sheets

## Quick Overview This workflow manually pulls company website data from Google Sheets, finds matching companies in Coresignal, and searches for decision-maker employees. It then writes the resulting contact and company details back to a dedicated “Decision makers” sheet in Google Sheets. ## How it works 1. Manually starts the workflow and reads company rows from a Google Sheets spreadsheet. 2. Normalizes each company website URL into a clean domain and searches Coresignal for the matching company by website domain. 3. Processes companies in batches and writes placeholder “no employee found” company details to the “Decision makers” sheet in Google Sheets. 4. For each matched company, searches Coresignal for current employees whose titles match common executive and leadership roles. 5. If the title-based search does not return a single employee ID, runs a broader Coresignal decision-maker search that excludes HR-related roles and departments. 6. Retrieves detailed employee (and, when needed, company) fields from Coresignal and appends or updates the “Decision makers” sheet with names, titles, emails, LinkedIn URLs, and company information. ## Setup 1. Create a Google Sheets OAuth2 connection and set the source sheet (companies with a Website field) and the target “Decision makers” sheet in the Google Sheets nodes. 2. Create a Coresignal API credential in n8n and ensure your plan supports company and employee Elasticsearch DSL search and profile retrieval. 3. Confirm your input sheet includes a website column named either Website or website, and adjust the Coresignal title/department filters to match the decision-maker roles you want to capture.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Sync and enrich HubSpot leads from Google Sheets and Telegram with Gemini and Lusha

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - HubSpot: Update Company

Block 2 - HubSpot: Create Company

Block 3 - Switch Logic

Block 4 - Telegram Trigger

Block 5 - Parse Telegram Message

Block 6 - Get HubSpot data

Block 7 - New or Updated row

Block 8 - Create or update a contact

Block 9 - Add a Note to Hubspot company

Block 10 - Identify Telegram triggered flow

Block 11 - Update Telegram user

Block 12 - Identify updated row

Block 13 - Acknowledge in sheet

Block 14 - Resolve Company ID

Block 15 - Retry ID resolution

Block 16 - Filter processed lines

Block 17 - Lusha Enrichment - email

Block 18 - Switch on email field

Block 19 - Lusha Company Enrichment

Block 20 - HubSpot: Update Enriched Company

Block 21 - Domain Resolver

Block 22 - Sticky Note3

Block 23 - Match Lead to Existing Company

Block 24 - Append Resolved Domain to Lead

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions