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 프로젝트 복제 프로젝트 에만 해당됩니다. 데이터 파이프라인 프로젝트는 지원되지 않습니다.대상 업데이트 방법
복제 작업:
데이터 레이크 작업에 데이터 랜딩:
메타데이터 관리
수동 메타데이터 생성이 필요하지 않습니다. 스키마 진화
열 데이터 유형 변경 작업만 지원됩니다. 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
사용 사례에 필요한 경우 데이터 이동 게이트웨이 를 선택합니다.
정보 메모 이 필드는 데이터 이동 게이트웨이 를 지원하지 않으므로 Qlik Talend Cloud 시작 구독에서는 사용할 수 없습니다. 다른 구독 계층이 있고 데이터 이동 게이트웨이 를 사용하지 않으려면 없음 을 선택합니다.
데이터 이동 게이트웨이 의 이점과 이를 필요로 하는 사용 사례에 대한 자세한 내용은 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.
campaigns table foreign keys Join campaigns with on email_events campaigns.id = email_events.emailCampaignId forms campaigns.id = forms.leadNurturingCampaignId
campaigns table schema
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
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.
companies table foreign keys 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
companies table schema
companyId
INTEGER
portalId
INTEGER
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.
The contacts table contains info about individual contacts in HubSpot.
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 .
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.
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.
custom_objects table schema
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.
companies: OBJECT, which is also a nested data structure.
results: ARRAY, which is also a nested data structure.
contacts: OBJECT, which is also a nested data structure.
results: ARRAY, which is also a nested data structure.
conversation_session: OBJECT, which is also a nested data structure.
results: ARRAY, which is also a nested data structure.
deals: OBJECT, which is also a nested data structure.
results: ARRAY, which is also a nested data structure.
emails: OBJECT, which is also a nested data structure.
results: ARRAY, which is also a nested data structure.
meetings: OBJECT, which is also a nested data structure.
results: ARRAY, which is also a nested data structure.
notes: OBJECT, which is also a nested data structure.
results: ARRAY, which is also a nested data structure.
products: OBJECT, which is also a nested data structure.
results: ARRAY, which is also a nested data structure.
tasks: OBJECT, which is also a nested data structure.
results: ARRAY, which is also a nested data structure.
tickets: OBJECT, which is also a nested data structure.
results: ARRAY, which is also a nested data structure.
createdAt
DATE-TIME
id
STRING
updatedAt
DATE-TIME
deal_pipelines
The deal_pipelines table contains info about the deal stage and pipeline properties.
deal_pipelines table schema
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.
deals table foreign keys 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
deals table schema
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])", [...]
email_events table foreign keys 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
email_events table schema
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
id
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.
engagements table foreign keys 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
engagements table schema
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:
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.
body: STRING cc: ARRAY, which is also a nested data structure.
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.
toNumber: STRING
The forms table contains info about your HubSpot website forms.
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.
owners table foreign keys 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
owners table schema
archived
BOOLEAN
createdAt
DATE-TIME
email
STRING
firstName
STRING
id
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.
subscription_changes table foreign keys 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
subscription_changes table schema
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
tickets table schema
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.
contacts: OBJECT, which is also a nested data structure.
results: ARRAY, which is also a nested data structure.
deals: OBJECT, which is also a nested data structure.
results: ARRAY, which is also a nested data structure.
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.
workflows table schema
contactListIds
OBJECT
This is a nested data structure:
active: INTEGER enrolled: INTEGER steps: ARRAY, which is also a nested data structure.
enabled
BOOLEAN
id
INTEGER
insertedAt
DATE-TIME
name
STRING
personaTagIds
ARRAY
This is a nested data structure.
type
STRING
updatedAt
DATE-TIME