Cal.com and HubSpot integration: full setup walkthrough for 2026

How the Cal.com + HubSpot Integration Works

Cal.com connects to HubSpot natively via OAuth and syncs booking data in one direction: from Cal.com into HubSpot. When someone books a meeting through your Cal.com link, HubSpot automatically creates or updates a contact and logs a meeting activity. The sync completes within 60 seconds of booking confirmation, with no middleware required on either platform's paid tiers.

The data flow is straightforward. Cal.com captures the attendee's name, email, booking time, and event type. It pushes those into HubSpot as a Contact object, creating a new record or merging with an existing one by email, and attaches a Meeting activity to that contact's timeline. Reschedules and cancellations push updates too, so your CRM reflects what actually happened, not just what was originally booked.

One gap teams regularly miss: this integration doesn't create HubSpot Deals automatically. If you need a booking to populate a deal pipeline stage, you'll need a HubSpot workflow on top of the contact creation. That's not a Cal.com shortcoming; it's just how HubSpot's object model is structured.

How to Set Up Cal.com + HubSpot in 6 Steps

The setup requires no code and takes under 15 minutes. You need Admin access in Cal.com and at least HubSpot Sales Hub Starter. Free HubSpot accounts don't have the API scopes this integration requires, and there's no workaround for that at the free tier.

1. Go to Cal.com Settings, then Integrations, then CRM. HubSpot appears near the top of the connector list. If you don't see the CRM tab, you're likely on Cal.com's free plan, which doesn't include native CRM connectors.
2. Click Connect next to HubSpot. An OAuth consent screen opens. You'll be redirected to HubSpot to authorize Cal.com's access to your portal.
3. Authorize the correct HubSpot portal. If you manage multiple portals, double-check you're connecting the production account, not a sandbox. The OAuth flow doesn't warn you if you pick the wrong one, and debugging a broken sync against the wrong portal wastes 30-60 minutes.
4. Select which Cal.com event types to sync. You'll see a toggle per event type. Only check the ones that belong in your CRM. Toggling everything creates noise in your contact timelines and makes your HubSpot activity feed harder to read.
5. Map custom fields if your booking forms include intake questions. Cal.com can push booking form answers to HubSpot contact properties. Create the custom properties in HubSpot first, then come back to Cal.com's integration settings to map them. This order matters; mapping to a nonexistent property silently fails.
6. Test with a real booking using your own email. Confirm a contact appears in HubSpot within 60 seconds and a meeting activity is attached to the contact record. If it doesn't show up, see the troubleshooting section below before touching anything else.

What Syncs Between Cal.com and HubSpot

Cal.com pushes seven data points into HubSpot out of the box. Anything beyond that requires custom property mapping configured before bookings arrive, since existing bookings don't backfill. Knowing what's automatic versus what needs setup prevents the most common support escalation on both platforms.

HubSpot doesn't write anything back to Cal.com. This is strictly one-way. For two-way sync, such as blocking Cal.com availability based on HubSpot deal stage, you'd need a custom API build or a dedicated scheduling middleware tool like Zapier with both a trigger and an action configured in each direction.

Troubleshooting Cal.com + HubSpot Setup Failures

Three issues cause roughly 80% of broken Cal.com + HubSpot integrations: the wrong HubSpot plan, missing OAuth scopes, and email-based deduplication mismatches. Start here before you file a support ticket with either platform.

• Bookings not appearing in HubSpot at all. Almost always an OAuth scope problem. In HubSpot, go to Settings, then Integrations, then Connected Apps. Find Cal.com and confirm it has "contacts.write" and "timeline.write" permissions. If either is missing, disconnect and reconnect Cal.com to trigger a fresh authorization with the correct scopes.
• Duplicate contacts created instead of merging. Cal.com matches contacts by exact email address. If the booking email differs from the existing HubSpot contact's email even by capitalization or an alias, Cal.com creates a new record. HubSpot's automatic deduplication runs daily, not in real time. Normalize email formats upstream to prevent this at the source.
• Custom field answers not syncing. The HubSpot custom property must exist before you map it in Cal.com. Mapping to a property that hasn't been created yet silently fails with no error message. Create the property in HubSpot, then return to Cal.com's integration settings to set the mapping. Previous bookings won't backfill; only future bookings will include the data.
• OAuth token expiring without warning. HubSpot OAuth tokens expire after 90 days of inactivity. If your Cal.com portal goes quiet over a period, the sync fails the next time a booking comes in, with no obvious error surfaced to the booker. Re-authenticate in Cal.com Settings → Integrations → CRM to refresh the connection if you suspect this.
• Meeting activity logged but no contact created. This happens when the attendee's email domain is on HubSpot's blocked domain list, a common setting for teams filtering out personal email noise. Check HubSpot Settings → Marketing → Email → Blocked Domains and remove the affected domain if it's blocking legitimate prospects.

Three Use Cases That Justify the Setup Time

Cal.com booking data alone isn't particularly valuable sitting in a contact record. The value comes when HubSpot workflows fire on that booking trigger and automate what your team would otherwise do manually after every call. Here are three setups that run in production at B2B teams right now.

Automatic lead routing by company size. When a contact books a 30-minute demo, a HubSpot workflow checks company headcount from enrichment data. If the company has 50+ employees, the contact routes to a senior AE and a Slack notification fires. Teams using this setup report cutting average handoff time from 2-4 hours down to under 5 minutes, per internal GTM ops feedback.

No-show recovery sequences. When a meeting gets cancelled or marked as a no-show via Cal.com status update, a workflow re-enrolls the contact into a 3-email follow-up sequence. Recovery rates of 20-30% on no-shows are achievable when this runs consistently, based on data from outbound programs we've managed.

Automatic deal creation at booking. A HubSpot workflow creates a new Deal at "Demo Scheduled" stage the moment a Cal.com booking syncs. After the meeting, a manual stage update or follow-up form moves it forward. Your pipeline view stays accurate without AEs touching their deals after every call.

Which Plans Support the Cal.com + HubSpot Integration?

The native connector requires Cal.com Teams ($12/user/month, billed annually) and at least HubSpot Sales Hub Starter ($20/month). Combined cost for a solo user is $32-50/month, which is less than a single hour of developer time to build the equivalent workflow manually via API.

If you're on Cal.com's free plan and won't upgrade, Zapier's Cal.com + HubSpot template works as a stopgap. But Zapier adds a third platform, a separate bill, and another authentication token to maintain. For teams booking more than 20 meetings a month, the native connector is cheaper and more reliable over time.

Want Research-Led Outreach Run For You?

Modern Inbound mines buyer language, builds account lists, writes outreach, manages client-owned inboxes, and routes qualified replies. Your team gets sales conversations, not another tool to operate.

Frequently Asked Questions

Does Cal.com have a native HubSpot integration?

Yes, on the Teams plan and above. It connects via OAuth and creates or updates HubSpot contacts automatically on every booking. No Zapier required.

Which HubSpot plan is required?

At least Sales Hub Starter ($20/month). Free HubSpot accounts don't have the API scopes the Cal.com connector needs.

Is the sync two-way?

No. Data flows from Cal.com to HubSpot only. Two-way sync needs a custom API build.

Why aren't bookings appearing in HubSpot?

Almost always a missing OAuth scope. Reconnect Cal.com under HubSpot's Connected Apps settings to refresh the authorization.

Getting Started

The Cal.com + HubSpot integration is one of the cleaner scheduling-to-CRM connections available without a developer. Set aside 15 minutes, test with a real booking before you rely on it in production, and build at least one HubSpot workflow on top of the booking trigger to make the data useful.

If your outbound motion needs more than scheduling automation, that's what Modern Inbound handles: cold email infrastructure, account lists, copywriting, and meeting routing, all managed. Talk to us about your pipeline targets.