Skip to content

Commit d89cc57

Browse files
authored
Merge pull request #7523 from segmentio/hubspot-source-cherry-pick
HubSpot Source Collections/Syncs one off
2 parents 06d3d75 + d7eeb85 commit d89cc57

File tree

1 file changed

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

1 file changed

+5
-3
lines changed

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

+5-3
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,9 @@ Are you trying to set up HubSpot as a destination to receive data from Segment?
1818

1919
**Note**: You can add multiple instances if you have multiple HubSpot accounts. That's why we allow you to customize the source's nickname and schema name!
2020

21-
4. Finally, connect an account with **admin API permissions** to access your HubSpot data. This account should be an active user on a Professional or Enterprise plan. Check out [HubSpot's docs on how to get your API Key](http://knowledge.hubspot.com/articles/kcs_article/integrations/how-do-i-get-my-hubspot-api-key){:target="_blank"}.
21+
4. Configure the Selective Sync settings. You can specify a start date for the initial sync, adjust the default sync frequency, and select which collections to sync.
22+
23+
5. Connect an account with **admin API permissions** to access your HubSpot data. This account should be an active user on a Professional or Enterprise plan. Check out [HubSpot's docs on how to get your API Key](http://knowledge.hubspot.com/articles/kcs_article/integrations/how-do-i-get-my-hubspot-api-key){:target="_blank"}.
2224

2325
Voila! We'll begin syncing your HubSpot data into Segment momentarily, and it will be written to your warehouse at your next Warehouse run.
2426

@@ -31,12 +33,12 @@ The HubSpot source is built with a sync component, which means Segment makes req
3133

3234
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`.
3335

34-
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. 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.
3537

3638

3739
## Collections
3840

39-
Collections are the groupings of resources we pull from your source. In your warehouse, each collection gets its own table.
41+
Collections are the groupings of resources we pull from your source. You can select which collections are included in your sync. In your warehouse, each collection gets its own table.
4042

4143
### Event History
4244

0 commit comments

Comments
 (0)