Block 1 - When Executed by Another Workflow
- Type / Role
- n8n-nodes-base.executeWorkflowTrigger - executeWorkflowTrigger
- Config choices
- Version 1.1
Comprehensive contact enrichment with Apollo, LinkedIn, and GPT-4o for HubSpot
Workflow preview
100%
$20/month : Unlimited workflows
2500 executions/month
THE #1 IN WEB SCRAPING
Scrape any website without limits
HOSTINGER 
Early Deal
DISCOUNT 20% Try free
Early DealDISCOUNT 20%
Self-hosted n8n
Unlimited workflows - from $4.99/mo
#1 hub for scraping, AI & automation
6000+ actors - $5 credits/mo
Important notice
This workflow is provided as-is. Please review and test before using in production.
1. Workflow Overview
Summary Turns a plain name + email into a fully enriched HubSpot contact by matching the person in Apollo, pulling their latest LinkedIn activity, summarising the findings with GPT 4o, and upsertin...
Best for
- Lead Generation automation workflows
- AI Summarization automation workflows
- advanced n8n builders looking for reusable templates
Tools used
n8n-nodes-base.executeworkflowtrigger, n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.hubspot, @n8n/n8n-nodes-langchain.outputparserautofixing, @n8n/n8n-nodes-langchain.outputparserstructured, @n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.chainllm
Source and attribution
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Interlock GTM.
Original n8n.io source1.1 Workflow description
- Title
- Comprehensive contact enrichment with Apollo, LinkedIn, and GPT-4o for HubSpot
- Workflow name
- Comprehensive contact enrichment with Apollo, LinkedIn, and GPT-4o for HubSpot
Summary
Turns a plain name + email into a fully-enriched HubSpot contact by matching the person in Apollo, pulling their latest LinkedIn activity, summarising the findings with GPT-4o, and upserting the clean data into HubSpot
Key use-cases
SDRs enriching inbound demo requests before routing
RevOps teams keeping executive records fresh
Marketers building highly-segmented email audiences
Inputs
| Field | Type | Example |
|---|---|---|
| name | string | “Jane Doe” |
| string | “[email protected]” |
Required credentials
| Service | Node | Notes |
|---|---|---|
| Apollo.io API key | HTTP Request – “Enrich with Apollo” | Set in header x-api-key |
| RapidAPI key | (Fresh-LinkedIn-Profile-Data) “Get recent posts” | Header x-rapidapi-key |
| OpenAI 3 LangChain nodes | Supply an API key | default model gpt-4o-mini |
| HubSpot OAuth2 | “Enrich in HubSpot” | Add/create any custom contact properties referenced |
High-level flow Trigger – Runs when another workflow passes name & email.
Clean – JS Code node normalises & deduplicates emails.
Apollo match – Queries /people/match; skips if no person.
LinkedIn fetch – Grabs up to 3 original posts from last 30 days.
AI summary chain
OpenAI → Structured/Auto-fixing parsers
Produces a strict JSON block with job title, location, summaries, etc.
HubSpot upsert – Maps every key (plus five custom properties) into the contact record.
Sticky-notes annotate the canvas; error-prone bits have retry logic.
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 2 - Enrich with Apollo
- Type / Role
- n8n-nodes-base.httpRequest - httpRequest
- Config choices
- Version 4.2
Block 3 - Found?
- Type / Role
- n8n-nodes-base.if - if
- Config choices
- Version 2.2
Block 4 - Enrich in HubSpot1
- Type / Role
- n8n-nodes-base.hubspot - hubspot
- Config choices
- Version 2.1
Block 5 - Auto-fixing Output Parser2
- Type / Role
- @n8n/n8n-nodes-langchain.outputParserAutofixing - outputParserAutofixing
- Config choices
- Version 1
Block 6 - Structured Output Parser2
- Type / Role
- @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
- Config choices
- Version 1.2
Block 7 - OpenAI Chat Model5
- Type / Role
- @n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
- Config choices
- Version 1.2
Block 8 - Enrichment summary agent
- Type / Role
- @n8n/n8n-nodes-langchain.chainLlm - chainLlm
- Config choices
- Version 1.6
Block 9 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Block 10 - Sticky Note2
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Block 11 - Sticky Note3
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Block 12 - Merge
- Type / Role
- n8n-nodes-base.merge - merge
- Config choices
- Version 3.1
Block 13 - OpenAI Chat Model6
- Type / Role
- @n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
- Config choices
- Version 1.2
Block 14 - Get recent posts
- Type / Role
- n8n-nodes-base.httpRequest - httpRequest
- Config choices
- Version 4.2
Block 15 - Split Out
- Type / Role
- n8n-nodes-base.splitOut - splitOut
- Config choices
- Version 1
Block 16 - Filter out reshares and old posts
- Type / Role
- n8n-nodes-base.filter - filter
- Config choices
- Version 2.2
Block 17 - Limit to 3
- Type / Role
- n8n-nodes-base.limit - limit
- Config choices
- Version 1
Block 18 - Sort by post date
- Type / Role
- n8n-nodes-base.sort - sort
- Config choices
- Version 1
Block 19 - Aggregate
- Type / Role
- n8n-nodes-base.aggregate - aggregate
- Config choices
- Version 1
Block 20 - Loop Over Items
- Type / Role
- n8n-nodes-base.splitInBatches - splitInBatches
- Config choices
- Version 3
Block 21 - Extract fields
- Type / Role
- n8n-nodes-base.set - set
- Config choices
- Version 3.4
Block 22 - Sticky Note5
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Block 23 - clean
- Type / Role
- n8n-nodes-base.code - code
- Config choices
- Version 2
Block 24 - Sticky Note1
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
3. Summary Table
| Workflow | Comprehensive contact enrichment with Apollo, LinkedIn, and GPT-4o for HubSpot |
|---|---|
| Complexity | advanced |
| Nodes | 24 |
| Categories | Lead Generation, AI Summarization |
| Author | Interlock GTM |
| Published | 17 Jul 2025 |
4. Reproducing the Workflow from Scratch
-
1. Download the workflow JSON
Use the JSON export at /data/workflows/6103/6103.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.
Frequently asked questions
What does Comprehensive contact enrichment with Apollo, LinkedIn, and GPT-4o for HubSpot do?
Summary Turns a plain name + email into a fully enriched HubSpot contact by matching the person in Apollo, pulling their latest LinkedIn activity, summarising the findings with GPT 4o, and upsertin...
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.