Skip to main content

How to overlay Google Calendar availability in HubSpot | TabCalendar

Last updated: February 23, 2026 (America/Los_Angeles)

This guide reflects current shipped behavior.

External calendars are where “unavailable” usually lives. HubSpot usually isn’t invited. This page covers the manual baseline, then TabCalendar’s read-only Google overlay path.

TabCalendar is a CleverCat operational utility for HubSpot. The Google integration is intentionally one-way: import overlays for planning, not bidirectional sync.

Fast answer

Native HubSpot baseline (manual)

  • Review Google events and HubSpot records separately.
  • Manually mirror unavailable dates into HubSpot fields/processes.
  • Re-check date conflicts during scheduling operations.

When native is enough

Manual overlay is enough when calendars are low volume and teams accept manual reconciliation.

Where native breaks

  • Unavailable-date visibility can drift between systems.
  • Recurring events become a maintenance project.
  • Booking teams lose confidence when overlays are inconsistent.

Operational utility path

Use TabCalendar when you want Google Calendar events imported as unavailable overlays in HubSpot planning context.

Why this is harder than it sounds

  • Availability overlays are a synchronization and interpretation problem, not just a field copy.
  • Recurring events require day-level expansion to be operationally useful.
  • Manual reconciliation introduces preventable scheduling errors.

What you’ll get (TabCalendar)

  • Hosted fullscreen calendar (/calendar/fullscreen) for availability planning.
  • Google Calendar import that maps events to unavailable overlays (read-only).
  • Recurring events are fetched as individual occurrences within the sync window (so recurring blocks actually block dates).
  • Overlays render alongside HubSpot-derived sold / held layers.
  • Optional read-only ICS subscription feeds (tokenized URLs; treat them like secrets).

Prerequisites

  • TabCalendar installed and configured for your portal.
  • Google import enabled in TabCalendar settings.
  • Google OAuth connected and at least one calendar mapped for the Company you’re validating.
  • A sync run (manual or scheduled) to populate overlays.

Boundaries and limitations

Does

  • Provide imported unavailable overlays for planning context.
  • Keep integration posture explicit (import-only).

Does not

  • Write events back to Google.
  • Claim real-time presence; overlay freshness depends on your sync cadence and portal settings.
  • Replace portal-specific validation for mappings, timezone, and calendar selection.

Validation slice checklist (before rollout)

  • Pick one test Company and map a single Google calendar.
  • Run a manual sync and confirm overlays appear as unavailable.
  • Create a recurring test event, sync, and confirm multiple dates block.
  • Edit or delete the test event, sync again, and confirm overlays update as expected.
  • Confirm overlays don’t mutate sold/held deal data (they’re an overlay layer).

Support-intake checklist

When contacting CleverCat support, include:

  • HubSpot portal ID + Company ID.
  • Which Google account is connected and which calendar IDs are mapped.
  • Whether sync is manual or scheduled + approximate sync time.
  • Example event (title/date range; note if recurring).
  • Screenshot of the External mapping panel and the calendar view.
  • Any error message/request ID shown by the app.

Fallback: validate import behavior on a test slice and use Known limitations for scope decisions.

Next steps

FAQ

Does TabCalendar import Google events as unavailable overlays?

Yes. That is the current integration claim.

Are recurring events supported in overlay imports?

Yes. Recurring events are fetched as individual occurrences within the sync window.

Does this provide two-way sync with Google Calendar?

No. Current behavior is import-focused for unavailable overlays.

Do overlays appear with sold and held statuses?

Yes. Imported unavailable overlays are displayed with other availability states.

What is the current TabCalendar release posture?

This guide reflects current shipped behavior. Validate in your portal before broad rollout.

Where should teams start implementation?

Start with setup docs, validate mappings in a test slice, then expand deliberately.