Skip to content

Commit 4991436

Browse files
authored
Merge pull request #5277 from segmentio/sneha-shashidhar-patch-4
Update index.md
2 parents 6833dab + 47c5a09 commit 4991436

File tree

1 file changed

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

1 file changed

+1
-1
lines changed

src/connections/sources/catalog/cloud-apps/hubspot/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Voila! We'll begin syncing your HubSpot data into Segment momentarily, and it wi
2727

2828
### Sync
2929

30-
The HubSpot source is built with a sync component, which means we'll make requests to their API on your behalf on a 3 hour interval to pull the latest data into Segment. In the initial sync, we'll grab all the HubSpot objects (and their corresponding properties) according to the Collections Table below. The objects will be written into a separate schema, corresponding to the source instance's schema name you designated upon creation (ie. my_source.charges).
30+
The HubSpot source is built with a sync component, which means Segment makes requests to their API on your behalf on a three hour interval to pull nearly all data into Segment. In the initial sync, Segment will grab all the HubSpot objects (and their corresponding properties) according to the Collections Table below. The objects will be written into a separate schema, corresponding to the source instance's schema name you designated upon creation (for example, `my_source.charges`).
3131

3232
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`.
3333

0 commit comments

Comments
 (0)