Connector
HubSpot as a pipeline source
HubSpot's daily API call limit drives the pipeline cost question more than the pipeline tool does. Confirm batched-object reads, not per-record polling - the difference between 5 calls and 5,000 calls per sync is the same data, but it eats the daily limit.source - pulled 2026-06-21
Coverage by vendor
| Vendor | Status | Note |
|---|---|---|
| Fivetran | Native (batched) | Respects daily API quota; configurable schemas |
| Airbyte | Native (batched) | OSS + Cloud; verify object coverage matches your portal |
| Stitch | Native | Stable; predictable row-tier billing |
| Hevo | Native | Event-priced; webhook integration for low-latency syncs |
| Census | Native destination | Reverse-ETL: warehouse → HubSpot |
| Estuary | Native | Real-time via webhooks |
HubSpot in detail
HubSpot exposes contacts, companies, deals, tickets, custom objects, and engagements. Batched-object reads pull thousands of records per call; per-record polling pulls one per call. Vendors differ on which mode they use; ask before signing.
For marketing-attribution workloads, hourly sync is the realistic default. Webhooks via Hevo or Estuary push closer to real-time but require HubSpot Marketing Hub Enterprise for some event types.
Related
Written by Oliver Wakefield-Smith, Founder of Digital Signet. Independent reference, no vendor sponsorship.
Sources logged at /sources. Pricing-change history at /changelog. Last reviewed 2026-06-21.