HubSpot contact AI enrichment
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: SerpApi (Google Search). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 8 nodes and runs on a schedule (every day). Along the way it connects HubSpot, SerpApi (Google Search) and Google Gemini Chat Model.
How it runs
Trigger: On a schedule (every day).
- Get recently created/updated contacts (HubSpot): get recently created updated
- Filter: keeps only the items that match a condition
- Company Research Agent (AI Agent): runs an AI agent, with model: Google Gemini Chat Model; 1 tool (Search the web with SerpAPI); output parser: Structured Output Parser
- Add company info (HubSpot): uses HubSpot
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- SerpApi (Google Search) in Search the web with SerpAPI1: no direct replacement: call the SerpApi REST API with an HTTP Request tool, or use a verified community node.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| SerpApi (Google Search) Search the web with SerpAPI1 | No direct replacement: call the SerpApi REST API with an HTTP Request tool, or use a verified community node |
Nodes used (7)
- HubSpot
n8n-nodes-base.hubspot - SerpApi (Google Search)
@n8n/n8n-nodes-langchain.toolSerpApi - Filter
n8n-nodes-base.filter - Google Gemini Chat Model
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - AI Agent
@n8n/n8n-nodes-langchain.agent - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
This n8n template auto-enriches brand-new HubSpot contacts with company details. Each day it finds contacts created in the last 24 hours (skipping free email domains), researches the company from the contact’s email domain, and writes back clean fields—no…