Quickstart · Source connector
HubSpot ELT Connector
Extract brings HubSpot quickstart data into data warehouses and databases for analysis with the rest of your business data. Teams use it to build recurring reporting and compare business activity across systems. Flexible scheduling keeps reporting current for routine analysis and time-sensitive decisions.
View setup guide
Use cases
What teams use this connector for
Business performance reporting
Use HubSpot data to monitor recurring activity and investigate meaningful changes over time.
Cross-system analysis
Combine HubSpot data with customer, finance, and operational metrics for consistent reporting.
Data quality monitoring
Compare HubSpot record totals and reporting periods to identify incomplete or unexpected data.
Flexible reporting cadence
Refresh HubSpot reporting every 15 minutes, hourly, daily, or on a custom schedule as business needs change.
Warehouse and database analysis
Use Extract to make HubSpot quickstart data available in data warehouses and databases such as Snowflake, BigQuery, Redshift, and PostgreSQL for governed analysis.
Connector data
Available streams
| Stream | Description | Sync mode |
|---|---|---|
campaign | Fields include hs_object_id, campaign_guid, created_at, hs_audience. | Incremental |
owner_team | Fields include id, owner_id, name. | Full refresh |
owner | Fields include id, archived, created_at, email. | Full refresh |
campaign_asset | Fields include campaign_guid, id, asset_type, name. | Incremental |
deal_pipeline | Fields include id, created_at, display_order, label. | Full refresh |
deal_pipeline_stages | Fields include deal_pipeline_id, id, archived, created_at. | Full refresh |
Schema
Data model at a glance
campaign
hs_object_idstringcampaign_guidstringcreated_atstringhs_audiencestringhs_budget_items_sum_amountnumberhs_campaign_statusstringhs_color_hexstringhs_created_by_user_idstring
owner_team
idstringowner_idstringnamestring
owner
idstringarchivedbooleancreated_atstringemailstringfirst_namestringlast_namestringtypestringupdated_atstring
campaign_asset
campaign_guidstringidstringasset_typestringnamestring
deal_pipeline
idstringcreated_atstringdisplay_orderintegerlabelstringupdated_atstring
deal_pipeline_stages
deal_pipeline_idstringidstringarchivedbooleancreated_atstringdisplay_orderintegerlabelstringmetadata.is_closedbooleanmetadata.probabilitynumber
No verified relationships are available in this schema preview.
Connector pairings
Popular destinations
Commonly paired with HubSpot in Extract workflows.
Why Extract
Why Extract for HubSpot
- Rust-native performanceUse Rust-native data movement to refresh HubSpot reporting every 15 minutes, hourly, daily, or on a custom schedule as volume grows.
- Full run transparencyInspect HubSpot API activity, execution steps, and timing in Extract's run-level logs when data needs review.
- ELT + Reverse ETL in oneCombine HubSpot data with customer and finance models, then send approved outputs through a separately configured Reverse ETL destination.
FAQ
Frequently asked questions
How does Extract handle incremental and full HubSpot syncs?
An incremental sync processes only new or changed data since a stored checkpoint or new date partition, while a full sync processes the complete selected dataset or date range again. By avoiding repeated processing and writes for the full dataset, incremental syncs can reduce destination database updates and warehouse compute costs. Stream schemas define full refresh, incremental changes, partition-based extraction. Behavior varies by stream and configuration. Extract records run details so teams can verify each sync.
Can I backfill historical HubSpot data with Extract?
Historical coverage for HubSpot: No connector-specific backfill parameter is exposed. Initial historical coverage depends on the stream and provider. Use the setup guide and run details to confirm the available source records and selected settings.
How can teams monitor HubSpot data quality and freshness?
Compare expected reporting periods and record totals in your models, then use Extract's run-level logs to inspect HubSpot API activity, execution steps, and timing. This helps teams distinguish a source-data delay from a failed or incomplete run.
How often can Extract sync data from HubSpot?
Extract supports schedules every 15 minutes, hourly, daily, or on a custom cadence. Teams can choose a frequency that matches routine reporting, time-sensitive monitoring, or operational activation needs.
What does the HubSpot data model look like in the destination?
The Available streams table describes the datasets Extract can read from HubSpot. The inline schema previews entities and fields. Only relationships verified from the exported schema are shown. Use the full schema link for more details.