# HubSpot (v4)
Information note **HubSpot extraction is supported by Stitch**
This integration is powered by [Singer's](https://www.singer.io/) HubSpot tap and certified by Stitch. [Check out and contribute to the repo on GitHub](https://github.com/singer-io/tap-hubspot).
For support, contact [Support](https://community.qlik.com/t5/Support/ct-p/qlikSupport).
## HubSpot integration summary
Stitch’s HubSpot integration replicates data using the [HubSpot REST API](https://developers.hubspot.com/docs/overview). Refer to the [Schema](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#schema) section for a list of objects available for replication.
## HubSpot feature snapshot
A high-level look at Stitch's HubSpot (v4) integration, including release status, useful links, and the features supported in Stitch.
| **STITCH** | | | |
| --- | --- | --- | --- |
| **[Release status](https://help.qlik.com/en-US/stitch/integrations/identify-an-integration-version)** | Released on September 9, 2025 | **Supported by**
the Info icon
Indicates if the integration is supported by Stitch or the Singer community. | [Stitch](https://community.qlik.com/t5/Support/ct-p/qlikSupport) |
| **Stitch plan**
the Info icon
The type of Stitch plan required to use the integration. | Standard | **[API availability](https://help.qlik.com/en-US/stitch/developers/stitch-connect/guides/source-destination-reference)**
the Info icon
Indicates if the integration is available as a source in Stitch Connect. | the Success icon
This version of the integration is available via the API.
Indicates if Replication Methods can be defined by you for tables in the integration. | the Remove icon
Configurable Replication Methods are not supported for this integration. Stitch will use pre-defined replication methods for tables you set to replicate.
The ability to select individual tables for replication in the Stitch interface. If table selection is unavailable, all tables and all the columns they contain will be set to replicate by default. | the Success icon
This feature is supported for this version of the integration.
Supported | **Column selection**
the Info icon
The ability to select individual columns for replication in the Stitch interface. If column selection is unavailable, all columns will be set to replicate by default. | the Success icon
This feature is supported for this version of the integration.
Supported |
| **Select all**
the Info icon
Indicates if the integration supports selecting all available tables and columns. | the Success icon
Reports detailing the Loading phase of the replication process for a given integration. Includes the number of rows loaded for each table and error info, should an error occur. | the Success icon
This feature is supported for this version of the integration.
Supported |
## Connecting HubSpot
### HubSpot setup requirements
To set up HubSpot in Stitch, you need:
* **For HubSpot CRM or Marketing products:** Administrator permissions in HubSpot. **Note**: To replicate [email events](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#email_events), you’ll need to have **Super Admin** permissions in HubSpot.
* **For the HubSpot Sales product:** Sales Administrator permissions in HubSpot.
More information about HubSpot user roles and permissions can be found in [HubSpot’s documentation](https://knowledge.hubspot.com/articles/kcs_article/settings/hubspot-user-roles-guide).
### Step 1: Add HubSpot as a Stitch data source
1. [Sign into your Stitch account](https://app.stitchdata.com/).
2. On the Stitch Dashboard page, click the **Add Integration** button.
3. Click the **HubSpot** icon.
4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch HubSpot” would create a schema called `stitch_hubspot` in the destination. **Note**: Schema names cannot be changed after you save the integration.
### Step 2: Define the historical replication start date
The Sync Historical Data setting defines the starting date for your HubSpot integration. This means that data **equal to or newer than this date** will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond HubSpot’s default setting of **30 days**. For a detailed look at historical replication jobs, check out the [Syncing Historical SaaS Data](https://help.qlik.com/en-US/stitch/replication/syncing-historical-saas-data-resetting-replication-keys) guide.
### Step 3: Create a replication schedule
Information note Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the [Replication Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling) documentation for more information.
In the **Replication Frequency** section, you’ll create the integration’s [replication schedule](https://help.qlik.com/en-US/stitch/replication/replication-scheduling). An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
HubSpot integrations support the following replication scheduling methods:
* [Replication Frequency](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/replication-frequency)
* [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)
* [Advanced Scheduling using Cron](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling) (Advanced or Premium plans only)
To keep your row usage low, consider setting the integration to replicate less frequently. See the [Understanding and Reducing Your Row Usage guide](https://help.qlik.com/en-US/stitch/getting-started/understanding-stitch-usage) for tips on reducing your usage.
### Step 4: Authorize Stitch to access HubSpot
1. Next, you’ll be prompted to sign into your HubSpot account.
2. After you log into HubSpot, a screen with a list of your HubSpot accounts will display. Click the account you want to connect to Stitch.
**Note that Stitch will only ever read your data**. Stitch will never modify or delete any data in your HubSpot account.
3. After the authorization process is successfully completed, you’ll be directed back to Stitch.
4. Click **All Done**.
### Step 5: Set objects to replicate
Information note **Is an object missing or not replicating?** Verify that the object meets the requirements for [selection](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#selection-requirements) and [replication](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#replication-requirements).
The last step is to select the tables and columns you want to replicate. [Learn about the available tables for this integration.](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#schema)
**Note**: If a replication job is currently in progress, new selections won’t be used until the next job starts.
* Selection options
* Individual tables and columns
* All tables and columns
For HubSpot integrations, you can select:
1. **Individual tables and columns**
2. **All tables and columns**
Click the tabs to view instructions for each selection method.
1. In the integration’s **Tables to Replicate tab**, locate a table you want to replicate.
2. To track a table, click the **checkbox** next to the table’s name. A blue checkmark means the table is set to replicate.
3. To track a column, click the **checkbox** next to the column’s name. A blue checkmark means the column is set to replicate.
4. Repeat this process for all the tables and columns you want to replicate.
5. When finished, click the **Finalize Your Selections** button at the bottom of the screen to save your selections.
Information note **Important**: Using the **Select All** feature will overwrite any previous selections. However, selections aren’t final until **Finalize Your Selections** is clicked. Clicking **Cancel** will restore your previous selections. Refer to the [Select All guide](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#set-all-data-to-replicate) for more info about this feature.
1. Click into the integration from the Stitch Dashboard page.
2. Click the **Tables to Replicate** tab.
3. In the list of tables, click the box next to the **Table Names** column.
4. In the menu that displays, click **Track all Tables and Fields**:
The Track all Tables and Fields menu in the Tables to Replicate tabThe Track all Tables and Fields menu in the Tables to Replicate tab
5. Click the **Finalize Your Selections** button at the bottom of the page to save your data selections.
### Initial and historical replication jobs
After you finish setting up HubSpot, its **Sync Status** may show as **Pending** on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a **Pending** status indicates that Stitch is in the process of scheduling the initial replication job for the integration. **This may take some time to complete.**
Information note
**Initial replication jobs with Anchor Scheduling**
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling#job-scheduling-and-anchor-times) documentation for more information.
#### Free historical data loads
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
Information note **Replication will continue after the seven days are over**. If you’re no longer interested in this source, be sure to **pause** or **delete** the integration to prevent unwanted usage.
## Removing the HubSpot integration
To completely disconnect Stitch from your HubSpot account, you need to delete the integration from Stitch, and uninstall the Stitch app from HubSpot.
Disconnecting HubSpot from Stitch will stop the replication of HubSpot data to your Stitch destination. There will be no impact to the HubSpot data, as Stitch is a read-only integration with HubSpot. All data that has already replicated to your Stitch destination will be maintained and under your control.
### Step 1: Deleting your HubSpot integration
To delete your HubSpot integration from your Stitch account:
1. Log in to your Stitch account and open the **Integrations** tab.
2. Click your HubSpot integration and click **Settings**.
3. Scroll down to the bottom of the page and click **Delete**.
4. Click **Delete** to confirm.
### Step 2: Uninstalling Stitch in your HubSpot account
To uninstall Stitch in your HubSpot account:
1. Log in to your HubSpot account and click the **Marketplaces** account in the navigation bar.
2. Under **Manage**, click **Connected apps**.
3. Click the **Actions** drop-down menu in the **Stitch** app, and click **Uninstall**.
4. In the dialog box that appears, enter `uninstall` in the text field and click **Uninstall** to confirm.
## HubSpot table reference
Information note
**Schemas and versioning**
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is for **version 4** of this integration.
This is the latest version of the HubSpot integration.
### Custom HubSpot field replication
Custom object properties, or fields, are supported by Stitch’s HubSpot integration. Stitch will query the `properties` list for each object and, if custom fields are available through HubSpot’s API, replicate them to your destination.
The data types of these fields will be the same as the data type in HubSpot. For example: A custom field containing `date` data will be a `date` field in your destination.
This is applicable to any object that supports custom fields in HubSpot.
### HubSpot date/date-time values & UNIX timestamps
[HubSpot uses UNIX-formatted timestamps in milliseconds](https://developers.hubspot.com/docs/faq/how-should-timestamps-be-formatted-for-hubspots-apis) to store `date` and `datetime` data. Stitch doesn’t perform any transformation during the replication process, meaning these values won’t be converted to timestamps before they’re loaded into your destination.
To account for this, consider creating a user-defined function to perform the conversion or building views on top of the raw data.
Information note
**Table and column names in your destination**
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (`CusTomERs` > `customers`), while case is maintained in PostgreSQL destinations (`CusTomERs` > `CusTomERs`). Refer to the [Loading Guide](https://help.qlik.com/en-US/stitch/replication/loading/destination-guides) for your destination for more info.
### campaigns
The `campaigns` table contains info about the campaigns in your HubSpot account.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Full Table |
| --- | --- |
| **Primary Key ** | id |
| **Useful links** | [HubSpot documentation](http://developers.hubspot.com/docs/methods/email/get_campaign_data "Opens in new tab: HubSpot documentation")
[campaigns schema on GitHub](https://github.com/singer-io/tap-hubspot/blob/master/tap_hubspot/schemas/campaigns.json "Opens in new tab: campaigns schema on GitHub")
[HubSpot API method](https://developers.hubspot.com/docs/methods/email/get_campaign_data "Opens in new tab: HubSpot API method") |
campaigns table foreign keys
| Join campaigns with | on |
| --- | --- |
| [email_events](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#email-events) | ``` campaigns.id = email_events.emailCampaignId ``` |
| [forms](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#forms) | ``` campaigns.id = forms.leadNurturingCampaignId ``` |
campaigns table schema
| **appId**
INTEGER |
| --- |
| **appName**
STRING |
| **contentId**
INTEGER |
| **counters**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand counters
bounce
INTEGER
click
INTEGER
deferred
INTEGER
delievered
INTEGER
delivered
INTEGER
dropped
INTEGER
forward
INTEGER
mta_dropped
INTEGER
open
INTEGER
print
INTEGER
processed
INTEGER
reply
INTEGER
sent
INTEGER
spamreport
INTEGER
statuschange
INTEGER
suppressed
INTEGER
unsubscribed
INTEGER
|
| **id**
INTEGER |
| **name**
STRING |
| **numIncluded**
INTEGER |
| **numQueued**
INTEGER |
| **subType**
STRING |
| **subject**
STRING |
| **type**
STRING |
### companies
The `companies` table contains info about the companies your HubSpot contacts belong to.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | companyId |
| **Useful links** | [HubSpot documentation](http://developers.hubspot.com/docs/methods/companies/get_company "Opens in new tab: HubSpot documentation")
[companies schema on GitHub](https://github.com/singer-io/tap-hubspot/blob/master/tap_hubspot/schemas/companies.json "Opens in new tab: companies schema on GitHub")
[HubSpot API method](https://developers.hubspot.com/docs/methods/companies/get_company "Opens in new tab: HubSpot API method") |
companies table foreign keys
| Join companies with | on |
| --- | --- |
| [contacts_by_company](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#contacts-by-company) | ``` companies.companyId = contacts_by_company.company-id ``` |
| [deals](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#deals) | ``` companies.companyId = deals.associations.associatedCompanyIds ```
INTEGER |
### contact\_lists
The `contact_lists` table contains info about the contacts lists in your HubSpot account. Contact lists are used to segment contacts into groups, and there are two types: dynamic (smart lists) and static.
**Note:** You might need to create new connections to continue to replicate contacts\_lists data after April 30th 2026. For more information, see [HubSpot’s documentation](https://developers.hubspot.com/docs/api/crm/contacts#update-contact-connection-deprecation).
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | listId |
| **Replication Key ** | updatedAt |
| **Useful links** | [HubSpot documentation](https://developers.hubspot.com/docs/methods/lists/contact-lists-overview "Opens in new tab: HubSpot documentation")
[contact_lists schema on GitHub](https://github.com/singer-io/tap-hubspot/blob/master/tap_hubspot/schemas/contact_lists.json "Opens in new tab: contact_lists schema on GitHub")
[HubSpot API method](https://developers.hubspot.com/docs/methods/lists/get_lists "Opens in new tab: HubSpot API method") |
contact\_lists table foreign keys
| Join contact\_lists with | on |
| --- | --- |
| [contacts](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#contacts) | ``` contact_lists.listId = contacts.list-memberships.internal-list-id ```
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand additionalProperties
hs_folder_name
STRING
hs_last_record_added_at
STRING
hs_last_record_removed_at
STRING
hs_list_reference_count
STRING
hs_list_size
STRING
|
| **updatedById**
STRING |
| **createdById**
STRING |
| **name**
STRING |
| **createdAt**
STRING |
| **updatedAt**
STRING |
| **filtersUpdatedAt**
STRING |
| **deletedAt**
STRING |
### contacts
The `contacts` table contains info about individual contacts in HubSpot.
**Note:** You might need to create new connections to continue to replicate contacts data after April 30th 2026. For more information, see [HubSpot’s documentation](https://developers.hubspot.com/docs/api/crm/contacts#update-contact-connection-deprecation).
### Contact properties
If properties have been set for the contact, additional fields beginning with `properties__` will be included in the table. **Note**: Contacts will only have an entry for a property if that property has been set for the contact’s record.
HubSpot always types the value of `properties` fields as `STRING` despite the property type. [Refer to HubSpot’s documentation for more info](https://developers.hubspot.com/docs/methods/contacts/contacts-overview).
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | id |
| **Replication Key ** | updatedAt |
| **Useful links** | [HubSpot documentation](https://developers.hubspot.com/docs/methods/contacts/contacts-overview "Opens in new tab: HubSpot documentation")
[contacts schema on GitHub](https://github.com/singer-io/tap-hubspot/blob/master/tap_hubspot/schemas/contacts.json "Opens in new tab: contacts schema on GitHub")
[HubSpot API method](https://developers.hubspot.com/docs/methods/contacts/get_contacts "Opens in new tab: HubSpot API method") |
contacts table foreign keys
| Join contacts with | on |
| --- | --- |
| [contacts_by_company](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#contacts-by-company) | ``` contacts.canonical-vid = contacts_by_company.contact-id ``` |
| [contact_lists](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#contact-lists) | ``` contacts.list-memberships.internal-list-id = contact_lists.listId ```
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand associations
contacts
OBJECT
results
ARRAY
id
STRING
type
STRING
deals
OBJECT
results
ARRAY
id
STRING
type
STRING
tickets
OBJECT
results
ARRAY
id
STRING
type
STRING
|
| **objectWriteTraceId**
STRING |
### contacts\_by\_company
The `contacts_by_company` table contains contact and company ID pairs, allowing you to join contacts to relevant company data.
To replicate data from this table, you must also select the parent `companies` table.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Full Table |
| --- | --- |
| **Primary Keys ** | contact-id
company-id |
| **Useful links** | [HubSpot documentation](http://developers.hubspot.com/docs/methods/companies/get_company "Opens in new tab: HubSpot documentation")
INTEGER |
### custom\_objects
Tables for custom CRM objects in your HubSpot account will have the same name as the object. For example, if you have a custom object named `cars`, the table will be named `cars`.
The fields listed below are standard fields; they are included in every custom object table. A field will be added for each property you select when configuring the table. The property names will be prefixed with `property_`. For example, if you have a property named `model`, it will appear as `property_model`.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | id |
| **Replication Key ** | updatedAt |
| **Useful links** | [HubSpot documentation](https://developers.hubspot.com/docs/api/crm/crm-custom-objects "Opens in new tab: HubSpot documentation")
[custom_objects schema on GitHub](https://github.com/singer-io/tap-hubspot/tree/master/tap_hubspot/schemas/shared/custom_objects.json "Opens in new tab: custom_objects schema on GitHub") |
custom\_objects table schema
| **archived**
BOOLEAN |
| --- |
| **associations**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand associations
calls
OBJECT
results
ARRAY
id
STRING
type
STRING
companies
OBJECT
results
ARRAY
id
STRING
type
STRING
contacts
OBJECT
results
ARRAY
id
STRING
type
STRING
conversation_session
OBJECT
results
ARRAY
id
STRING
type
STRING
deals
OBJECT
results
ARRAY
id
STRING
type
STRING
emails
OBJECT
results
ARRAY
id
STRING
type
STRING
meetings
OBJECT
results
ARRAY
id
STRING
type
STRING
notes
OBJECT
results
ARRAY
id
STRING
type
STRING
products
OBJECT
results
ARRAY
id
STRING
type
STRING
tasks
OBJECT
results
ARRAY
id
STRING
type
STRING
tickets
OBJECT
results
ARRAY
id
STRING
type
STRING
|
| **createdAt**
DATE-TIME |
| **id**
STRING |
| **updatedAt**
DATE-TIME |
### deal\_pipelines
The `deal_pipelines` table contains info about the `deal stage` and `pipeline` properties.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Full Table |
| --- | --- |
| **Primary Key ** | pipelineId |
| **Useful links** | [HubSpot documentation](https://developers.hubspot.com/docs/methods/deal-pipelines/overview "Opens in new tab: HubSpot documentation")
[deal_pipelines schema on GitHub](https://github.com/singer-io/tap-hubspot/blob/master/tap_hubspot/schemas/deal_pipelines.json "Opens in new tab: deal_pipelines schema on GitHub")
[HubSpot API method](https://developers.hubspot.com/docs/methods/deal-pipelines/get-all-deal-pipelines "Opens in new tab: HubSpot API method") |
deal\_pipelines table schema
| **active**
BOOLEAN |
| --- |
| **displayOrder**
INTEGER |
| **label**
STRING |
| **pipelineId**
STRING |
| **stages**
ARRAY
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand stages
active
BOOLEAN
closedWon
BOOLEAN
displayOrder
INTEGER
label
STRING
probability
NUMBER
stageId
STRING
|
| **staticDefault**
BOOLEAN |
### deals
The `deals` table contains info about the deals in a HubSpot portal.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | dealId |
| **Useful links** | [HubSpot documentation](https://developers.hubspot.com/docs/methods/deals/deals_overview "Opens in new tab: HubSpot documentation")
[deals schema on GitHub](https://github.com/singer-io/tap-hubspot/blob/master/tap_hubspot/schemas/deals.json "Opens in new tab: deals schema on GitHub")
[HubSpot API method](https://developers.hubspot.com/docs/methods/deals/get-all-deals "Opens in new tab: HubSpot API method") |
deals table foreign keys
| Join deals with | on |
| --- | --- |
| [companies](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#companies) | ``` deals.associations.associatedCompanyIds = companies.companyId ```
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand associations
associatedCompanyIds
ARRAY
associatedDealIds
ARRAY
associatedVids
ARRAY
|
| --- |
| **dealId**
INTEGER |
| **isDeleted**
BOOLEAN |
| **portalId**
INTEGER |
### email\_events
The `email_events` table contains info about email events and how recipients interact with content.
#### Email events and HubSpot permissions
Replicating this table requires **Super Admin** permissions in HubSpot. The Super Admin role is different than the Admin role, which you can read more about in [HubSpot’s documentation](https://knowledge.hubspot.com/articles/kcs_article/settings/hubspot-user-roles-guide#admin).
If this table is selected and you don’t have Super Admin permissions in HubSpot, an error similar to the following will surface in the integration’s [Extraction Logs](https://help.qlik.com/en-US/stitch/replication/extractions/integration-extraction-logs):
```
tap - ERROR b'{"status":"error","message":"This oauth-token (**********) does not have proper permissions! (requires any of [email-access])", [...]
```
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | id |
| **Useful links** | [HubSpot documentation](https://developers.hubspot.com/docs/methods/email/email_events_overview "Opens in new tab: HubSpot documentation")
[email_events schema on GitHub](https://github.com/singer-io/tap-hubspot/blob/master/tap_hubspot/schemas/email_events.json "Opens in new tab: email_events schema on GitHub")
[HubSpot API method](https://developers.hubspot.com/docs/methods/email/get_events "Opens in new tab: HubSpot API method") |
email\_events table foreign keys
| Join email\_events with | on |
| --- | --- |
| [campaigns](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#campaigns) | ``` email_events.emailCampaignId = campaigns.id ``` |
| [forms](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#forms) | ``` email_events.emailCampaignId = forms.leadNurturingCampaignId ```
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand browser
family
STRING
name
STRING
producer
STRING
producerUrl
STRING
type
STRING
url
STRING
|
| **created**
DATE-TIME |
| **deviceType**
STRING |
| **duration**
INTEGER |
| **emailCampaignGroupId**
INTEGER |
| **emailCampaignId**
INTEGER |
| **filteredEvent**
BOOLEAN |
| **from**
STRING |
| **hmid**
STRING |
| **id**
STRING |
| **ipAddress**
STRING |
| **linkId**
INTEGER |
| **location**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand location
city
STRING
country
STRING
state
STRING
|
| **portalId**
INTEGER |
| **recipient**
STRING |
| **response**
STRING |
| **sentBy**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand sentBy
created
DATE-TIME
id
STRING
|
| **smtpId**
STRING |
| **subject**
STRING |
| **type**
STRING |
| **url**
STRING |
| **userAgent**
STRING |
### engagements
The `engagements` table contains info about all the engagements in a HubSpot portal.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | engagement\_id |
| **Replication Key ** | lastUpdated |
| **Useful links** | [HubSpot documentation](https://developers.hubspot.com/docs/methods/engagements/engagements-overview "Opens in new tab: HubSpot documentation")
[engagements schema on GitHub](https://github.com/singer-io/tap-hubspot/blob/master/tap_hubspot/schemas/engagements.json "Opens in new tab: engagements schema on GitHub")
[HubSpot API method](https://developers.hubspot.com/docs/methods/engagements/get-all-engagements "Opens in new tab: HubSpot API method") |
engagements table foreign keys
| Join engagements with | on |
| --- | --- |
| [companies](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#companies) | ``` engagements.associations.companyIds = companies.companyId ```
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand associations
companyIds
ARRAY
contactIds
ARRAY
dealIds
ARRAY
|
| --- |
| **attachments**
ARRAY
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand attachments
id
INTEGER
|
| **engagement**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand engagement
active
BOOLEAN
createdAt
DATE-TIME
id
INTEGER
lastUpdated
DATE-TIME
ownerId
INTEGER
portalId
INTEGER
timestamp
DATE-TIME
type
STRING
|
| **engagement\_id**
INTEGER |
| **lastUpdated**
DATE-TIME |
| **metadata**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand metadata
bcc
ARRAY
email
STRING
body
STRING
cc
ARRAY
email
STRING
disposition
STRING
durationMilliseconds
INTEGER
endTime
INTEGER
externalAccountId
STRING
externalId
STRING
forObjectType
STRING
from
OBJECT
email
STRING
firstName
STRING
lastName
STRING
fromNumber
STRING
html
STRING
recordingUrl
STRING
startTime
INTEGER
status
STRING
subject
STRING
text
STRING
title
STRING
to
ARRAY
email
STRING
toNumber
STRING
|
### forms
The `forms` table contains info about your HubSpot website forms.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | guid |
| **Replication Key ** | updatedAt |
| **Useful links** | [HubSpot documentation](https://developers.hubspot.com/docs/methods/forms/forms_overview "Opens in new tab: HubSpot documentation")
[forms schema on GitHub](https://github.com/singer-io/tap-hubspot/blob/master/tap_hubspot/schemas/forms.json "Opens in new tab: forms schema on GitHub")
[HubSpot API method](https://developers.hubspot.com/docs/methods/forms/v2/get_forms "Opens in new tab: HubSpot API method") |
forms table foreign keys
| Join forms with | on |
| --- | --- |
| [campaigns](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#campaigns) | ``` forms.leadNurturingCampaignId = campaigns.id ``` |
| [email_events](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#email-events) | ``` forms.leadNurturingCampaignId = email_events.emailCampaignId ```
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand formFieldGroups
default
BOOLEAN
fields
ARRAY
defaultValue
STRING
description
STRING
displayOrder
INTEGER
enabled
BOOLEAN
fieldType
STRING
groupName
STRING
hidden
BOOLEAN
isSmartField
BOOLEAN
label
STRING
labelHidden
BOOLEAN
name
STRING
options
ARRAY
description
STRING
displayOrder
INTEGER
doubleData
NUMBER
hidden
BOOLEAN
label
STRING
readOnly
BOOLEAN
value
STRING
placeholder
STRING
required
BOOLEAN
selectedOptions
ARRAY
type
STRING
unselectedLabel
STRING
validation
OBJECT
blockedEmailAddresses
ARRAY
data
STRING
message
STRING
name
STRING
useDefaultBlockList
BOOLEAN
isSmartGroup
BOOLEAN
richText
OBJECT
content
STRING
|
| **formType**
STRING |
| **guid**
STRING |
| **ignoreCurrentValues**
BOOLEAN |
| **inlineMessage**
STRING |
| **leadNurturingCampaignId**
STRING |
| **metaData**
ARRAY
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand metaData
name
STRING
value
STRING
|
| **method**
STRING |
| **migratedFrom**
STRING |
| **name**
STRING |
| **notifyRecipients**
STRING |
| **performableHtml**
STRING |
| **portalId**
INTEGER |
| **redirect**
STRING |
| **submitText**
STRING |
| **tmsId**
STRING |
| **updatedAt**
DATE-TIME |
### owners
The `owners` table contains info about the owners that exist in your HubSpot portal. Owners are created and updated in HubSpot when new users are added or when owners are synced from Salesforce to HubSpot.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | Id |
| **Replication Key ** | updatedAt |
| **Useful links** | [HubSpot documentation](https://developers.hubspot.com/docs/methods/owners/owners_overview "Opens in new tab: HubSpot documentation")
[owners schema on GitHub](https://github.com/singer-io/tap-hubspot/blob/master/tap_hubspot/schemas/owners.json "Opens in new tab: owners schema on GitHub")
[HubSpot API method](https://developers.hubspot.com/docs/api/crm/owners "Opens in new tab: HubSpot API method") |
owners table foreign keys
| Join owners with | on |
| --- | --- |
| [engagements](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#engagements) | ``` owners.Id = engagements.engagement.ownerId ``` |
owners table schema
| **archived**
BOOLEAN |
| --- |
| **createdAt**
DATE-TIME |
| **email**
STRING |
| **firstName**
STRING |
| **id**
STRING |
| **lastName**
STRING |
| **teams**
ARRAY
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand teams
id
STRING
name
STRING
primary
BOOLEAN
|
| **updatedAt**
DATE-TIME |
| **userId**
INTEGER |
### subscription\_changes
The `subscription_changes` table contains info about changes made subscriptions.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | recipient
portalId
timestamp |
| **Useful links** | [HubSpot documentation](https://developers.hubspot.com/docs/methods/timeline/timeline-overview "Opens in new tab: HubSpot documentation")
[subscription_changes schema on GitHub](https://github.com/singer-io/tap-hubspot/blob/master/tap_hubspot/schemas/subscription_changes.json "Opens in new tab: subscription_changes schema on GitHub")
[HubSpot API method](https://developers.hubspot.com/docs/methods/email/get_subscriptions_timeline "Opens in new tab: HubSpot API method") |
subscription\_changes table foreign keys
| Join subscription\_changes with | on |
| --- | --- |
| [companies](https://help.qlik.com/en-US/stitch/integrations/saas/hubspot#companies) | ``` subscription_changes.portalId = companies.portalId ```
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand changes
causedByEvent
OBJECT
created
DATE-TIME
id
STRING
change
STRING
changeType
STRING
portalId
INTEGER
source
STRING
subscriptionId
INTEGER
timestamp
DATE-TIME
|
| --- |
| **portalId**
INTEGER |
| **recipient**
STRING |
| **timestamp**
DATE-TIME |
### tickets
In HubSpot, tickets represents customer requests for help.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | id |
| **Replication Key ** | updatedAt |
| **Useful links** | [tickets schema on GitHub](https://github.com/singer-io/tap-hubspot/tree/master/tap_hubspot/schemas/tickets.json "Opens in new tab: tickets schema on GitHub")
[HubSpot API method](https://developers.hubspot.com/docs/api/crm/tickets "Opens in new tab: HubSpot API method") |
tickets table schema
| **archived**
BOOLEAN |
| --- |
| **associations**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand associations
companies
OBJECT
results
ARRAY
id
STRING
type
STRING
contacts
OBJECT
results
ARRAY
id
STRING
type
STRING
deals
OBJECT
results
ARRAY
id
STRING
type
STRING
|
| **createdAt**
DATE-TIME |
| **id**
STRING |
| **updatedAt**
DATE-TIME |
### workflows
The `workflows` table contains info about the workflows in your HubSpot portal.
**Note**: The `workflows` stream only supports contact-based workflows.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | id |
| **Replication Key ** | updatedAt |
| **Useful links** | [HubSpot documentation](https://developers.hubspot.com/docs/methods/workflows/workflows_overview "Opens in new tab: HubSpot documentation")
[workflows schema on GitHub](https://github.com/singer-io/tap-hubspot/blob/master/tap_hubspot/schemas/workflows.json "Opens in new tab: workflows schema on GitHub")
[HubSpot API method](https://developers.hubspot.com/docs/methods/workflows/v3/get_workflows "Opens in new tab: HubSpot API method") |
workflows table schema
| **contactListIds**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand contactListIds
active
INTEGER
enrolled
INTEGER
steps
ARRAY
|
| --- |
| **enabled**
BOOLEAN |
| **id**
INTEGER |
| **insertedAt**
DATE-TIME |
| **name**
STRING |
| **personaTagIds**
ARRAY
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>. |
| **type**