When someone books a meeting, the system captures their email, enriches the details, and sends clean records into your CRM. Sales teams get full company profiles and ready to work leads without manual research. It suits teams that rely on online bookings for demos or consultations.

An event from Calendly starts the flow. Personal email domains like gmail and yahoo are filtered out to skip low value records. Clearbit looks up the person and finds the company domain, then a company enrichment step collects firmographic details. HubSpot is searched for a matching company. If no match is found, a new company is created with description, location, year founded, and social bios. If a match exists, the profile is updated. A lead is upserted and a contact is added and linked when a new company is created.

Set up credentials for Calendly, Clearbit, and HubSpot, and map the email field from your booking data. Expect faster handoffs, less manual entry, and fewer errors on every meeting. This is ideal for SDR intake, partner calls, and inbound meetings that must be in the CRM before the call.

• Calendly event trigger starts the process as soon as a meeting is booked.
• Personal email filter removes free domains to focus on business leads.
• Email enrichment pulls name, role, and company domain from Clearbit.
• Company enrichment uses the domain to fetch firmographic details like description, location, and year founded.
• HubSpot company search checks if the account already exists before making changes.
• Conditional logic creates a new company or updates the existing one with mapped fields, including social bios.
• Lead upsert in HubSpot records the opportunity from the booking.
• Contact upsert adds the person and links them to the newly created company when available.

• Reduce manual research from 30 minutes to 2 minutes per booking
• Cut junk leads by 60 percent by filtering personal emails
• Improve company data accuracy by 90 percent with enrichment
• Handle 5 times more meeting intake without extra headcount
• Connect Calendly, Clearbit, and HubSpot in one flow

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Calendly, Clearbit and HubSpot. See the Tools Required section above for links to create accounts with these services.
3. Open the Calendly Trigger node, click the Credential dropdown, choose Create new credential, and follow the on screen steps to connect your Calendly account. Use your personal access token if prompted.
4. Open the Enrich email node, create a Clearbit credential using your API key from the Clearbit dashboard, and save it with a clear name like Clearbit Prod.
5. Open any HubSpot node, create a new HubSpot OAuth2 credential, and complete the sign in flow. Name it HubSpot Prod and reuse it across all HubSpot nodes.
6. In Calendly Trigger, select the event types you want to listen to and enable the webhook. Use Test workflow in n8n to register it.
7. In Filter out personal emails, review the domain list and add any domains your team wants to exclude.
8. In Enrich email, map the email field from the Calendly payload so the enrichment has a valid business email.
9. In If person has a company, set the check so it only passes when a company domain exists in the enrichment result.
10. In Enrich company, confirm the domain field uses the value from employment.domain so company data can be fetched.
11. In Search company, search by the domain or website field in HubSpot to find an existing company.
12. In the If company does not exist on CRM node, keep the condition that routes to Create company when no match is found and to Update company when a match exists.
13. In Create company and Update company, review mapped fields like description, geo, founded year, and social bios. In Upsert contact, map the email and associate the companyId from the create step.
14. Click Test workflow, book a test meeting in Calendly, then verify the company, lead, and contact in HubSpot. If nothing appears, recheck credentials, confirm the email is not filtered, and review n8n execution logs for errors.