Skip to content

Commit d300a20

Browse files
sade-wusiforstisabella
andauthoredMar 19, 2025··
Update src/connections/sources/catalog/cloud-apps/hubspot/index.md
Co-authored-by: forstisabella <[email protected]>
1 parent 22a5c61 commit d300a20

File tree

1 file changed

+1
-1
lines changed
  • src/connections/sources/catalog/cloud-apps/hubspot

1 file changed

+1
-1
lines changed
 

Diff for: ‎src/connections/sources/catalog/cloud-apps/hubspot/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The HubSpot source is built with a sync component, which means Segment makes req
3333

3434
Our sync component uses an upsert API, so the data in your warehouse loaded using sync will reflect the latest state of the corresponding resource in HubSpot. For example, if `deals` goes from `open` to `closed` between syncs, on its next sync that deal's status will be `closed`.
3535

36-
The source syncs and warehouse syncs are independent processes. Source runs pull your data into the Segment Hub, and warehouse runs flush that data to your warehouse. You can set the start date of the first sync and sources will sync with Segment every 3 hours. Depending on your Warehouses plan, we will push the Source data to your warehouse on the interval associated with your billing plan.
36+
The source syncs and warehouse syncs are independent processes. Source runs pull your data into the Segment Hub, and warehouse runs flush that data to your warehouse. You can set the start date of the first sync. After the first sync, sources sync with Segment every 3 hours. Depending on your Warehouses plan, Segment pushes the Source data to your warehouse on the interval associated with your billing plan.
3737

3838

3939
## Collections

0 commit comments

Comments
 (0)