The HubSpot source is built with a sync component, which meanswe'll make requests to their API on your behalf on a3 hour interval to pullthe latest data into Segment. In the initial sync,we'llgrab 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).

The HubSpot source is built with a sync component, which meansSegment makes requests to their API on your behalf on athree hour interval to pullnearly all data into Segment. In the initial sync,Segment willgrab 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`).

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