Calendly to HubSpot: Enrich Leads with Clearbit & Auto-Create Companies

Overview

This workflow automates the process of capturing new Calendly event invitees, enriching their data with Clearbit, and then creating or updating both contact and company records in HubSpot. It is designed for sales and marketing teams who want to instantly enrich lead data the moment a meeting is booked, ensuring your CRM is always up-to-date with the most accurate company and contact information.

By filtering out personal email addresses (like Gmail, Yahoo, etc.) and only processing business leads, this workflow helps maintain a clean, B2B-focused CRM. It also checks if a company already exists in HubSpot before creating a new record, preventing duplicates and intelligently updating existing company profiles with enriched data.

Step-by-Step Node Breakdown

  1. Calendly Trigger (No auth — uses webhook) — Listens for invitee.created events from Calendly. When someone books a meeting, this node triggers the workflow and passes the invitee's data (including email and name) to the next nodes.

  2. Filter out personal emails (No auth) — A Filter node that checks the invitee's email address. It passes the data forward only if the email does NOT contain common personal email domains: @gmail.com, @yahoo.com, @outlook.com, @hotmail.com, @icloud.com, @mail.com, @aol.com, @zoho.com, or @gmx. This ensures only business leads are processed.

  3. Enrich email (Clearbit — API Key auth) — Uses the Clearbit Person API to enrich the invitee's email address. It returns detailed person data including name, employment domain, company, and social profiles. The node is configured to continue on error (e.g., if the email is not found), so the workflow doesn't break.

  4. If person has a company (No auth) — An IF node that checks if the enriched person data contains a non-null employment.domain field. If a domain exists, the workflow proceeds to the company enrichment branch; otherwise, it goes to the "Upsert lead" branch to create a contact without a company association.

  5. Enrich company (Clearbit — API Key auth) — Uses the Clearbit Company API to enrich the company domain obtained from the person enrichment. It returns detailed company data: name, description, founded year, location, Twitter profile, employee count, and total money raised.

  6. Search company (HubSpot — OAuth2) — Searches HubSpot for an existing company by domain using the searchByDomain operation. It limits results to 1 and passes the found company ID (or empty) to the next node.

  7. If company does not exist on CRM (No auth) — An IF node that checks if the search result from HubSpot is empty. If the company does not exist, it routes to the "Create company" node; if it exists, it routes to the "Update company" node.

  8. Create company (HubSpot — OAuth2) — Creates a new company record in HubSpot using the enriched data from Clearbit. It maps fields like name, description, founded year, country, Twitter bio/handle/followers, employee count, and total money raised.

  9. Update company (HubSpot — OAuth2) — Updates an existing company record in HubSpot with the enriched Clearbit data. It uses the company ID from the search step and updates the same fields as the create step.

  10. Upsert contact (HubSpot — OAuth2) — Creates or updates a contact in HubSpot using the enriched email. It associates the contact with the newly created or updated company using the associatedCompanyId field.

  11. Upsert lead (HubSpot — OAuth2) — A fallback branch for contacts that do not have a company domain. It creates or updates a contact in HubSpot with the first and last name from Clearbit enrichment, but without a company association.

  12. Contact not found, do nothing (No auth) — A NoOp node that serves as an endpoint for cases where the email enrichment fails or the person has no company and no valid business email. It does nothing, effectively ending that branch gracefully.

  13. Error Handler (No auth) — A Stop and Error node that catches any unhandled errors and stops the workflow with a clear error message.

Setup Instructions

To use this workflow, you need accounts and API credentials for the following services:

  • Calendly: Create a Calendly account and connect it via the Calendly Trigger node. No API key is required — n8n handles the webhook automatically.
  • Clearbit: Sign up for a Clearbit account and generate an API key. Add it as a credential in n8n (type: Clearbit API).
  • HubSpot: Create a HubSpot account and generate OAuth2 credentials in n8n. Ensure the scopes include crm.objects.contacts.write, crm.objects.companies.write, and crm.objects.companies.read.

Once credentials are added, simply activate the workflow. The Calendly Trigger will automatically start listening for new event invitees.

Use Cases & Variations

  • Sales Lead Enrichment: Instantly enrich every booked demo or sales call with company data, so your sales team has context before the meeting.
  • Marketing Lead Scoring: Use the enriched data (employee count, funding, industry) to assign lead scores in HubSpot.
  • Custom CRM Integration: Replace HubSpot nodes with other CRM nodes (e.g., Salesforce, Pipedrive) to achieve the same enrichment pipeline.
  • Slack Notifications: Add a Slack node after enrichment to notify your team when a high-value lead books a meeting.
  • Email Validation: Add an email validation step (e.g., ZeroBounce) before enrichment to reduce bounces.
17 nodesmanual triggerSales
IFSticky NoteClearbitHubspotNo OpFilterStop And Error

Workflow JSON

{
  "meta": {
    "instanceId": "workflow-f9c393a5",
    "versionId": "1.0.0",
    "createdAt": "2025-09-29T07:07:42.259825",
    "updatedAt": "2025-09-29T07:07:42.259849",
    "owner": "n8n-user",
    "license": "MIT",
    "category": "automation",
    "status": "active",
    "priority": "high",
    "environment": "production"
  },
  "nodes": [
    {
      "id": "02cd5c16-de39-4e5c-acf8-fd3287662dfb",
      "name": "if company does not exist on CRM",
      "type": "n8n-nodes-base.if",
      "position": [
        2240,
        140
      ],
      "parameters": {
        "options": {},
        "conditions": {
          "options": {
            "leftValue": "",
            "caseSensitive": true,
            "typeValidation": "strict"
          },
          "combinator": "and",
          "conditions": [
            {
              "id": "19bf6d06-76f4-479a-a9d8-2157414190b3",
              "operator": {
                "type": "object",
                "operation": "empty",
                "singleValue": true
              },
              "leftValue": "={{ $input.item.json }}",
              "rightValue": ""
            }
          ]
        }
      },
      "typeVersion": 2,
      "notes": "This if node performs automated tasks as part of the workflow."
    },
    {
      "id": "c1325687-53cf-404f-9f9c-16696be0fcce",
// ... truncated (copy to see full JSON)

How to Import This Workflow

  1. 1Copy the workflow JSON above using the Copy Workflow JSON button.
  2. 2Open your n8n instance and go to Workflows.
  3. 3Click Import from JSON and paste the copied workflow.

Don't have an n8n instance? Start your free trial at n8nautomation.cloud

Related Templates

AI-Powered Competitor Price RAG Pipeline with Logging

Overview This workflow implements a Retrieval-Augmented Generation (RAG) pipeline for processing and analyzing competitor pricing data. It is triggered via a webhook (e.g., by an external scraper), splits incoming text into chunks, generates embeddings using OpenAI, stores them in a Supabase vector store, and then allows an Anthropic-powered AI agent to query that context. Results are appended to a Google Sheet for record-keeping, and any errors trigger a Slack alert to a designated channel. This setup is ideal for teams that need to automate the ingestion of structured or unstructured competitor data, enable natural language queries against that data, and maintain an audit log—all without manual intervention. Node-by-Node Breakdown Sticky Note — A visual note in the editor (not executed). Webhook Trigger (No auth) — Listens for incoming POST requests at the path . This is the entry point; an external service (e.g., a custom scraper) should send data here. Text Splitter (No auth) — Splits the incoming text into chunks of 400 characters with 40 character overlap. This ensures the embeddings are meaningful and context windows are manageable. Embeddings (API Key auth — OpenAI) — Uses the model to convert each text chunk into a vector embedding. Requires an OpenAI API key. Supabase Insert (API Key auth — Supabase) — Inserts the generated embeddings into the Supabase vector store under the index . This stores the data for future retrieval. Supabase Query (API Key auth — Supabase) — Queries the same Supabase vector index to retrieve relevant chunks based on a question or input from the agent. Vector Tool (No auth) — Wraps the Supabase query as a tool that the AI agent can call to fetch contextual data. Window Memory (No auth) — Provides conversational memory (buffer window) so the agent can maintain context across multiple interactions. Chat Model (API Key auth — Anthropic) — The language model that powers the AI agent. Uses Anthropic’s Claude model (selected via credentials). Requires an Anthropic API key. RAG Agent (No auth) — The core AI agent that receives the incoming data, uses the vector tool to retrieve relevant context, and generates a response using the chat model. The system message is set to "You are an assistant for Competitor Price Scraper". Append Sheet (OAuth2 — Google Sheets) — Appends the agent’s response (from the node) to a Google Sheet named . You must specify the Google Sheet ID and sheet name in the node parameters. Slack Alert (OAuth2 — Slack) — Triggered only on error from the RAG Agent. Sends a message to the channel with the error details. Setup Instructions Accounts & Credentials – You will need: - An OpenAI account (for embeddings). Create an API key and add it in n8n as an OpenAI credential. - An Anthropic account (for the chat model). Create an API key and add it as an Anthropic credential. - A Supabase project. Enable the pgvector extension, create a table for embeddings, and get the Supabase URL + anon/public API key. Add these as a Supabase credential in n8n. - A Google Cloud project with the Sheets API enabled. Generate OAuth2 credentials (or use a service account) and add them as a Google Sheets OAuth2 credential in n8n. - A Slack workspace. Create a Slack app with chat:write permission and install it to your workspace. Add the bot token as a Slack OAuth2 credential in n8n. Configure the Webhook – The webhook path is . You can change this as needed. Expose this endpoint (e.g., via n8n’s public URL or a tunnel) so your scraper can POST data to it. Set the Google Sheet ID and sheet name – In the Append Sheet node, replace with the actual ID of your Google Sheet and ensure the sheet is named (or update the parameter). Adjust Slack Channel – In the Slack Alert node, set the channel name (default ) to one that exists in your Slack workspace. Test the workflow – Send a sample POST request with some competitor price text to the webhook URL. Check the Google Sheet for logged responses and test error handling by sending malformed data. Use Cases & Variations Competitive Intelligence – Automate the ingestion of price lists, product descriptions, or news articles from competitors. Use the AI agent to answer questions like “Which competitor has the lowest price on product X?”. Document Q&A – Adapt this pipeline for any document type (PDFs, support tickets, internal memos). Replace the webhook with a file trigger and use the same RAG flow. Multi-Source Ingestion – Add an HTTP Request node before the Text Splitter to fetch data from an API or RSS feed instead of relying on a webhook. Custom Output – Instead of a Google Sheet, send the agent’s response via email, SMS, or directly into a CRM. Scheduled Runs – Swap the Webhook Trigger for a Schedule Trigger to run the ingestion on a regular basis (e.g., daily).

12 nodes

Extract Google Maps Business Leads via Dumpling AI to Google Sheets

Overview This workflow automates the extraction of business listings from Google Maps using Dumpling AI's search-maps API and logs the results into a structured Google Sheet. It's ideal for lead generation, market research, or competitive analysis — allowing you to quickly gather data like business names, ratings, addresses, phone numbers, websites, and booking links without manual browsing. Workflow Steps Trigger: Manual Test Run (Manual Trigger) — Starts the workflow on demand for testing. No authentication required. Search Google Maps via Dumpling AI (HTTP Request) — Sends a POST request to with a JSON body containing the search query (e.g., ) and language. Authentication uses Header Auth — you must provide a Dumpling AI API key as a header (configured in n8n credentials). The response returns an array of places with details like title, rating, address, phone, website, price level, and booking links. Split Places List for Processing (Split Out) — Splits the array from the HTTP response into individual items so each place can be processed separately. No authentication needed. Save Results to Google Sheet (Place Info) (Google Sheets) — Appends each place's data (name, address, rating, price level, type, website, phone, position, booking link) to a specified sheet in a Google Sheets document. Uses OAuth2 authentication (Google account). The sheet name is set to "Google Maps" and the document ID points to a spreadsheet named "Places". Setup Instructions Dumpling AI Account: Sign up at dumplingai.com and obtain an API key. In n8n, create a new Header Auth credential with the key name (e.g., ) and value . Google Sheets: Create a Google Sheet (or use the one referenced in the workflow). In n8n, create a Google Sheets OAuth2 credential by connecting your Google account. Ensure the sheet has a tab named "Google Maps" (or update the sheet name in the node). Customize Query: Edit the of the HTTP Request node to change the search query (e.g., ) or language. Run: Click "Execute Workflow" to test. The first run will prompt you to authorize Google Sheets access. Use Cases & Variations Lead Generation: Replace the query with industry-specific terms (e.g., "dentists in Los Angeles") to build a targeted prospect list. Competitor Analysis: Search for competitors in a niche and analyze their ratings, price levels, and online presence. Real Estate / Local Business Research: Extract data for multiple locations by chaining queries or using a loop. Automation: Replace the Manual Trigger with a Schedule Trigger to run daily/weekly, and add a Set node to dynamically pass queries from a spreadsheet or webhook. Enrichment: Add nodes to clean data, send notifications (Slack/Email), or integrate with a CRM like HubSpot.

5 nodes

Auto-Qualify Google Sheets Leads with OpenAI GPT-4

Overview This workflow automatically qualifies new leads submitted via Google Forms (or directly entered) into a Google Sheet. Using OpenAI's GPT-4, it evaluates each lead against custom criteria (e.g., decision-maker role, team size, email domain) and updates the sheet with a qualification rating and explanation. This saves manual review time and ensures consistent lead scoring for sales teams or community managers. Node-by-Node Breakdown Check for new entries (Google Sheets Trigger – OAuth2) - Listens for new rows added to a specific Google Sheet (connected to a Google Form or standalone). - Configured to poll every minute (adjustable). - Requires: A Google Sheet document ID and sheet name. Qualify leads with GPT (OpenAI – API Key auth) - Uses the chat model. - A system message defines qualification rules (decision-maker, team size, corporate email). - A user message injects the lead's name, email, business area, and team size from the trigger output. - Temperature set to 0.3 for consistent, deterministic responses. - Instructed to reply with a JSON object: . Extract JSON reply (Set Node – no auth) - Parses the from OpenAI's response using . - Stores the resulting object in a new field for downstream nodes. Merge (Merge Node – no auth) - Combines the original lead data (from the trigger) with the parsed GPT reply. - Uses “Combine” mode with “Merge by position” to join the two inputs horizontally. - Input 0 (from trigger) holds the row data; Input 1 (from Extract JSON reply) holds the GPT rating. Update lead status (Google Sheets – OAuth2) - Updates the same Google Sheet with the GPT's rating and explanation. - Matches rows by the column (to avoid updating the wrong row). - Writes the rating into a column (and optionally the explanation if you extend the schema). Setup Instructions Google Cloud / Sheets API - Create a Google Cloud project, enable the Google Sheets API, and create OAuth2 credentials (Desktop app or Web application). - In n8n, add a new Google Sheets credential (OAuth2) using your client ID and secret. OpenAI API Key - Sign up at OpenAI and create an API key. - In n8n, add a new OpenAI credential with your API key. Google Sheet - Use the provided template or create your own with columns: Timestamp, Email Address, Your name, Your business area, Your team size, Rating. - If using Google Forms, submissions will automatically populate the sheet. Configure the workflow - After importing, select each Google Sheets node and choose your credential and the correct sheet/document. - Adjust the polling interval if needed (default: every minute). - Modify the GPT system message to fit your own lead qualification criteria. Use Cases & Adaptations Sales lead scoring: Replace the criteria with your ICP (ideal customer profile) – e.g., industry, company size, budget. Community membership approval: Automatically accept or reject join requests based on responses. Event registration filtering: Qualify attendees for VIP access or follow-up. Extend output: Store the explanation in a separate column by adding it to the Update node's column mapping. Add notifications: Insert a Slack or email node after the Merge to alert your team when a high-quality lead is detected. Use a different model: Switch to for lower cost or for faster responses. This template is a starting point – tweak the prompt, polling frequency, and output columns to match your exact process.

9 nodes

Ready to automate with n8n?

Get affordable managed n8n hosting with 24/7 support.