Block 1 - if company does not exist on CRM
- Type / Role
- n8n-nodes-base.if - if
- Config choices
- Version 2
Enrich lead that booked a call on Calendly and save it on 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
Use Case When having a call with a new potential customer, one of the keys to getting the most out of the call is to find out as much information as you can about them before the call. Normally thi...
Best for
- Lead Generation automation workflows
- intermediate n8n builders looking for reusable templates
Tools used
n8n-nodes-base.if, n8n-nodes-base.stickynote, n8n-nodes-base.clearbit, n8n-nodes-base.hubspot, n8n-nodes-base.noop, n8n-nodes-base.filter, n8n-nodes-base.calendlytrigger
Source and attribution
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Ricardo Espinozaas.
Original n8n.io source1.1 Workflow description
- Title
- Enrich lead that booked a call on Calendly and save it on Hubspot
- Workflow name
- Enrich lead that booked a call on Calendly and save it on Hubspot
Use Case
When having a call with a new potential customer, one of the keys to getting the most out of the call is to find out as much information as you can about them before the call. Normally this involves a lot of manual research before every call. This workflow automates this tedious work for you.
What this workflow does
The workflow runs every time a new call is booked via your Calendly. It then filters out personal emails, before enriching the email. If the email is attached to a company it enriches the company and upserts it in your Hubspot CRM.
Setup
- Add
Clearbit,Hubspot, andCalendlycredentials. - Click on
Test workflow. - Book a meeting on Calendly so the event starts the workflow. Be aware that you can adapt this workflow to work with your enrichment tool, CRM, and booking tool of choice.
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 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Block 3 - Sticky Note1
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Block 4 - Sticky Note2
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Block 5 - Sticky Note3
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Block 6 - Enrich company
- Type / Role
- n8n-nodes-base.clearbit - clearbit
- Config choices
- Version 1
Block 7 - Create company
- Type / Role
- n8n-nodes-base.hubspot - hubspot
- Config choices
- Version 2
Block 8 - Upsert contact
- Type / Role
- n8n-nodes-base.hubspot - hubspot
- Config choices
- Version 2
Block 9 - Update company
- Type / Role
- n8n-nodes-base.hubspot - hubspot
- Config choices
- Version 2
Block 10 - Contact not found, do nothing
- Type / Role
- n8n-nodes-base.noOp - noOp
- Config choices
- Version 1
Block 11 - Enrich email
- Type / Role
- n8n-nodes-base.clearbit - clearbit
- Config choices
- Version 1
Block 12 - Filter out personal emails
- Type / Role
- n8n-nodes-base.filter - filter
- Config choices
- Version 2
Block 13 - Search company
- Type / Role
- n8n-nodes-base.hubspot - hubspot
- Config choices
- Version 2
Block 14 - Upsert lead
- Type / Role
- n8n-nodes-base.hubspot - hubspot
- Config choices
- Version 2
Block 15 - If person has a company
- Type / Role
- n8n-nodes-base.if - if
- Config choices
- Version 2
Block 16 - Calendly Trigger
- Type / Role
- n8n-nodes-base.calendlyTrigger - calendlyTrigger
- Config choices
- Version 1
3. Summary Table
| Workflow | Enrich lead that booked a call on Calendly and save it on Hubspot |
|---|---|
| Complexity | intermediate |
| Nodes | 16 |
| Categories | Lead Generation |
| Author | Ricardo Espinozaas |
| Published | 23 Feb 2024 |
4. Reproducing the Workflow from Scratch
-
1. Download the workflow JSON
Use the JSON export at /data/workflows/2129/2129.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 Enrich lead that booked a call on Calendly and save it on Hubspot do?
Use Case When having a call with a new potential customer, one of the keys to getting the most out of the call is to find out as much information as you can about them before the call. Normally thi...
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 use case.