HubSpot

HubSpot is an AI-powered customer platform with all the software, integrations, and resources you need to connect your marketing, sales, and customer service.

It replicates data using the HubSpot REST API.

See the Schema section for a list of objects available for replication.

便利なリンクやサポートされている機能など、このコネクタの概要について説明します。

機能/性能	サポートの詳細
サポートされている Qlik Talend Data Integration プロジェクト	レプリケーションプロジェクトのみ。データパイプラインプロジェクトはサポートされていません。
ターゲットの更新方法	レプリケーションタスク: 変更を適用変更の保存データレイクタスクにデータをランディング: 変更データキャプチャ (CDC)
メタデータの管理	手動でのメタデータ生成は必要ありません。
スキーマの進化	[列のデータ型を変更] 操作のみサポートされています。
LOB 列 (NCLOB、CLOB、BLOB) のレプリケーション	サポートされていません。
スケジュールされた CDC	必須。これにより、ソースの変更に応じてターゲットが最新の状態に保たれます。レプリケーションタスクについては、「タスクのスケジューリング」を参照してください。レイクランディングタスクについては、「レイクランディングタスクの CDC のスケジュール設定」を参照してください。
通知	部分的にサポート動作変更時の通知の設定
監視	このコネクタではフルロードは関係ないため、CDC のみ。個々のデータタスクの監視
JSON 列ペイロードの自動ネスト解除	サポートされていません。ソースデータセット内の JSON 列ペイロードは、ターゲット上で自動的にネスト解除されません。

Preparing for authentication

To access your data, you need to authenticate the connection with your account credentials.

使用するアカウントに、フェッチするテーブルへのアクセス権があることを確認してください。

To retrieve your access token:

Log into HubSpot.
Create a private app by following HubSpot's documentation.
You must have a HubSpot super admin role to create a private app.
Once your private app is created, navigate to Development.
In the left sidebar menu, navigate to Legacy apps.
Click the name of your app.
Click the Auth tab > Show token to reveal your access token.
Copy and paste your access token into a secured file.

Creating the connection

詳細については、「SaaSアプリケーションへの接続」を参照してください。

必要な接続プロパティを入力します。
接続名に接続の名前を入力します。
接続メタデータを開くを選択して、作成時の接続のメタデータを定義します。
[作成] をクリックします。

Connection settings
Setting	Description
Data gateway	ユースケースに応じて Data Movement gateway を選択します。情報メモ Qlik Talend Cloud スターターサブスクリプションでは Data Movement gateway をサポートしていないため、この項目は使用できません。別のサブスクリプションティアを利用しており、Data Movement gateway を使用しない場合は、 [None] (なし) を選択します。 Data Movement gateway の利点とそれを必要とするユースケースの詳細については、「Qlik データゲートウェイ - データ移動」を参照してください。
Start Date	ソースからターゲットにデータをレプリケートする必要がある日付を `MM/DD/YYYY` 形式で入力します。
Personal Access Token	Personal access token.

Schema

Schemas and naming conventions can change from version to version. It is recommended to verify your version before continuing.

The schema and info displayed below is for version 2.

Custom HubSpot field replication

Custom object properties, or fields, are supported by HubSpot integration. It 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 to store date and datetime data. For more information, see Charts overview. It 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.

Depending on your destination, table and column names may not appear as they are outlined below.

campaigns

The campaigns table contains info about the campaigns in your HubSpot account.

Replication Method

Full Table

Primary Key

Useful links

HubSpot documentation

HubSpot API method

Join campaigns with	on
email_events	campaigns.id = email_events.emailCampaignId
forms	campaigns.id = forms.leadNurturingCampaignId

appId

INTEGER

appName

STRING

contentId

INTEGER

counters

OBJECT

This is a nested data structure:

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

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

CDC

Primary Key

companyId

Useful links

HubSpot documentation

HubSpot API method

Join companies with	on
contacts_by_company	companies.companyId = contacts_by_company.company-id
deals	companies.companyId = deals.associations.associatedCompanyIds companies.portalId = deals.portalId
engagements	companies.companyId = engagements.associations.companyIds companies.portalId = engagements.engagement.portalId
contact_lists	companies.portalId = contact_lists.portalId
contacts	companies.portalId = contacts.portal-id companies.portalId = contacts.form-submissions.portal-id
email_events	companies.portalId = email_events.portalId
forms	companies.portalId = forms.portalId
owners	companies.portalId = owners.portalId companies.portalId = owners.remoteList.portalId
subscription_changes	companies.portalId = subscription_changes.portalId companies.portalId = subscription_changes.changes.portalId

companyId

INTEGER

portalId

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.

Replication Method	CDC
Primary Key	listId
Replication Key	updatedAt
Useful links	HubSpot documentation HubSpot API method

Join contact_lists with	on
contacts	contact_lists.listId = contacts.list-memberships.internal-list-id contact_lists.portalId = contacts.portal-id contact_lists.portalId = contacts.form-submissions.portal-id
engagements	contact_lists.listId = engagements.associations.contactIds contact_lists.portalId = engagements.engagement.portalId
companies	contact_lists.portalId = companies.portalId
deals	contact_lists.portalId = deals.portalId
email_events	contact_lists.portalId = email_events.portalId
forms	contact_lists.portalId = forms.portalId
owners	contact_lists.portalId = owners.portalId contact_lists.portalId = owners.remoteList.portalId
subscription_changes	contact_lists.portalId = subscription_changes.portalId contact_lists.portalId = subscription_changes.changes.portalId

processingType

STRING

objectTypeId

STRING

listId

STRING

processingStatus

STRING

listVersion

STRING

additionalProperties

OBJECT

This is a nested data structure:

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.

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.

Replication Method	CDC
Primary Key	vid
Replication Key	versionTimestamp
Useful links	HubSpot documentation HubSpot API method

Join contacts with	on
contacts_by_company	contacts.canonical-vid = contacts_by_company.contact-id
contact_lists	contacts.list-memberships.internal-list-id = contact_lists.listId contacts.portal-id = contact_lists.portalId contacts.form-submissions.portal-id = contact_lists.portalId
engagements	contacts.list-memberships.internal-list-id = engagements.associations.contactIds contacts.portal-id = engagements.engagement.portalId contacts.form-submissions.portal-id = engagements.engagement.portalId
forms	contacts.form-submissions.form-id = forms.guid contacts.portal-id = forms.portalId contacts.form-submissions.portal-id = forms.portalId
companies	contacts.portal-id = companies.portalId contacts.form-submissions.portal-id = companies.portalId
deals	contacts.portal-id = deals.portalId contacts.form-submissions.portal-id = deals.portalId
email_events	contacts.portal-id = email_events.portalId contacts.form-submissions.portal-id = email_events.portalId
owners	contacts.portal-id = owners.portalId contacts.form-submissions.portal-id = owners.portalId contacts.portal-id = owners.remoteList.portalId contacts.form-submissions.portal-id = owners.remoteList.portalId
subscription_changes	contacts.portal-id = subscription_changes.portalId contacts.form-submissions.portal-id = subscription_changes.portalId contacts.portal-id = subscription_changes.changes.portalId contacts.form-submissions.portal-id = subscription_changes.changes.portalId

STRING

createdAt

STRING

updatedAt

STRING

archived

BOOLEAN

associations

OBJECT

This is a nested data structure:

contacts: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING
deals: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING
tickets: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - 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

Full Table

Primary Keys

contact-id

company-id

Useful links

HubSpot documentation

Join contacts_by_company with	on
contacts	contacts_by_company.contact-id = contacts.canonical-vid
companies	contacts_by_company.company-id = companies.companyId
deals	contacts_by_company.company-id = deals.associations.associatedCompanyIds
engagements	contacts_by_company.company-id = engagements.associations.companyIds

company-id

INTEGER

contact-id

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	CDC
Primary Key	id
Replication Key	updatedAt
Useful links	HubSpot documentation

archived

BOOLEAN

associations

OBJECT

This is a nested data structure:

calls: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING
companies: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING
contacts: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING
conversation_session: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING
deals: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING
emails: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING
meetings: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING
notes: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING
products: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING
tasks: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING
tickets: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING

createdAt

DATE-TIME

STRING

updatedAt

DATE-TIME

deal_pipelines

The deal_pipelines table contains info about the deal stage and pipeline properties.

Replication Method

Full Table

Primary Key

pipelineId

Useful links

HubSpot documentation

HubSpot API method

active

BOOLEAN

displayOrder

INTEGER

label

STRING

pipelineId

STRING

stages

ARRAY

This is a nested data structure:

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

CDC

Primary Key

dealId

Useful links

HubSpot documentation

HubSpot API method

Join deals with	on
companies	deals.associations.associatedCompanyIds = companies.companyId deals.portalId = companies.portalId
contacts_by_company	deals.associations.associatedCompanyIds = contacts_by_company.company-id
engagements	deals.associations.associatedCompanyIds = engagements.associations.companyIds deals.dealId = engagements.associations.dealIds deals.associations.associatedDealIds = engagements.associations.dealIds deals.portalId = engagements.engagement.portalId
contact_lists	deals.portalId = contact_lists.portalId
contacts	deals.portalId = contacts.portal-id deals.portalId = contacts.form-submissions.portal-id
email_events	deals.portalId = email_events.portalId
forms	deals.portalId = forms.portalId
owners	deals.portalId = owners.portalId deals.portalId = owners.remoteList.portalId
subscription_changes	deals.portalId = subscription_changes.portalId deals.portalId = subscription_changes.changes.portalId

associations

OBJECT

This is a nested data structure:

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.

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:

tap - ERROR b'{"status":"error","message":"This oauth-token (**********) does not have proper permissions! (requires any of [email-access])", [...]

Replication Method

CDC

Primary Key

Useful links

HubSpot documentation

HubSpot API method

Join email_events with	on
campaigns	email_events.emailCampaignId = campaigns.id
forms	email_events.emailCampaignId = forms.leadNurturingCampaignId email_events.portalId = forms.portalId
companies	email_events.portalId = companies.portalId
contact_lists	email_events.portalId = contact_lists.portalId
contacts	email_events.portalId = contacts.portal-id email_events.portalId = contacts.form-submissions.portal-id
deals	email_events.portalId = deals.portalId
engagements	email_events.portalId = engagements.engagement.portalId
owners	email_events.portalId = owners.portalId email_events.portalId = owners.remoteList.portalId
subscription_changes	email_events.portalId = subscription_changes.portalId email_events.portalId = subscription_changes.changes.portalId

appId

INTEGER

appName

STRING

browser

OBJECT

This is a nested data structure:

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

ipAddress

STRING

linkId

INTEGER

location

OBJECT

This is a nested data structure:

city: STRING
country: STRING
state: STRING

portalId

INTEGER

recipient

STRING

response

STRING

sentBy

OBJECT

This is a nested data structure:

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	CDC
Primary Key	engagement_id
Replication Key	lastUpdated
Useful links	HubSpot documentation HubSpot API method

Join engagements with	on
companies	engagements.associations.companyIds = companies.companyId engagements.engagement.portalId = companies.portalId
contacts_by_company	engagements.associations.companyIds = contacts_by_company.company-id
deals	engagements.associations.companyIds = deals.associations.associatedCompanyIds engagements.associations.dealIds = deals.dealId engagements.associations.dealIds = deals.associations.associatedDealIds engagements.engagement.portalId = deals.portalId
contact_lists	engagements.associations.contactIds = contact_lists.listId engagements.engagement.portalId = contact_lists.portalId
contacts	engagements.associations.contactIds = contacts.list-memberships.internal-list-id engagements.engagement.portalId = contacts.portal-id engagements.engagement.portalId = contacts.form-submissions.portal-id
owners	engagements.engagement.ownerId = owners.ownerId engagements.engagement.ownerId = owners.remoteList.ownerId engagements.engagement.portalId = owners.portalId engagements.engagement.portalId = owners.remoteList.portalId
email_events	engagements.engagement.portalId = email_events.portalId
forms	engagements.engagement.portalId = forms.portalId
subscription_changes	engagements.engagement.portalId = subscription_changes.portalId engagements.engagement.portalId = subscription_changes.changes.portalId

associations

OBJECT

This is a nested data structure:

companyIds: ARRAY, which is also a nested data structure.
contactIds: ARRAY, which is also a nested data structure.
dealIds: ARRAY, which is also a nested data structure.

attachments

ARRAY

This is a nested data structure:

id: INTEGER

engagement

OBJECT

This is a nested data structure:

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:

bcc: ARRAY, which is also a nested data structure.
- email: STRING
body: STRING
cc: ARRAY, which is also a nested data structure.
- email: STRING
disposition: STRING
durationMilliseconds: INTEGER
endTime: INTEGER
externalAccountId: STRING
externalId: STRING
forObjectType: STRING
from: OBJECT, which is also a nested data structure.
- email: STRING
- firstName: STRING
- lastName: STRING
fromNumber: STRING
html: STRING
recordingUrl: STRING
startTime: INTEGER
status: STRING
subject: STRING
text: STRING
title: STRING
to: ARRAY, which is also a nested data structure.
- email: STRING
toNumber: STRING

forms

The forms table contains info about your HubSpot website forms.

Replication Method	CDC
Primary Key	guid
Replication Key	updatedAt
Useful links	HubSpot documentation HubSpot API method

Join forms with	on
campaigns	forms.leadNurturingCampaignId = campaigns.id
email_events	forms.leadNurturingCampaignId = email_events.emailCampaignId forms.portalId = email_events.portalId
contacts	forms.guid = contacts.form-submissions.form-id forms.portalId = contacts.portal-id forms.portalId = contacts.form-submissions.portal-id
companies	forms.portalId = companies.portalId
contact_lists	forms.portalId = contact_lists.portalId
deals	forms.portalId = deals.portalId
engagements	forms.portalId = engagements.engagement.portalId
owners	forms.portalId = owners.portalId forms.portalId = owners.remoteList.portalId
subscription_changes	forms.portalId = subscription_changes.portalId forms.portalId = subscription_changes.changes.portalId

action

STRING

campaignGuid

STRING

captchaEnabled

BOOLEAN

cloneable

BOOLEAN

createdAt

DATE-TIME

cssClass

STRING

deletable

BOOLEAN

deletedAt

INTEGER

editable

BOOLEAN

followUpId

STRING

formFieldGroups

ARRAY

This is a nested data structure:

default: BOOLEAN
fields: ARRAY, which is also a nested data structure.
- defaultValue: STRING
- description: STRING
- displayOrder: INTEGER
- enabled: BOOLEAN
- fieldType: STRING
- groupName: STRING
- hidden: BOOLEAN
- isSmartField: BOOLEAN
- label: STRING
- labelHidden: BOOLEAN
- name: STRING
- options: ARRAY, which is also a nested data structure.
  - 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, which is also a nested data structure.
  - blockedEmailAddresses: ARRAY
  - data: STRING
  - message: STRING
  - name: STRING
  - useDefaultBlockList: BOOLEAN
isSmartGroup: BOOLEAN
richText: OBJECT, which is also a nested data structure.
- content: STRING

formType

STRING

guid

STRING

ignoreCurrentValues

BOOLEAN

inlineMessage

STRING

leadNurturingCampaignId

STRING

metaData

ARRAY

This is a nested data structure:

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	CDC
Primary Key	ownerId
Replication Key	updatedAt
Useful links	HubSpot documentation HubSpot API method

Join owners with	on
engagements	owners.ownerId = engagements.engagement.ownerId owners.remoteList.ownerId = engagements.engagement.ownerId owners.portalId = engagements.engagement.portalId owners.remoteList.portalId = engagements.engagement.portalId
companies	owners.portalId = companies.portalId owners.remoteList.portalId = companies.portalId
contact_lists	owners.portalId = contact_lists.portalId owners.remoteList.portalId = contact_lists.portalId
contacts	owners.portalId = contacts.portal-id owners.remoteList.portalId = contacts.portal-id owners.portalId = contacts.form-submissions.portal-id owners.remoteList.portalId = contacts.form-submissions.portal-id
deals	owners.portalId = deals.portalId owners.remoteList.portalId = deals.portalId
email_events	owners.portalId = email_events.portalId owners.remoteList.portalId = email_events.portalId
forms	owners.portalId = forms.portalId owners.remoteList.portalId = forms.portalId
subscription_changes	owners.portalId = subscription_changes.portalId owners.remoteList.portalId = subscription_changes.portalId owners.portalId = subscription_changes.changes.portalId owners.remoteList.portalId = subscription_changes.changes.portalId

archived

BOOLEAN

createdAt

DATE-TIME

email

STRING

firstName

STRING

lastName

STRING

teams

ARRAY

This is a nested data structure:

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

CDC

Primary Keys

recipient

portalId

timestamp

Useful links

HubSpot documentation

HubSpot API method

Join subscription_changes with	on
companies	subscription_changes.portalId = companies.portalId subscription_changes.changes.portalId = companies.portalId
contact_lists	subscription_changes.portalId = contact_lists.portalId subscription_changes.changes.portalId = contact_lists.portalId
contacts	subscription_changes.portalId = contacts.portal-id subscription_changes.changes.portalId = contacts.portal-id subscription_changes.portalId = contacts.form-submissions.portal-id subscription_changes.changes.portalId = contacts.form-submissions.portal-id
deals	subscription_changes.portalId = deals.portalId subscription_changes.changes.portalId = deals.portalId
email_events	subscription_changes.portalId = email_events.portalId subscription_changes.changes.portalId = email_events.portalId
engagements	subscription_changes.portalId = engagements.engagement.portalId subscription_changes.changes.portalId = engagements.engagement.portalId
forms	subscription_changes.portalId = forms.portalId subscription_changes.changes.portalId = forms.portalId
owners	subscription_changes.portalId = owners.portalId subscription_changes.changes.portalId = owners.portalId subscription_changes.portalId = owners.remoteList.portalId subscription_changes.changes.portalId = owners.remoteList.portalId

changes

ARRAY

This is a nested data structure:

causedByEvent: OBJECT, which is also a nested data structure.
- 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	CDC
Primary Key	id
Replication Key	updatedAt
Useful links	HubSpot API method

archived

BOOLEAN

associations

OBJECT

This is a nested data structure:

companies: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING
contacts: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING
deals: OBJECT, which is also a nested data structure.
- results: ARRAY, which is also a nested data structure.
  - id: STRING
  - type: STRING

createdAt

DATE-TIME

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	CDC
Primary Key	id
Replication Key	updatedAt
Useful links	HubSpot documentation HubSpot API method

contactListIds

OBJECT

This is a nested data structure:

active: INTEGER
enrolled: INTEGER
steps: ARRAY, which is also a nested data structure.

enabled

BOOLEAN

INTEGER

insertedAt

DATE-TIME

name

STRING

personaTagIds

ARRAY

This is a nested data structure.

type

STRING

updatedAt

DATE-TIME

このページは役に立ちましたか?

このページまたはコンテンツにタイポ、ステップの省略、技術的エラーなどの問題が見つかった場合はお知らせください。

こちらにフィードバックをお寄せください