Skip to main content

How to run an availability calendar in HubSpot | TabCalendar

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

This guide reflects current shipped behavior.

HubSpot can store dates. It’s less good at giving you a calm, shared view of availability across a year. This page lays out the native manual baseline, then the operational-utility path with TabCalendar.

TabCalendar is a CleverCat operational utility for HubSpot: a hosted fullscreen calendar (/calendar/fullscreen) for availability planning from Company/Deal context.

Fast answer

Native HubSpot baseline (manual)

  • Track availability with manual property updates on Company/Deal records.
  • Use notes and tasks for context and handoffs.
  • Reconcile sold / held / unavailable decisions manually.

When native is enough

Manual status tracking is enough for low-volume scheduling where cross-record visibility is limited but acceptable.

Where native breaks

  • Year-view context is hard to maintain by hand.
  • Status language drifts across teams (and across quarters).
  • Day-level actions live in multiple surfaces.

Operational utility path

Use TabCalendar when you need a year-at-a-glance availability calendar inside HubSpot, with explicit boundaries for rollout.

Why this is harder than it sounds

  • Availability planning is cross-date and cross-record, not a single field update.
  • Operational teams need consistent status semantics to avoid booking conflicts.
  • Manual coordination creates hidden scheduling risk over time.

What you’ll get (TabCalendar)

  • Hosted fullscreen calendar at /calendar/fullscreen, launched from HubSpot Company/Deal context.
  • Year / Month / Week / Day views over the same availability model.
  • Canonical status set: sold, held, unavailable.
  • Day-level actions for manual holds, plus creating deals and notes from a date (permission-dependent).
  • Optional read-only ICS subscription feeds (tokenized URLs; treat them like secrets).

Prerequisites

  • TabCalendar installed and configured for your HubSpot portal.
  • Access to the Company/Deal records you plan to use as context.
  • If you plan to create records from the calendar: permission to create Deals and Notes.

Boundaries and limitations

Does

  • Provide a hosted calendar surface for availability planning.
  • Keep the availability status contract explicit and documented.
  • Encourage test-slice validation before you roll it out broadly.

Does not

  • Replace portal-specific validation for your status mappings and permissions.
  • Act as a booking system (it’s a planning surface).
  • Protect ICS feed URLs beyond the token itself.

Validation slice checklist (before rollout)

  • Pick 1–2 Companies and a small set of Deals that represent real data.
  • Open the calendar from Company context and confirm the correct year loads.
  • Verify sold vs held behavior on a few known deals.
  • Create one manual hold, refresh, and confirm it persists.
  • Create a test Deal and a test Note from a date (if you plan to use those actions).
  • If you use ICS: generate a feed, subscribe in a calendar client, and confirm scope/filters match what you intended.

Support-intake checklist

When contacting CleverCat support, include:

  • HubSpot portal ID.
  • Company ID (and Deal ID if deal-scoped).
  • Steps to reproduce + expected vs actual.
  • Screenshot of the calendar state and any error message.
  • If ICS is involved: share the feed URL privately (it’s effectively a secret).
  • Approximate timestamp + your timezone.

Fallback: validate behavior in a narrow test slice, then use Known limitations and Support.

Next steps

FAQ

Does TabCalendar show a full year view?

Yes. TabCalendar supports Year / Month / Week / Day view modes.

Which status states are supported?

sold, held, and unavailable.

Can teams create actions from a specific day?

Yes. Day-level actions include manual holds plus deal and note create flows (permission-dependent).

Does TabCalendar support an ICS subscription feed?

Yes, when enabled. TabCalendar can generate tokenized, read-only ICS subscription feeds; treat subscription URLs as secrets.

Which record contexts are supported?

Company and Deal context (as documented in the TabCalendar docs).

Where should rollout teams start?

Start with setup docs and limitations before broader deployment.