HubSpot
Set up the HubSpot source connector and find its reference information on this page.
Prerequisites
- HubSpot Account
- For Airbyte Open Source: a Private App access token or a Service Key
Setup guide
Step 1: Set up HubSpot
For Airbyte Cloud:
- OAuth (Recommended). Use OAuth instead of Private App authentication to simplify the setup process significantly.
- Private App: If you’re using a Private App, use your Access Token to set up the connector. See official HubSpot documentation for instructions on getting the access token. If your HubSpot account can no longer create Private Apps, create a Service Key instead. Enter it in the same Access token field.
For Airbyte Open Source:
- Private App setup (Recommended): If you’re authenticating through a Private App, use your Access Token to set up the connector. See official HubSpot documentation for instructions on getting the access token. If your HubSpot account can no longer create Private Apps, create a Service Key instead. Enter it in the same Access token field.
- OAuth setup: If you’re using OAuth to authenticate on Airbyte Open Source, see HubSpot’s detailed walkthrough. You’ll need the following details to set up the connector:
- Client ID
- Client Secret
- Refresh Token
See HubSpot’s authentication documentation for more details.
Service keys
HubSpot is retiring the creation of legacy Private Apps. Accounts created on or after September 28, 2026 can’t create new Private Apps from that date. All other accounts lose this ability on October 26, 2026. Existing Private Apps and their access tokens will continue working.
If your account can’t create a Private App, use a HubSpot Service Key (public beta). A Service Key is a static bearer token. It uses the same pat- format and per-object scopes as a Private App access token. The connector therefore accepts it without any special configuration:
- In HubSpot, go to Development, then Keys > Service keys, and click Create service key.
- Add the scopes for the streams you want to sync. See Step 2. HubSpot has deprecated the legacy
ticketsande-commercescopes, so the Service Key scope picker might not offer them. Step 2 lists their granular replacements. - Create the key, click Show, and copy it.
- In Airbyte, choose the Private App authentication method. Paste the Service Key into the Access token field.
A Service Key can only include scopes that your HubSpot account and user already have. If HubSpot returns 403 for a stream, first confirm the key has the scope listed in Step 2. If the scope is present, your account’s subscription tier probably doesn’t include that object. For example, the leads stream needs the Leads object, which requires Sales Hub Professional or Enterprise.
Step 2: Configure stream scopes (Private App and Service Key only) {#step-2-configure-the-scopes-for-your-streams-private-app-only}
These instructions only apply when you authenticate with a Private App or a Service Key. You can skip them if you’re using OAuth.
For a Private App or Service Key, configure scopes manually so Airbyte can sync all available data. Each scope relates to one or more specific streams. See HubSpot’s documentation on scopes for instructions.
The legacy tickets and e-commerce scopes are deprecated. They might be unavailable when you create a Service Key. Where the table lists tickets, grant crm.objects.tickets.read. Also grant crm.schemas.tickets.read for ticket properties and pipelines. Where it lists e-commerce, grant crm.objects.products.read, crm.objects.line_items.read, and crm.schemas.line_items.read.
Expand to review scopes
| Stream | Required Scope |
|---|---|
campaigns | content |
companies | crm.objects.companies.read, crm.schemas.companies.read |
contact_lists | crm.lists.read |
contacts | crm.objects.contacts.read |
association_streams | Read scopes for the selected source and target objects |
| Custom CRM Objects | crm.objects.custom.read |
custom_object_association_streams | crm.objects.custom.read and the read scope for any selected standard object |
deal_pipelines | crm.objects.contacts.read |
deals | crm.objects.deals.read, crm.schemas.deals.read |
deals_archived | crm.objects.deals.read, crm.schemas.deals.read |
email_events | content |
email_subscriptions | content |
engagements | crm.objects.companies.read, crm.objects.contacts.read, crm.objects.deals.read, tickets, e-commerce |
engagements_emails | sales-email-read |
engagements_task_pipelines | crm.objects.contacts.read |
forms | forms |
form_submissions | forms |
goals | crm.objects.goals.read |
leads | crm.objects.leads.read, crm.schemas.leads.read |
list_memberships | crm.lists.read |
line_items | e-commerce |
listings | crm.objects.listings.read |
owners | crm.objects.owners.read |
products | e-commerce |
contacts_property_history | crm.objects.contacts.read |
companies_property_history | crm.objects.companies.read |
deals_property_history | crm.objects.deals.read |
subscription_changes | content |
tickets | tickets |
users | crm.objects.users.read, settings.users.read |
account_details | oauth |
deal_splits | crm.objects.deals.read |
properties | No additional scopes required |
workflows | automation |
flows | automation (plus *.sensitive.read for flows touching sensitive data) |
contacts_web_analytics | business-intelligence, crm.objects.contacts.read |
companies_web_analytics | business-intelligence, crm.objects.companies.read |
deals_web_analytics | business-intelligence, crm.objects.deals.read |
tickets_web_analytics | business-intelligence, tickets |
engagements_calls_web_analytics | business-intelligence, crm.objects.contacts.read |
engagements_emails_web_analytics | business-intelligence, crm.objects.contacts.read, sales-email-read |
engagements_meetings_web_analytics | business-intelligence, crm.objects.contacts.read |
engagements_notes_web_analytics | business-intelligence, crm.objects.contacts.read |
engagements_tasks_web_analytics | business-intelligence, crm.objects.contacts.read |
goals_web_analytics | business-intelligence, crm.objects.goals.read |
line_items_web_analytics | business-intelligence, e-commerce, crm.objects.line_items.read |
products_web_analytics | business-intelligence, e-commerce |
Step 3: Set up the HubSpot connector in Airbyte
Airbyte Cloud
- Log into your Airbyte Cloud account.
- Click Sources, then click + New source.
- On the Set up the source page, select HubSpot from the Source type dropdown.
- Enter a name for the HubSpot connector.
- From the Authentication dropdown, select your chosen authentication method:
-
(Recommended) To authenticate using OAuth, select OAuth. Click Authenticate your HubSpot account to sign in with HubSpot and authorise your account.
:::note HubSpot Authentication issues The popup window might show an
An invalid scope name was providederror during authentication. Close the window and retry authentication. ::: -
(Not Recommended) To authenticate using a Private App, select Private App. Enter the Access Token for your HubSpot account. Enter a Service Key in the same field.
-
- (Optional) For Start date, use the date picker or enter the date in this format:
yyyy-mm-ddThh:mm:ssZ. Data added on or after this date will be replicated. If unset, the start date defaults to “2006-06-01T00:00:00Z”, when HubSpot was created.
- (Optional) Set CRM Search Lookback Window in minutes. CRM Search streams will re-fetch data from this period before the previous sync’s state. These streams include contacts, companies, deals and tickets. This helps capture missing records in CRM Search streams.
- (Optional) Set Property History Lookback Window in minutes for property history streams:
deals_property_history,contacts_property_historyandcompanies_property_history. These streams will re-fetch data from this period. This helps capture records missed through cursor drift from HubSpot calculated properties. A reasonable starting point is43200(30 days). - (Optional) Enable Treat dynamic number and boolean properties as strings if your destination rejects values that HubSpot returns outside the declared
numberorbooleantype. See Destination type conversion errors in Troubleshooting for details. - Click Set up source and wait for the tests to finish.
Airbyte Open Source
- Go to the Airbyte Open Source dashboard.
- In the Airbyte UI, click Sources, then + New Source. Select HubSpot from the available sources.
- Enter your chosen Source name.
- Select your authentication method from the Authentication dropdown:
- (Recommended) To authenticate with a Private App, select Private App. Enter your HubSpot account’s Access Token. A Service Key goes in the same field.
- (Not recommended) To authenticate with OAuth, select OAuth. Enter your Client ID, Client Secret and Refresh Token.
- (Optional) For Start date, use the date picker or enter the date in this format:
yyyy-mm-ddThh:mm:ssZ. Data added on or after this date will be replicated. If unset, the start date defaults to “2006-06-01T00:00:00Z”, when HubSpot was created. For more efficient synchronisation, provide a start date relevant to your data. - (Optional) Set CRM Search Lookback Window in minutes. CRM Search streams will re-fetch data from this period before the previous sync’s state. These streams include contacts, companies, deals and tickets. This helps capture missing records in CRM Search streams.
- (Optional) Set Property History Lookback Window in minutes for property history streams:
deals_property_history,contacts_property_historyandcompanies_property_history. These streams will re-fetch data from this period. This helps capture records missed through cursor drift from HubSpot calculated properties. A reasonable starting point is43200(30 days). - (Optional) Enable Treat dynamic number and boolean properties as strings if your destination rejects values that HubSpot returns outside the declared
numberorbooleantype. See Destination type conversion errors in Troubleshooting for details. - Click Set up source and wait for the tests to finish.
Experimental streams
Enable Enable experimental streams to sync the Web Analytics streams. They read HubSpot’s Events API (/events/event-occurrences/2026-03). They emit web analytics events for each parent object, including page views and form submissions:
contacts_web_analyticscompanies_web_analyticsdeals_web_analyticstickets_web_analyticsengagements_calls_web_analyticsengagements_emails_web_analyticsengagements_meetings_web_analyticsengagements_notes_web_analyticsengagements_tasks_web_analyticsgoals_web_analyticsline_items_web_analyticsproducts_web_analytics
These streams require HubSpot Marketing Hub Enterprise and the business-intelligence scope. They also require each stream’s parent-object read scope. See the scopes table in Step 2. They start syncing from the configured Start date with fresh state.
This toggle also enables the flows stream. It syncs full workflow definitions from HubSpot’s Automation v4 Flows API. See Flows vs. workflows below.
Association streams
Use Association Between Objects Streams to sync relationships between two standard HubSpot CRM objects. Add one item for each relationship you want to sync. Each item creates a stream that reads IDs from the source object. It calls HubSpot’s associations batch read API and emits one record for each association.
Configure these fields for each association stream:
- From Object: The source object type, such as
tickets,dealsorcontacts. - To Object: The target object type, such as
companiesorcontacts. - Stream Name: Optional. Leave this empty and Airbyte names the stream
associations_<from_object>_<to_object>.
For example, set From Object to tickets and To Object to companies. This creates the associations_tickets_companies stream. After adding or editing association stream settings, refresh the source schema. The generated streams will then appear in the catalogue.
Association stream records include:
from_id: The source object record’s ID.to_id: The target object record’s ID.association_type_id: HubSpot’s numeric association type identifier.category: The association category, such asHUBSPOT_DEFINEDorUSER_DEFINED.label: The association label. This isnullfor unlabelled associations.
Association streams sync in Full Refresh mode. The stream doesn’t track an incremental cursor. Each sync reads every parent record modified since the configured start date, then fetches its associations.
Grant read scopes for both selected objects when you authenticate with a Private App or Service Key. For example, a tickets-to-companies association stream needs the tickets (or, for a Service Key, crm.objects.tickets.read) and crm.objects.companies.read scopes.
Custom object associations
Use Custom Object Association Streams to sync relationships where one or both sides are custom HubSpot objects. Add one item for each relationship you want to sync.
Configure these fields for each custom object association stream:
- From Object: The source object’s name or identifier.
- To Object: The target object’s name or identifier.
- Stream Name: Optional. Leave this empty and Airbyte names the stream
associations_<from_object>_<to_object>.
After adding or editing custom object association stream settings, refresh the source schema. The generated streams will then appear in the catalogue.
For custom objects, use either:
- The custom object’s
fullyQualifiedName, such asp_my_custom_object. - The custom object’s
objectTypeId, such as2-12345.
For the standard-object side of the relationship, use standard object names such as contacts, companies, or deals.
Custom object association streams emit the same fields as standard association streams: from_id, to_id, association_type_id, category, and label. They also sync in Full Refresh mode.
If you authenticate with a Private App or Service Key, grant crm.objects.custom.read. Also grant the read scope for every standard object in the relationship.
Supported sync modes
The HubSpot source connector supports these sync modes:
- Full Refresh
- Incremental
:::note You can use two types of incremental sync:
- Incremental: the API returns only data updated or generated since the last sync.
- Client-Side Incremental: the API returns all available data, then the connector filters for new records. :::
Supported streams
The HubSpot source connector supports these streams:
- Campaigns (Client-Side Incremental)
- Companies (Incremental)
- Contact Lists (Incremental)
- Contacts (Incremental)
- Deal Pipelines (Client-Side Incremental)
- Deal Splits (Incremental)
- Deals (including Contact associations) (Incremental)
- HubSpot’s recycle bin keeps deleted (archived) records for only 90 days. See response from HubSpot Team.
- Deals Archived (including Contact associations) (Incremental)
- Email Events (Incremental)
- Email Subscriptions
- Engagements (Incremental)
- Engagements Calls (Incremental)
- Engagements Emails (Incremental)
- Engagements Meetings (Incremental)
- Engagements Notes (Incremental)
- Engagements Tasks (Incremental)
- Engagements Task Pipelines (Client-Side Incremental)
- Forms (Client-Side Incremental)
- Form Submissions (Client-Side Incremental)
- Goals (Incremental)
- Leads (Incremental)
- List Memberships (Full Refresh)
- Line Items (Incremental)
- Listings (Incremental)
- Marketing Emails (Incremental)
- Owners (Client-Side Incremental)
- Owners Archived (Client-Side Incremental)
- Users (Full-Refresh)
- Products (Incremental)
- Properties (Full Refresh)
- Contacts Property History (Client-Side Incremental)
- Companies Property History (Client-Side Incremental)
- Deals Property History (Client-Side Incremental)
- Subscription Changes (Incremental)
- Tickets (Incremental)
- Ticket Pipelines (Client-Side Incremental)
- Workflows (Client-Side Incremental)
- Flows (Client-Side Incremental, experimental)
- Account Details (Full Refresh)
- Association streams for standard objects, such as
associations_tickets_companies(Full Refresh) - Custom object association streams for custom-to-standard or custom-to-custom associations (Full Refresh)
Entity-relationship diagram
Flows and workflows
The connector provides HubSpot automations through two independent streams. Neither replaces the other, and you can sync both simultaneously.
workflows | flows | |
|---|---|---|
| HubSpot API | Legacy GET /automation/v3/workflows | GET /automation/v4/flows |
| Availability | Always available | Requires Enable experimental streams |
| Content | Inventory metadata only (name, type, enabled, counters, migration status) | Full workflow definitions |
id type | Integer | String |
| Cursor format | Epoch milliseconds | ISO 8601 date-time |
Use flows when you need the workflow definition, rather than an inventory. This includes the actions action graph, enrollmentCriteria, dataSources, enrollmentSchedule, timeWindows, blockedDates, goal and suppression filter branches, and un-enrolment settings.
Keep these points in mind for the flows stream:
- It costs one extra API call per flow. The list endpoint returns summaries only, so the connector fetches
GET /automation/v4/flows/{flowId}for every emitted flow. Filtering happens before enrichment. Therefore, incremental syncs only incur this cost for flows changed since the previous sync. - It covers more than workflows. The v4 API also returns platform flows and action sets (
flowTypeofACTION_SET). Therefore,flowstypically contains more records thanworkflows. To include only contact workflows, filter onflowTypeandtypedownstream. - Flows are not joinable to workflows by
id. The two APIs use different identifier spaces. HubSpot providesPOST /automation/v4/workflow-id-mappings/batch/readto translate between them, but the connector doesn’t call it. - Inaccessible flows degrade rather than fail. HubSpot requires additional
*.sensitive.readscopes for flows referencing sensitive data. If a detail request fails, the connector logs a warning naming the flow. It then emits the flow’s summary fields, preventing one restricted flow from failing the entire stream. - The upstream API is a developer preview. HubSpot documents Automation v4 as subject to change. For this reason, the stream sits behind the experimental toggle. The
actions,enrollmentCriteria,dataSources, and filter-branch fields use free-form object types. This prevents new HubSpot action or criteria subtypes from breaking syncs.
About the property_history streams
The property history streams (contacts_property_history, companies_property_history, deals_property_history) use Client-Side Incremental sync. A cursor timestamp identifies records changed since the previous sync.
HubSpot calculated properties include formula fields, rollup summaries, and analytics properties such as hs_analytics_*. Their timestamp always reflects the latest sync, not the latest user-initiated change. The cursor can therefore advance past records that haven’t synced yet, resulting in missing records.
To reduce this risk, configure the Property History Lookback Window in the source settings. A value of 43200 (30 days) is a reasonable starting point. These streams use Append + Deduped sync mode, which automatically handles duplicate records from the lookback period.
By default, these streams request every property history for the object. This can generate many API requests and records. To limit them, configure Deals Property History Properties, Contacts Property History Properties, or Companies Property History Properties with property internal names, such as ["dealstage"]. The corresponding stream then syncs history only for the listed properties. For internal names, see HubSpot’s default deal, contact, and company properties. If a list is empty or unset, the stream syncs history for all properties.
About the engagements stream
- Objects in the
engagementsstream can have these types:note,email,task,meeting,call. The engagement type determines which object properties appear in the destination’sengagements_metadatatable:
- A
callengagement has a correspondingengagements_metadataobject. It has non-null values in thetoNumber,fromNumber,status,externalId,durationMilliseconds,externalAccountId,recordingUrl,body, anddispositioncolumns. - An
emailengagement has a correspondingengagements_metadataobject. It has non-null values in thesubject,html, andtextcolumns. You’ll also find records in four related tables:engagements_metadata_from,engagements_metadata_to,engagements_metadata_cc, andengagements_metadata_bcc. - A
meetingengagement has a correspondingengagements_metadataobject. It has non-null values in thebody,startTime,endTime, andtitlecolumns. - A
noteengagement has a correspondingengagements_metadataobject with a non-null value in thebodycolumn. - A
taskengagement has a correspondingengagements_metadataobject. It has non-null values in thebody,status, andforObjectTypecolumns.
- The
engagementsstream selects between two APIs. The selection depends on time since the last sync and how many records Airbyte hasn’t yet synced.
- EngagementsRecent when both criteria are met:
- The last sync ran within the past 30 days
- The sync includes fewer than 10,000 records
- EngagementsAll when either criterion isn’t met.
The engagements stream can sync slowly when it hasn’t synced within 30 days or generates large volumes of new data. Schedule more frequent syncs to accommodate this limitation.
deal_pipelines stream notes
From version 6.13.3, the deal_pipelines stream reads from HubSpot’s Pipelines API 2026-09. HubSpot retires Pipelines API V1 on 4 December 2026. The connector converts records back to the V1 shape. Columns, the primary key and the cursor remain unchanged. Some output details differ from earlier versions:
- The new API doesn’t return
default. For HubSpot’s built-in deal pipeline, the connector sets it totruewhenpipelineIdisdefault. For every other pipeline, it sets it tofalse. - The new API doesn’t return
objectTypeorobjectTypeId. The connector sets them toDEALand0-3. These are the values V1 returned for deal pipelines. - Each item in
stageshas a newwritePermissionsfield. - Built-in pipeline stages can have
updatedAtset to0instead ofnull. - Stages within a pipeline can appear in a different order.
Forms and Form Submissions stream notes
This stream syncs marketing forms only.
list_memberships stream notes
The list_memberships stream reads memberships for every list returned by the contact_lists stream. It calls HubSpot’s GET /crm/v3/lists/{listId}/memberships endpoint. Keep these behaviours in mind:
- The stream supports full refresh only. HubSpot’s memberships endpoint doesn’t provide a suitable cursor for incremental sync.
- The composite primary key
(recordId, listId)identifies records.listIdis emitted as a string, allowing records to serialise cleanly to Avro destinations. - Some lists returned by
contact_listsreference anobjectTypeIdthat isn’t active for your portal. Examples include Leads lists withobjectTypeId0-136. HubSpot’s memberships endpoint rejects these lists with a 400VALIDATION_ERROR / ListError.INVALID_OBJECT_TYPE_FOR_LIST. The connector skips these lists to prevent sync failure and logs an entry for each one. To sync memberships for those object types, enable the corresponding HubSpot object. Alternatively, sync the object directly from its own stream, such asleads.
Custom CRM objects
Custom CRM Objects appear as available streams alongside the standard objects listed above.
Discover returns two identically named streams when a custom object shares a built-in stream’s name. For example, this happens with a custom object named form_submissions. Connection setup then fails with a duplicate stream name error. To fix this, enable Prefix custom objects that share a name with a built-in stream (prefix_colliding_custom_objects) in the source configuration. Then refresh the source schema. The custom object then appears as custom_object_<name>. Custom objects with other names aren’t renamed.
If you already synced the identically named built-in stream, it may contain the custom object’s records. After enabling the setting and refreshing the schema, clear that stream’s data. Its destination table will then contain only the built-in stream’s records.
Connections created before 15 April 2023 on Airbyte Cloud require extra steps to sync custom CRM objects. This also applies to OSS connections created before 0.8.0.
First, give the connector these additional permissions:
-
If you are using OAuth on Airbyte Cloud: Open the HubSpot source settings page in the Airbyte UI. Re-authenticate through OAuth to grant Airbyte permission to access custom objects.
-
If you are using OAuth on OSS, Private App, or Service Key auth: Open the HubSpot UI where you created your Private App, Service Key, or OAuth application. Add the
crm.objects.custom.readscope to its scopes. See HubSpot’s scopes documentation.
Then open your connection’s schema tab and click refresh source schema. This pulls in the new streams for syncing.
Limitations and troubleshooting
Expand to see details about HubSpot connector limitations and troubleshooting.
Rate limits
Normal HubSpot rate limits restrict the connector. The burst limit applies per app. All apps within the same HubSpot account share the daily limit.
| Product tier | Burst (per 10 seconds) | Daily (per account) |
|---|---|---|
| Free & Starter | 100 | 250,000 |
| Professional | 190 | 625,000 |
| Enterprise | 190 | 1,000,000 |
| API Limit Increase add-on | 250 | +1,000,000 per add-on (max 2) |
Slow custom property syncs
Syncs take longer when you use custom properties in HubSpot. Airbyte doesn’t alert you when custom properties are present. You can check for them in HubSpot’s UI.
Troubleshooting
-
Enabling streams: Some streams, including
workflows, require specific scopes before the connector can read them. Without the required user permissions, the connector logs a warning and skips the stream. -
HubSpot object labels HubSpot can apply a stream label that differs from its original API name. HubSpot’s UI shows the stream label, while Airbyte shows the stream name. If you can’t find an expected stream, search for the HubSpot object’s
nameinstead. -
Unnesting top level properties: Since version 1.5.0, the connector provides access to nested fields. It also denests top-level fields into individual destination fields. This most often affects the
propertiesfield, which is split into each attribute in the destination.For example:
{ "id": 1, "updatedAt": "2020-01-01", "properties": { "hs_note_body": "World's best boss", "hs_created_by": "Michael Scott" } }becomes
{ "id": 1, "updatedAt": "2020-01-01", "properties": { "hs_note_body": "World's best boss", "hs_created_by": "Michael Scott" }, "properties_hs_note_body": "World's best boss", "properties_hs_created_by": "Michael Scott" } -
401 Unauthorized Error (Private App Token or Service Key)
The connector fails immediately if you authenticate using a Private App access token or Service Key and receive a 401 Unauthorized error. A configuration error asks you to update your token. These tokens are static and can’t be refreshed, so retrying won’t help. Generate a new access token in your HubSpot Private App settings or rotate your Service Key. Then update the connector configuration.
With OAuth, the connector automatically refreshes expired tokens and retries the request. You only need to act if the error persists. If it does, re-authenticate the connector.
-
403 Forbidden Error
-
HubSpot has scopes for each API call.
-
Each stream links to a scope. You need access to that scope to sync its data.
-
Additional permissions:
feedback_submissions: Service Hub Professional accountmarketing_emails: Market Hub Starter accountworkflows: Sales, Service, and Marketing Hub Professional accountsflows: Sales, Service, and Marketing Hub Professional accounts
-
-
Find common troubleshooting guidance for the HubSpot source connector on Airbyte Forum.
-
Missing records in CRM Search streams (
deals,companies,engagements_calls,engagements_emails,engagements_meetings,engagements_notes,engagements_tasks,contacts,deal_splits,leads,tickets):- Missing records during incremental syncs may result from irregularities in HubSpot’s API behaviour.
- To reduce this risk, configure the CRM Search Lookback Window in the source settings. This re-fetches data for a set number of minutes before the previous sync’s state. It helps capture missing records.
contactsand custom objects use the list endpoint for their first incremental sync instead of CRM Search. They also use it after a reset or refresh. That sync can save a cursor later than its start time. The next sync won’t capture a previously read record edited before the first sync finishes. Set the CRM Search Lookback Window to at least that first sync’s duration in minutes. With Incremental | Append + Deduped, records fetched again are deduplicated.
-
Missing records in property history streams (
deals_property_history,contacts_property_history,companies_property_history):- HubSpot calculated properties include formula fields, rollup summaries and analytics properties. They can emit timestamps ahead of user-initiated changes. This can move the sync cursor beyond records that haven’t yet synced.
- To reduce this risk, configure the Property History Lookback Window in the source settings. A value of
43200(30 days) is recommended. These streams use Append + Deduped sync mode, which automatically handles duplicate records from the lookback period.
-
Destination type conversion errors on dynamic
number/booleanproperties, such asJSON → NUMERIC,JSON → BOOLor decimal-precision / scale errors onhs_hd_ticket_ids,zendesk_requester_id,hs_task_send_default_reminderor anycompanies.properties.*field:- HubSpot sometimes declares a property as
numberorbooleanbut returns values that can’t be cast to that type. Examples include semicolon-separated IDs ("3092727991;3881228353;15895321999") in anumberfield and multi-value text in abooleanfield. They also include numbers beyond the declared precision. The connector then emits the raw string. However, the published schema still specifiesnumber/boolean, so strict destinations reject the record. - To resolve this, enable Treat dynamic number and boolean properties as strings (
treat_numbers_and_booleans_as_strings) in the source configuration. The connector then declares every HubSpot dynamic property normally defined asnumberorbooleanasstring. Affected values reach the destination as strings instead of failing type conversion. - The toggle only affects HubSpot dynamic
properties.*fields. It doesn’t change static schema fields or non-property fields. - After enabling the toggle you must refresh both the schema and the data. Otherwise, the new string type won’t reach the destination. In the Airbyte UI:
- Open the affected connection.
- Click Refresh source schema and save the updated catalog. The affected columns should now be
string. - Trigger a Refresh data sync. Alternatively, clear the affected streams and run a new sync. This rewrites the destination tables with the new column type. It also re-emits previously rejected records as strings.
- If you later disable the toggle, follow the same steps. Refresh the schema and data so the destination column types match the new catalog.
- HubSpot sometimes declares a property as
IP allow list
If you use Airbyte Cloud and restrict access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.
Changelog
Expand to review
| Version | Date | Pull Request | Subject |
|---|---|---|---|
| 6.14.1 | 2026-11-04 | 90854 | Fix contacts silently missing records: CRM Search now pages by record ID, and Full Refresh reads contacts from the list endpoint. |
| 6.14.0 | 2026-11-04 | 88970 | Add listings stream |
| 6.13.3 | 2026-11-03 | 90251 | Migrate deal_pipelines to Pipelines API 2026-09 ahead of the V1 sunset. Columns, primary key and cursor are unchanged; stages gain writePermissions. See Notes on the deal_pipelines stream |
| 6.13.2 | 2026-11-03 | 88157 | Fix custom object association streams with a contacts from_object: use the lastmodifieddate parent cursor, as the standard association streams do, instead of hs_lastmodifieddate, which contacts do not have and which made the stream emit no records. Document association streams as Full Refresh. |
| 6.13.1 | 2026-11-03 | 89950 | Update dependencies |
| 6.13.0 | 2026-10-14 | 88415 | Add the optional prefix_colliding_custom_objects config toggle. When enabled, a custom object whose name matches a built-in stream (e.g. form_submissions) is exposed as custom_object_<name>, so connections can be created without a duplicate stream name error. Off by default, so existing stream names are unchanged. |
| 6.12.2 | 2026-10-20 | 89246 | Update dependencies |
| 6.12.1 | 2026-10-13 | 87204 | Update dependencies |
| 6.12.0 | 2026-09-12 | 85854 | Add the flows stream, which syncs full workflow definitions (action graph, enrollment criteria, data sources, schedules) from HubSpot’s Automation v4 Flows API. Each flow summary from GET /automation/v4/flows is enriched with GET /automation/v4/flows/{flowId}. Requires the automation scope and is gated behind enable_experimental_streams because the upstream API is a HubSpot developer preview. The legacy workflows stream is unchanged. |
| 6.11.0 | 2026-10-01 | 87604 | Add deals_property_history_properties, contacts_property_history_properties, and companies_property_history_properties config options to limit property history streams to a configured list of properties |
| 6.10.0 | 2026-09-22 | 86415 | Add new engagements_task_pipelines stream exposing HubSpot task pipelines and their stages, so engagements_tasks.properties.hs_pipeline_stage can be resolved to a stage label and open/closed state |
| 6.9.3 | 2026-09-22 | 86682 | Update dependencies |
| 6.9.2 | 2026-09-16 | 86350 | Report an invalid from_object/to_object identifier in custom_object_association_streams as a configuration error instead of a generic credentials error |
| 6.9.1 | 2026-09-15 | 86075 | Update dependencies |
| 6.9.0 | 2026-09-14 | 82769 | Declare marketing_emails testing.isAbVariation and teams[].primary on owners and owners_archived, returned by the API but missing from the schemas |
| 6.8.3 | 2026-09-08 | 85528 | Update dependencies |
| 6.8.2 | 2026-08-20 | 84917 | Update CDK to 7.28.0 to fix a startup crash (ValueError: No format in [...] matching True) when a full-refresh association stream with an incremental_dependency parent is deselected. |
| 6.8.1 | 2026-08-14 | 84411 | Fix the Number of concurrent threads setting being ignored: read the num_worker config key emitted by the spec instead of num_workers |
| 6.8.0 | 2026-06-24 | 80806 | Restore 12 Web Analytics streams removed during the v5.8.0 manifest-only migration. Uses HubSpot’s latest 2026-03 Events API endpoint with explicit eventType fanout. Streams require the business-intelligence scope (Marketing Hub Enterprise) plus each parent stream’s read scope. Gated behind enable_experimental_streams with fresh state from start_date. |
| 6.7.0 | 2026-06-11 | 76396 | Add treat_numbers_and_booleans_as_strings config toggle to coerce dynamic number/boolean properties to string |
| 6.6.1 | 2026-06-10 | 79636 | Add configurable property_history_lookback_window (minutes) to property history streams (deals, contacts, companies) to prevent silent record loss caused by cursor drift from HubSpot calculated properties. Clarify existing lookback_window field as CRM Search-specific. |
| 6.6.0 | 2026-06-08 | 71259 | Add association streams for standard and custom objects, including optional OAuth scopes needed to support them |
| 6.5.5 | 2026-04-28 | 76323 | Add failure_type classification to list_memberships error handler response filters |
| 6.5.4 | 2026-04-21 | 76848 | Fix OAuth optional_scopes to align with connector streams |
| 6.5.3 | 2026-04-21 | 76073 | Update CDK to pre-release with deadlock fix |
| 6.5.2 | 2026-04-21 | 76641 | Update dependencies |
| 6.5.1 | 2026-04-20 | 76395 | Emit listId as a string in the list_memberships stream, and skip lists whose objectTypeId is not active for the portal (for example, Leads) instead of failing the sync |
| 6.5.0 | 2026-04-14 | 75281 | Add new list_memberships stream via V3 Lists API |
| 6.4.4 | 2026-04-13 | 76276 | Rename “concurrent workers” to “concurrent threads” in connector spec |
| 6.4.3 | 2026-04-08 | 76149 | Added missing OAuth scopes crm.objects.users.read and settings.users.read for the users stream |
| 6.4.2 | 2026-04-06 | 76096 | Remove registry version overrides pinning to 6.3.1, fix stream count test assertions |
| 6.4.1 | 2026-04-03 | 75574 | Add oauth_connector_input_specification with granular scopes and optional_scopes |
| 6.4.0 | 2026-04-01 | 70920 | Add new stream Users |
| 6.3.5 | 2026-03-31 | 75665 | Update dependencies |
| 6.3.4 | 2026-03-30 | 75595 | Fixed HTTP 429 responses mapped to RETRY instead of RATE_LIMITED, enabling correct rate-limit handling |
| 6.3.3 | 2026-03-26 | 75452 | Fixed HTTP 401 errors retrying indefinitely for Private App Token authentication |
| 6.3.2 | 2026-03-17 | 74526 | Update dependencies |
| 6.3.1 | 2026-03-09 | 74410 | Promoting release candidate 6.3.1-rc.1 to a main version. |
| 6.3.1-rc.1 | 2026-03-03 | 74032 | fix(source-hubspot): use v3 properties API for CRM search streams |
| 6.3.0 | 2026-03-03 | 61703 | Add new stream account_details |
| 6.2.2 | 2026-02-24 | 73909 | Update dependencies |
| 6.2.1 | 2026-02-17 | 73491 | Update dependencies |
| 6.2.0 | 2026-03-03 | 61704 | Add new properties stream |
| 6.1.1 | 2026-02-10 | 70486 | Update dependencies |
| 6.1.0 | 2026-02-06 | 72906 | Promoting release candidate 6.1.0-rc.2 to a main version. |
| 6.1.0-rc.2 | 2026-02-03 | 72799 | Bump the CDK version which fixed a bug where streams without incremental showed a cursor |
| 6.1.0-rc.1 | 2025-12-09 | 69782 | Allow for user defined cursor field key in the configured catalog for incremental streams |
| 6.0.15 | 2025-11-25 | 70053 | Update dependencies |
| 6.0.14 | 2025-11-24 | 69803 | Add missing fields in Marketing Emails stream for Avro/Parquet conversions |
| 6.0.13 | 2025-11-19 | 69749 | Fix retrieving associations for CRMSearch streams |
| 6.0.12 | 2025-11-19 | 69203 | Add lookback window |
| 6.0.11 | 2025-11-18 | 69381 | Update dependencies |
| 6.0.10 | 2025-11-03 | 69145 | Promoting release candidate 6.0.10-rc.1 to a main version. |
| 6.0.10-rc.1 | 2025-10-30 | 68610 | Add APIBudget |
| 6.0.9 | 2025-10-29 | 69077 | Promoting release candidate 6.0.9-rc.1 to a main version. |
| 6.0.9-rc.1 | 2025-10-27 | 68665 | Improve performance following CDK release 7.4.1 |
| 6.0.8 | 2025-10-27 | 68662 | Promoting release candidate 6.0.8-rc.1 to a main version. |
| 6.0.8-rc.1 | 2025-10-22 | 63744 | Switch all CRMSearch streams to use incremental endpoint for server-side filtering, even during full refresh |
| 6.0.7 | 2025-10-21 | 68582 | Promoting release candidate 6.0.7-rc.1 to a main version. |
| 6.0.7-rc.1 | 2025-10-20 | 68159 | Upgrade to latest version of CDK 7.3.7 to get the bug fix for missing custom properties during incremental syncs |
| 6.0.6 | 2025-10-14 | 67911 | Update dependencies |
| 6.0.5 | 2025-10-07 | 67400 | Update dependencies |
| 6.0.4 | 2025-09-30 | 66409 | Update dependencies |
| 6.0.3 | 2025-09-25 | 66700 | Revert to 6.0.1 |
| 6.0.2 | 2025-09-15 | 65947 | Set fallback target type to ‘string’ for numbers and booleans |
| 6.0.1 | 2025-09-09 | 66100 | Update dependencies |
| 6.0.0 | 2025-09-02 | 65100 | Migrate Marketing Emails stream from deprecated v1 API to v3 API. Breaking change requires stream reset. This change also enables incremental syncs for marketing_emails stream. |
| 5.8.20 | 2025-08-25 | 65513 | Add missing datetime format |
| 5.8.19 | 2025-08-23 | 65327 | Update dependencies |
| 5.8.18 | 2025-08-09 | 64603 | Update dependencies |
| 5.8.17 | 2025-08-03 | 64197 | Update dependencies |
| 5.8.16 | 2025-07-26 | 63898 | Update dependencies |
| 5.8.15 | 2025-07-21 | 63341 | Bump memory on Discover to 1GB |
| 5.8.14 | 2025-07-19 | 63499 | Update dependencies |
| 5.8.13 | 2025-07-12 | 63115 | Update dependencies |
| 5.8.12 | 2025-07-08 | 62866 | Handle non-numeric values in fields with declared numeric type |
| 5.8.11 | 2025-07-07 | 62838 | Promoting release candidate 5.8.11-rc.1 to a main version. |
| 5.8.11-rc.1 | 2025-07-02 | 62481 | For CRMSearch streams, fix retry behavior for the underlying associations HttpRequester to retry 401 errors |
| 5.8.10 | 2025-06-28 | 62179 | Update dependencies |
| 5.8.9 | 2025-06-21 | 61842 | Update dependencies |
| 5.8.8 | 2025-06-14 | 60640 | Update dependencies |
| 5.8.7 | 2025-06-11 | 61543 | Fix pagination for contacts and other CRM Search streams when paginating past 10,000 records streams |
| 5.8.6 | 2025-06-10 | 61502 | Set cursor based pagination for CRM object streams |
| 5.8.5 | 2025-06-02 | 61326 | Additional change for millisecond float timestamps |
| 5.8.4 | 2025-05-30 | 61013 | Fix Typo |
| 5.8.3 | 2025-05-30 | 61007 | Bump memory on Check to 1600mi |
| 5.8.2 | 2025-05-29 | 60962 | Fix bug to allow millisecond timestamps coming in as a float string to be parsed into a datetime. |
| 5.8.1 | 2025-05-28 | 60937 | Retry 401 Unauthorized errors since token might have just expired. |
| 5.8.0 | 2025-05-28 | 60855 | Migrate to manifest-only |
| 5.7.0 | 2025-05-27 | 60919 | Promoting release candidate 5.7.0-rc.2 to a main version. |
| 5.7.0-rc.2 | 2025-05-23 | 60881 | Ignore 403 errors for dynamic streams to prevent sync failures |
| 5.7.0-rc.1 | 2025-05-22 | 60830 | Migrate CustomObjects streams |
| 5.6.0 | 2025-05-21 | 60338 | Migrate CRM search streams: contacts, deal_splits, leads, tickets |
| 5.5.0 | 2025-05-21 | 60812 | Migrate CRM search companies stream |
| 5.4.0 | 2025-05-20 | 59727 | Migrate CRM object streams: goals, product, line_items |
| 5.3.0 | 2025-05-16 | 60249 | Migrate engagements_calls, engagements_emails, engagements_meetings, engagements_notes, engagements_tasks to low code |
| 5.2.0 | 2025-05-15 | 60306 | Promoting release candidate 5.2.0-rc.1 to a main version. |
| 5.2.0-rc.1 | 2025-05-14 | 59127 | Migrate deals to low code |
| 5.1.0 | 2025-05-14 | 60276 | Promoting release candidate 5.1.0-rc.1 to a main version. |
| 5.1.0-rc.1 | 2025-05-13 | 58105 | Migrate deals_archived, forms, form_submissions, owners, owners_archived to low-code |
| 5.0.0 | 2025-05-12 | 59673 | Deprecate contacts_form_submissions, contacts_list_memberships, contacts_merged_audit streams which are not supported in Hubspot’s V3 API. Update contact_lists to use V3 API. |
| 4.12.2 | 2025-05-09 | 59755 | Add missing cursor format for workflows stream state migration |
| 4.12.1 | 2025-05-10 | 59810 | Update dependencies |
| 4.12.0 | 2025-05-09 | 58592 | Migrate incremental streams: email_events, engagements, subscription_changes |
| 4.11.0 | 2025-05-07 | 59216 | Migrate workflows to low code |
| 4.10.0 | 2025-05-07 | 59195 | Migrate deal_pipelines to low code |
| 4.9.0 | 2025-05-07 | 58135 | Migrate campaigns to low code |
| 4.8.0 | 2025-05-06 | 59693 | Promoting release candidate 4.8.0-rc.1 to a main version. |
| 4.8.0-rc.1 | 2025-04-30 | 58092 | Migrate companies_property_history, contacts_property_history and deals_property_history to low code |
| 4.7.0 | 2025-04-30 | 59165 | Promoting release candidate 4.7.0-rc.2 to a main version. |
| 4.7.0-rc.2 | 2025-04-28 | 59118 | Add empty string state migration |
| 4.7.0-rc.1 | 2025-04-23 | 58083 | Migrate ticket_pipelines to low code |
| 4.6.4 | 2025-04-22 | 58138 | Use short-hand custom object type name path for custom object streams. |
| 4.6.3 | 2025-04-19 | 58226 | Update dependencies |
| 4.6.2 | 2025-04-18 | 58137 | Promoting release candidate 4.6.2-rc.1 to a main version. |
| 4.6.2-rc.1 | 2025-04-13 | 57534 | Migrate marketing_emails and email_subscriptions to low code |
| 4.6.1 | 2025-04-12 | 57694 | Update dependencies |
| 4.6.0 | 2025-04-11 | 57572 | Promoting release candidate 4.6.0-rc.1 to a main version. |
| 4.6.0-rc.1 | 2025-03-31 | 56919 | Update CDK to v6 |
| 4.5.6 | 2025-03-29 | 56647 | Update dependencies |
| 4.5.5 | 2025-03-26 | 56416 | Disabled blog_comment and all form-types for Forms and FormSubmissions stream |
| 4.5.4 | 2025-03-25 | 55822 | add userIdIncludingInactive to owners and owners_archived streams |
| 4.5.3 | 2025-03-24 | 55245 | Add conversionId to form_submissions schema |
| 4.5.2 | 2024-12-14 | 49141 | Improves Forms stream by adding the formTypes query parameter to support all form types. This enhancement also propagates to the FormSubmission stream. |
| 4.5.1 | 2025-03-22 | 53818 | Update dependencies |
| 4.5.0 | 2025-03-10 | 54177 | Add option to cast fields from stream json schema per list of fields |
| 4.4.9 | 2025-02-01 | 52729 | Update dependencies |
| 4.4.8 | 2025-01-25 | 52295 | Update dependencies |
| 4.4.7 | 2025-01-11 | 51146 | Update dependencies |
| 4.4.6 | 2025-01-04 | 50898 | Update dependencies |
| 4.4.5 | 2024-12-28 | 50669 | Update dependencies |
| 4.4.4 | 2024-12-21 | 50138 | Update dependencies |
| 4.4.3 | 2024-12-14 | 48984 | Update dependencies |
| 4.4.2 | 2024-12-10 | 48480 | Adds individual read scopes to LineItems Stream |
| 4.4.1 | 2024-11-25 | 48662 | Starting with this version, the Docker image is now rootless. Please note that this and future versions will not be compatible with Airbyte versions earlier than 0.64 |
| 4.4.0 | 2024-11-18 | 48548 | Promoting release candidate 4.4.0-rc.1 to a main version. |
| 4.4.0-rc.1 | 2024-11-18 | 48472 | Adds support to maintain use of legacy fields for Contacts, Deals, and DealsArchived streams: hs_lifecyclestage_{stage_id}_date, hs_date_entered_{stage_id}, hs_date_exited_{stage_id}, hs_time_in_{stage_id}. |
| 4.3.0 | 2024-11-15 | 44481 | Add Leads stream |
| 4.2.26 | 2024-11-04 | 48199 | Update dependencies |
| 4.2.25 | 2024-10-29 | 47028 | Update dependencies |
| 4.2.24 | 2024-10-12 | 46827 | Update dependencies |
| 4.2.23 | 2024-10-05 | 46494 | Update dependencies |
| 4.2.22 | 2024-09-28 | 46160 | Update dependencies |
| 4.2.21 | 2024-09-23 | 44899 | Fix incremental search to use primary key as placeholder instead of lastModifiedDate |
| 4.2.20 | 2024-09-21 | 45753 | Update dependencies |
| 4.2.19 | 2024-09-14 | 45018 | Update dependencies |
| 4.2.18 | 2024-08-24 | 43762 | Update dependencies |
| 4.2.17 | 2024-08-21 | 44538 | Fix issue with CRM search streams when they have no associations |
| 4.2.16 | 2024-08-20 | 42919 | Add support for Deal Splits |
| 4.2.15 | 2024-08-08 | 43381 | Fix associations retrieval for Engagements streams (calls, meetings, notes, tasks, emails) in Incremental with existing state |
| 4.2.14 | 2024-07-27 | 42688 | Update dependencies |
| 4.2.13 | 2024-07-20 | 42264 | Update dependencies |
| 4.2.12 | 2024-07-13 | 41766 | Update dependencies |
| 4.2.11 | 2024-07-10 | 41558 | Update dependencies |
| 4.2.10 | 2024-07-09 | 41286 | Update dependencies |
| 4.2.9 | 2024-07-08 | 41045 | Use latest CDK version possible |
| 4.2.8 | 2024-07-06 | 40923 | Update dependencies |
| 4.2.7 | 2024-06-25 | 40441 | Update dependencies |
| 4.2.6 | 2024-06-22 | 40126 | Update dependencies |
| 4.2.5 | 2024-06-17 | 39432 | Remove references to deprecated state method |
| 4.2.4 | 2024-06-10 | 38800 | Retry hubspot _parse_and_handle_errors on JSON decode errors |
| 4.2.3 | 2024-06-06 | 39314 | Added missing schema types for the Workflows stream schema |
| 4.2.2 | 2024-06-04 | 38981 | [autopull] Upgrade base image to v1.2.1 |
| 4.2.1 | 2024-05-30 | 38024 | Retry when attempting to get scopes |
| 4.2.0 | 2024-05-24 | 38049 | Add resumable full refresh support to contacts_form_submissions and contacts_merged_audit streams |
| 4.1.5 | 2024-05-17 | 38243 | Replace AirbyteLogger with logging.Logger |
| 4.1.4 | 2024-05-16 | 38286 | Added default schema normalization for the Tickets stream, to ensure the data types |
| 4.1.3 | 2024-05-13 | 38128 | contacts_list_memberships as semi-incremental stream |
| 4.1.2 | 2024-04-24 | 36642 | Schema descriptions and CDK 0.80.0 |
| 4.1.1 | 2024-04-11 | 35945 | Add integration tests |
| 4.1.0 | 2024-03-27 | 36541 | Added test configuration features, fixed type hints |
| 4.0.0 | 2024-03-10 | 35662 | Update Deals Property History and Companies Property History schemas |
| 3.3.0 | 2024-02-16 | 34597 | Make start date not required, sync all data from default value if it’s not provided |
| 3.2.0 | 2024-02-15 | 35328 | Add mailingIlsListsIncluded and mailingIlsListsExcluded fields to Marketing emails stream schema |
| 3.1.1 | 2024-02-12 | 35165 | Manage dependencies with Poetry. |
| 3.1.0 | 2024-02-05 | 34829 | Add Contacts Form Submissions stream |
| 3.0.1 | 2024-01-29 | 34635 | Fix pagination for CompaniesPropertyHistory stream |
| 3.0.0 | 2024-01-25 | 34492 | Update marketing_emails stream schema |
| 2.0.2 | 2023-12-15 | 33844 | Make property_history PK combined to support Incremental/Deduped sync type |
| 2.0.1 | 2023-12-15 | 33527 | Make query string calculated correctly for PropertyHistory streams to avoid 414 HTTP Errors |
| 2.0.0 | 2023-12-08 | 33266 | Add ContactsPropertyHistory, CompaniesPropertyHistory, DealsPropertyHistory streams |
| 1.9.0 | 2023-12-04 | 33042 | Add Web Analytics streams |
| 1.8.0 | 2023-11-23 | 32778 | Extend PropertyHistory stream to support incremental sync |
| 1.7.0 | 2023-11-01 | 32035 | Extend the Forms stream schema |
| 1.6.1 | 2023-10-20 | 31644 | Base image migration: remove Dockerfile and use the python-connector-base image |
| 1.6.0 | 2023-10-19 | 31606 | Add new field aifeatures to the marketing emails stream schema |
| 1.5.1 | 2023-10-04 | 31050 | Add type transformer for Engagements stream |
| 1.5.0 | 2023-09-11 | 30322 | Unnest stream schemas |
| 1.4.1 | 2023-08-22 | 29715 | Fix python package configuration stream |
| 1.4.0 | 2023-08-11 | 29249 | Add OwnersArchived stream |
| 1.3.3 | 2023-08-10 | 29248 | Specify threadId in engagements stream to type string |
| 1.3.2 | 2023-08-10 | 29326 | Add primary keys to streams ContactLists and PropertyHistory |
| 1.3.1 | 2023-08-08 | 29211 | Handle 400 and 403 errors without interruption of the sync |
| 1.3.0 | 2023-08-01 | 28909 | Add handling of source connection errors |
| 1.2.0 | 2023-07-27 | 27091 | Add new stream ContactsMergedAudit |
| 1.1.2 | 2023-07-27 | 28558 | Improve error messages during connector setup |
| 1.1.1 | 2023-07-25 | 28705 | Fix retry handler for token expired error |
| 1.1.0 | 2023-07-18 | 28349 | Add unexpected fields in schemas of streams email_events, email_subscriptions, engagements, campaigns |
| 1.0.1 | 2023-06-23 | 27658 | Use fully qualified name to retrieve custom objects |
| 1.0.0 | 2023-06-08 | 27161 | Fix increment sync for engagements stream, ‘Recent’ API is used for recent syncs of last recent 30 days and less than 10k records, otherwise full sync if performed by ‘All’ API |
| 0.9.0 | 2023-06-26 | 27726 | License Update: Elv2 |
| 0.8.4 | 2023-05-17 | 26082 | Fixed bug with wrong parsing of boolean encoded like “false” parsed as True |
| 0.8.3 | 2023-05-31 | 26831 | Remove authSpecification from connector specification in favour of advancedAuth |
| 0.8.2 | 2023-05-16 | 26418 | Add custom availability strategy which catches permission errors from parent streams |
| 0.8.1 | 2023-05-29 | 26719 | Handle issue when state value is literally "" (empty str) |
| 0.8.0 | 2023-04-10 | 16032 | Add new stream Custom Object |
| 0.7.0 | 2023-04-10 | 24450 | Add new stream Goals |
| 0.6.2 | 2023-04-28 | 25667 | Fix bug with Invalid Date like 2000-00-00T00:00:00Z while settip up the connector |
| 0.6.1 | 2023-04-10 | 21423 | Update scope for DealPipelines stream to only crm.objects.contacts.read |
| 0.6.0 | 2023-04-07 | 24980 | Add new stream DealsArchived |
| 0.5.2 | 2023-04-07 | 24915 | Fix field key parsing (replace whitespace with uderscore) |
| 0.5.1 | 2023-04-05 | 22982 | Specified date formatting in specification |
| 0.5.0 | 2023-03-30 | 24711 | Add incremental sync support for campaigns, deal_pipelines, ticket_pipelines, forms, form_submissions, form_submissions, workflows, owners |
| 0.4.0 | 2023-03-31 | 22910 | Add email_subscriptions stream |
| 0.3.4 | 2023-03-28 | 24641 | Convert to int only numeric values |
| 0.3.3 | 2023-03-27 | 24591 | Fix pagination for marketing emails stream |
| 0.3.2 | 2023-02-07 | 22479 | Turn on default HttpAvailabilityStrategy |
| 0.3.1 | 2023-01-27 | 22009 | Set AvailabilityStrategy for streams explicitly to None |
| 0.3.0 | 2022-10-27 | 18546 | Sunsetting API Key authentication. Quotes stream is no longer available |
| 0.2.2 | 2022-10-03 | 16914 | Fix 403 forbidden error validation |
| 0.2.1 | 2022-09-26 | 17120 | Migrate to per-stream state. |
| 0.2.0 | 2022-09-13 | 16632 | Remove Feedback Submissions stream as the one using unstable (beta) API. |
| 0.1.83 | 2022-09-01 | 16214 | Update Tickets, fix missing properties and change how state is updated. |
| 0.1.82 | 2022-08-18 | 15110 | Check if it has a state on search streams before first sync |
| 0.1.81 | 2022-08-05 | 15354 | Fix Deals stream schema |
| 0.1.80 | 2022-08-01 | 15156 | Fix 401 error while retrieving associations using OAuth |
| 0.1.79 | 2022-07-28 | 15144 | Revert v0.1.78 due to permission issues |
| 0.1.78 | 2022-07-28 | 15099 | Fix to fetch associations when using incremental mode |
| 0.1.77 | 2022-07-26 | 15035 | Make PropertyHistory stream read historic data not limited to 30 days |
| 0.1.76 | 2022-07-25 | 14999 | Partially revert changes made in v0.1.75 |
| 0.1.75 | 2022-07-18 | 14744 | Remove override of private CDK method |
| 0.1.74 | 2022-07-25 | 14412 | Add private app authentication |
| 0.1.73 | 2022-07-13 | 14666 | Decrease number of http requests made, disable Incremental mode for PropertyHistory stream |
| 0.1.72 | 2022-06-24 | 14054 | Extended error logging |
| 0.1.71 | 2022-06-24 | 14102 | Removed legacy AirbyteSentry dependency from the code |
| 0.1.70 | 2022-06-16 | 13837 | Fix the missing data in CRM streams issue |
| 0.1.69 | 2022-06-10 | 13691 | Fix the URI Too Long issue |
| 0.1.68 | 2022-06-08 | 13596 | Fix for the property_history which did not emit records |
| 0.1.67 | 2022-06-07 | 13566 | Report which scopes are missing to the user |
| 0.1.66 | 2022-06-05 | 13475 | Scope crm.objects.feedback_submissions.read added for feedback_submissions stream |
| 0.1.65 | 2022-06-03 | 13455 | Discover only returns streams for which required scopes were granted |
| 0.1.64 | 2022-06-03 | 13218 | Transform contact_lists data to comply with schema |
| 0.1.63 | 2022-06-02 | 13320 | Fix connector incremental state handling |
| 0.1.62 | 2022-06-01 | 13383 | Add line items to deals stream |
| 0.1.61 | 2022-05-25 | 13381 | Requests scopes as optional instead of required |
| 0.1.60 | 2022-05-25 | 13159 | Use RFC3339 datetime |
| 0.1.59 | 2022-05-10 | 12711 | Ensure oauth2.0 token has all needed scopes in “check” command |
| 0.1.58 | 2022-05-04 | 12482 | Update input configuration copy |
| 0.1.57 | 2022-05-04 | 12198 | Add deals associations for quotes |
| 0.1.56 | 2022-05-02 | 12515 | Extra logs for troubleshooting 403 errors |
| 0.1.55 | 2022-04-28 | 12424 | Correct schema for ticket_pipeline stream |
| 0.1.54 | 2022-04-28 | 12335 | Mock time slep in unit test s |
| 0.1.53 | 2022-04-20 | 12230 | Change spec json to yaml format |
| 0.1.52 | 2022-03-25 | 11423 | Add tickets associations to engagements streams |
| 0.1.51 | 2022-03-24 | 11321 | Fix updated at field non exists issue |
| 0.1.50 | 2022-03-22 | 11266 | Fix Engagements Stream Pagination |
| 0.1.49 | 2022-03-17 | 11218 | Anchor hyperlink in input configuration |
| 0.1.48 | 2022-03-16 | 11105 | Fix float numbers, upd docs |
| 0.1.47 | 2022-03-15 | 11121 | Add partition keys where appropriate |
| 0.1.46 | 2022-03-14 | 10700 | Handle 10k+ records reading in Hubspot streams |
| 0.1.45 | 2022-03-04 | 10707 | Remove stage history from deals stream to increase efficiency |
| 0.1.44 | 2022-02-24 | 9027 | Add associations companies to deals, ticket and contact stream |
| 0.1.43 | 2022-02-24 | 10576 | Cast timestamp to date/datetime |
| 0.1.42 | 2022-02-22 | 10492 | Add date-time format to datetime fields |
| 0.1.41 | 2022-02-21 | 10177 | Migrate to CDK |
| 0.1.40 | 2022-02-10 | 10142 | Add associations to ticket stream |
| 0.1.39 | 2022-02-10 | 10055 | Bug fix: reading not initialized stream |
| 0.1.38 | 2022-02-03 | 9786 | Add new streams for engagements(calls, emails, meetings, notes and tasks) |
| 0.1.37 | 2022-01-27 | 9555 | Getting form_submission for all forms |
| 0.1.36 | 2022-01-22 | 7784 | Add Property History Stream |
| 0.1.35 | 2021-12-24 | 9081 | Add Feedback Submissions stream and update Ticket Pipelines stream |
| 0.1.34 | 2022-01-20 | 9641 | Add more fields for email_events stream |
| 0.1.33 | 2022-01-14 | 8887 | More efficient support for incremental updates on Companies, Contact, Deals and Engagement streams |
| 0.1.32 | 2022-01-13 | 8011 | Add new stream form_submissions |
| 0.1.31 | 2022-01-11 | 9385 | Remove auto-generated properties from Engagements stream |
| 0.1.30 | 2021-01-10 | 9129 | Created Contacts list memberships streams |
| 0.1.29 | 2021-12-17 | 8699 | Add incremental sync support for companies, contact_lists, contacts, deals, line_items, products, quotes, tickets streams |
| 0.1.28 | 2021-12-15 | 8429 | Update fields and descriptions |
| 0.1.27 | 2021-12-09 | 8658 | Fix config backward compatibility issue by allowing additional properties in the spec |
| 0.1.26 | 2021-11-30 | 8329 | Remove ‘skip_dynamic_fields’ config param |
| 0.1.25 | 2021-11-23 | 8216 | Add skip dynamic fields for testing only |
| 0.1.24 | 2021-11-09 | 7683 | Fix name issue ‘Hubspot’ -> ‘HubSpot’ |
| 0.1.23 | 2021-11-08 | 7730 | Fix OAuth flow schema |
| 0.1.22 | 2021-11-03 | 7562 | Migrate Hubspot source to CDK structure |
| 0.1.21 | 2021-10-27 | 7405 | Change of package import from urllib to urllib.parse |
| 0.1.20 | 2021-10-26 | 7393 | Hotfix for split_properties function, add the length of separator symbol ,(%2C in HTTP format) to the checking of the summary URL length |
| 0.1.19 | 2021-10-26 | 6954 | Fix issue with getting 414 HTTP error for streams |
| 0.1.18 | 2021-10-18 | 5840 | Add new marketing emails (with statistics) stream |
| 0.1.17 | 2021-10-14 | 6995 | Update discover method: disable quotes stream when using OAuth config |
| 0.1.16 | 2021-09-27 | 6465 | Implement OAuth support. Use CDK authenticator instead of connector specific authenticator |
| 0.1.15 | 2021-09-23 | 6374 | Use correct schema for owners stream |
| 0.1.14 | 2021-09-08 | 5693 | Include deal_to_contact association when pulling deal stream and include contact ID in contact stream |
| 0.1.13 | 2021-09-08 | 5834 | Fix array fields without items property in schema |
| 0.1.12 | 2021-09-02 | 5798 | Treat empty string values as None for field with format to fix normalization errors |
| 0.1.11 | 2021-08-26 | 5685 | Remove all date-time format from schemas |
| 0.1.10 | 2021-08-17 | 5463 | Fix fail on reading stream using API Key without required permissions |
| 0.1.9 | 2021-08-11 | 5334 | Fix empty strings inside float datatype |
| 0.1.8 | 2021-08-06 | 5250 | Fix issue with printing exceptions |
| 0.1.7 | 2021-07-27 | 4913 | Update fields schema |