[source-hubspot] Add leads_property_history and tickets_property_history streams

[CraigAtRocketOps (CraigAtRocketOps)]

Airbyte HubSpot: Request for leads_property_history and tickets_property_history

Post to: Airbyte Discussions - Connector Ideas and Features

---

Title

[source-hubspot] Add leads_property_history and tickets_property_history streams

---

Body

Summary

The HubSpot source connector exposes property history for contacts, companies, and deals, but not for leads or tickets. HubSpot's API supports property history for both objects, so this is a connector gap rather than an API limitation.

Why This Matters

Leads and tickets are core objects for funnel and journey analytics. Without property history, stage changes can only be inferred from snapshots, which causes:

1. Inception problem – On first sync, all existing records get change timestamps equal to the sync date instead of real historical dates.
2. Inaccurate funnel metrics – Stage velocity, conversion rates, and time-in-stage are wrong when entry dates are wrong.
3. Broken time-series analytics – Any analysis that depends on when properties actually changed (e.g. stage transitions) is unreliable.

HubSpot API Support

The HubSpot CRM API supports propertiesWithHistory for leads and tickets:

• Leads: CRM API | Leads – propertiesWithHistory in GET and batch read
• Tickets: CRM API | Tickets – same pattern

This matches the pattern used for contacts, companies, and deals, which already have property history streams.

Requested Streams

Stream	HubSpot Object	Key Property for Stage	API Support
leads_property_history	Leads	hs_lead_label (stage)	✅ propertiesWithHistory
tickets_property_history	Tickets	hs_pipeline_stage (stage)	✅ propertiesWithHistory

Implementation Path

The connector already has contacts_property_history, companies_property_history, and deals_property_history. Adding leads_property_history and tickets_property_history would follow the same pattern, using the existing property history logic and HubSpot batch read with propertiesWithHistory.

Suggested Scopes

• crm.objects.leads.read for leads
• tickets scope for tickets (already used by the tickets stream)