Skip to main content

HubSpot

Availability
Available CoreAvailable StandardAvailable PlusAvailable ProAvailable Enterprise FlexAvailable Self-Managed EnterpriseAvailable PyAirbyte
Support Level
Airbyte
Connector Version
6.7.0 (last updated a day ago)
Sync Success Rate
Usage Rate
Data workers used
0.2 per sync (Learn more)
Definition ID
36c891d9-4bd9-43ac-bad2-10e12756272c

This page contains the setup guide and reference information for the HubSpot source connector.

Prerequisites​

  • HubSpot Account
  • For Airbyte Open Source: Private App with Access Token

Setup guide​

Step 1: Set up HubSpot​

For Airbyte Cloud:

- OAuth (Recommended). We highly recommend you use OAuth rather than Private App authentication, as it significantly simplifies the setup process.

- Private App: If you are using a Private App, you will need to use your Access Token to set up the connector. Please refer to the official HubSpot documentation to learn how to obtain the access token.

For Airbyte Open Source:

- Private App setup (Recommended): If you are authenticating via a Private App, you will need to use your Access Token to set up the connector. Please refer to the official HubSpot documentation to learn how to obtain the access token.

- OAuth setup: If you are using OAuth to authenticate on Airbyte Open Source, please refer to HubSpot's detailed walkthrough. To set up the connector, you will need to acquire your:

  • Client ID
  • Client Secret
  • Refresh Token

For more details, refer to HubSpot's authentication documentation.

Step 2: Configure the scopes for your streams (Private App only)​

These instructions are only relevant if you are using a Private App for authentication. You can ignore this if you are authenticating via OAuth.

To set up a Private App, you must manually configure scopes to ensure Airbyte can sync all available data. Each scope relates to a specific stream or streams. Refer to HubSpot's documentation on scopes for instructions.

Expand to review scopes
StreamRequired Scope
campaignscontent
companiescrm.objects.companies.read, crm.schemas.companies.read
contact_listscrm.lists.read
contactscrm.objects.contacts.read
contacts_web_analyticscrm.objects.contacts.read, business-intelligence
association_streamsRead scopes for the selected source and target objects
Custom CRM Objectscrm.objects.custom.read
custom_object_association_streamscrm.objects.custom.read and the read scope for any selected standard object
deal_pipelinescrm.objects.contacts.read
dealscrm.objects.deals.read, crm.schemas.deals.read
deals_archivedcrm.objects.deals.read, crm.schemas.deals.read
email_eventscontent
email_subscriptionscontent
engagementscrm.objects.companies.read, crm.objects.contacts.read, crm.objects.deals.read, tickets, e-commerce
engagements_emailssales-email-read
formsforms
form_submissionsforms
goalscrm.objects.goals.read
leadscrm.objects.leads.read, crm.schemas.leads.read
list_membershipscrm.lists.read
line_itemse-commerce
ownerscrm.objects.owners.read
productse-commerce
contacts_property_historycrm.objects.contacts.read
companies_property_historycrm.objects.companies.read
deals_property_historycrm.objects.deals.read
subscription_changescontent
ticketstickets
userscrm.objects.users.read, settings.users.read
account_detailsoauth
deal_splitscrm.objects.deals.read
propertiesNo additional scopes required
workflowsautomation

Step 3: Set up the HubSpot connector in Airbyte​

For Airbyte Cloud:​

  1. Log into your Airbyte Cloud account.
  2. Click Sources and then click + New source.
  3. On the Set up the source page, select HubSpot from the Source type dropdown.
  4. Enter a name for the HubSpot connector.
  5. From the Authentication dropdown, select your chosen authentication method:

    • (Recommended) To authenticate using OAuth, select OAuth and click Authenticate your HubSpot account to sign in with HubSpot and authorize your account.

      HubSpot Authentication issues

      You may encounter an error during the authentication process in the popup window with the message An invalid scope name was provided. To resolve this, close the window and retry authentication.

    • (Not Recommended) To authenticate using a Private App, select Private App and enter the Access Token for your HubSpot account.

  1. (Optional) For Start date, use the provided datepicker or enter the date in the following format: yyyy-mm-ddThh:mm:ssZ. Data added on and after this date will be replicated. If this is not set, "2006-06-01T00:00:00Z" (the date HubSpot was created) will be used as a start date.
  1. (Optional) Set the CRM Search Lookback Window in minutes to re-fetch data for CRM Search streams (e.g. contacts, companies, deals, tickets) for a specified number of minutes before the state from the previous sync. This helps capture missing records in CRM Search streams.
  2. (Optional) Set the Property History Lookback Window in minutes to re-fetch data for property history streams (deals_property_history, contacts_property_history, companies_property_history). This helps capture records that may be missed due to cursor drift caused by HubSpot calculated properties. A value of 43200 (30 days) is a reasonable starting point.
  3. (Optional) Enable Treat dynamic number and boolean properties as strings if your destination rejects records because HubSpot returns values that don't match the declared number or boolean type. See Destination type conversion errors in Troubleshooting for details.
  4. Click Set up source and wait for the tests to complete.

For Airbyte Open Source:​

  1. Navigate to the Airbyte Open Source dashboard.
  2. From the Airbyte UI, click Sources, then click on + New Source and select HubSpot from the list of available sources.
  3. Enter a Source name of your choosing.
  4. From the Authentication dropdown, select your chosen authentication method:
    • (Recommended) To authenticate using a Private App, select Private App and enter the Access Token for your HubSpot account.
    • (Not Recommended:) To authenticate using OAuth, select OAuth and enter your Client ID, Client Secret, and Refresh Token.
  5. (Optional) For Start date, use the provided datepicker or enter the date in the following format: yyyy-mm-ddThh:mm:ssZ. The data added on and after this date will be replicated. If not set, "2006-06-01T00:00:00Z" (HubSpot creation date) will be used as start date. It's recommended to provide a start date relevant to your data to optimize synchronization.
  6. (Optional) Set the CRM Search Lookback Window in minutes to re-fetch data for CRM Search streams (e.g. contacts, companies, deals, tickets) for a specified number of minutes before the state from the previous sync. This helps capture missing records in CRM Search streams.
  7. (Optional) Set the Property History Lookback Window in minutes to re-fetch data for property history streams (deals_property_history, contacts_property_history, companies_property_history). This helps capture records that may be missed due to cursor drift caused by HubSpot calculated properties. A value of 43200 (30 days) is a reasonable starting point.
  8. (Optional) Enable Treat dynamic number and boolean properties as strings if your destination rejects records because HubSpot returns values that don't match the declared number or boolean type. See Destination type conversion errors in Troubleshooting for details.
  9. Click Set up source and wait for the tests to complete.

Experimental streams​

Web Analytics streams may be enabled as an experimental feature. Note that these streams use a HubSpot API that is currently in beta, and they may be modified or unstable as the API continues to develop.

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 one stream that reads IDs from the source object, 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, deals, or contacts.
  • To Object: The target object type, such as companies or contacts.
  • Stream Name: Optional. If you leave this empty, Airbyte names the stream associations_<from_object>_<to_object>.

For example, set From Object to tickets and To Object to companies to create the associations_tickets_companies stream. After you add or edit association stream settings, refresh the source schema so the generated streams appear in the catalog.

Association stream records include:

  • from_id: The ID of the source object record.
  • to_id: The ID of the target object record.
  • association_type_id: HubSpot's numeric association type identifier.
  • category: The association category, such as HUBSPOT_DEFINED or USER_DEFINED.
  • label: The association label. This is null for unlabeled associations.

Association streams sync incrementally. Only associations for records modified since the last sync are fetched.

If you authenticate with a Private App, grant read scopes for both selected objects. For example, a tickets-to-companies association stream needs the tickets and crm.objects.companies.read scopes.

Custom object association streams​

Use Custom Object Association Streams to sync relationships where at least one side is a custom HubSpot object. Add one item for each relationship you want to sync.

Configure these fields for each custom object association stream:

  • From Object: The source object name or identifier.
  • To Object: The target object name or identifier.
  • Stream Name: Optional. If you leave this empty, Airbyte names the stream associations_<from_object>_<to_object>.

After you add or edit custom object association stream settings, refresh the source schema so the generated streams appear in the catalog.

For custom objects, use either:

  • The custom object's fullyQualifiedName, such as p_my_custom_object.
  • The custom object's objectTypeId, such as 2-12345.

You can use standard object names, such as contacts, companies, or deals, for the standard-object side of the relationship.

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 incrementally, the same way as standard association streams.

If you authenticate with a Private App, grant crm.objects.custom.read and the read scope for any standard object in the relationship.

Supported sync modes​

The HubSpot source connector supports the following sync modes:

  • Full Refresh
  • Incremental
note

There are two types of incremental sync:

  1. Incremental (standard server-side, where API returns only the data updated or generated since the last sync)
  2. Client-Side Incremental (API returns all available data and connector filters out only new records)

Supported Streams​

The HubSpot source connector supports the following streams:

Entity-Relationship Diagram (ERD)​

Notes on the property_history streams​

The property history streams (contacts_property_history, companies_property_history, deals_property_history) use Client-Side Incremental sync with a cursor timestamp to determine which records have changed since the previous sync.

HubSpot calculated properties — formula fields, rollup summaries, and analytics properties such as hs_analytics_* — always have a timestamp that mirrors the time of the latest sync, not the time of the last user-initiated change. This causes the sync cursor to advance past records that have not yet been synced, which can result in missing records.

To mitigate this, configure the Property History Lookback Window in the source settings. A value of 43200 (30 days) is a reasonable starting point. Because these streams use Append + Deduped sync mode, duplicate records from the lookback period are handled automatically.

Notes on the engagements stream​

  1. Objects in the engagements stream can have one of the following types: note, email, task, meeting, call. Depending on the type of engagement, different properties are set for that object in the engagements_metadata table in the destination:
  • A call engagement has a corresponding engagements_metadata object with non-null values in the toNumber, fromNumber, status, externalId, durationMilliseconds, externalAccountId, recordingUrl, body, and disposition columns.
  • An email engagement has a corresponding engagements_metadata object with non-null values in the subject, html, and text columns. In addition, there will be records in four related tables, engagements_metadata_from, engagements_metadata_to, engagements_metadata_cc, engagements_metadata_bcc.
  • A meeting engagement has a corresponding engagements_metadata object with non-null values in the body, startTime, endTime, and title columns.
  • A note engagement has a corresponding engagements_metadata object with non-null values in the body column.
  • A task engagement has a corresponding engagements_metadata object with non-null values in the body, status, and forObjectType columns.
  1. The engagements stream uses two different APIs based on the length of time since the last sync and the number of records which Airbyte hasn't yet synced.
  • EngagementsRecent if the following two criteria are met:
    • The last sync was performed within the last 30 days
    • Fewer than 10,000 records are being synced
  • EngagementsAll if either of these criteria are not met.

Because of this, the engagements stream can be slow to sync if it hasn't synced within the last 30 days and/or is generating large volumes of new data. To accommodate for this limitation, we recommend scheduling more frequent syncs.

Notes on the Forms and Form Submissions stream​

This stream only syncs marketing forms.

Notes on the list_memberships stream​

The list_memberships stream reads memberships for every list returned by the contact_lists stream by calling HubSpot's GET /crm/v3/lists/{listId}/memberships endpoint. A few behaviors are worth knowing about:

  • The stream only supports full refresh. HubSpot's memberships endpoint doesn't expose a cursor suitable for incremental sync.
  • Records are keyed by the composite primary key (recordId, listId). listId is emitted as a string so records serialize cleanly to Avro destinations.
  • Some lists returned by contact_lists reference an objectTypeId that isn't active for your portal (for example, Leads lists with objectTypeId 0-136). HubSpot's memberships endpoint rejects those lists with a 400 VALIDATION_ERROR / ListError.INVALID_OBJECT_TYPE_FOR_LIST. The connector skips those lists so they don't fail the sync, and logs an entry for each one. If you need memberships for those object types, enable the corresponding object in HubSpot or sync the object directly from its own stream (for example, leads).

Notes on the Custom CRM Objects​

Custom CRM Objects and Custom Web Analytics will appear as streams available for sync, alongside the standard objects listed above.

If you set up your connections before April 15th, 2023 (on Airbyte Cloud) or before 0.8.0 (OSS) then you'll need to do some additional work to sync custom CRM objects.

First you need to give the connector some additional permissions:

  • If you are using OAuth on Airbyte Cloud go to the HubSpot source settings page in the Airbyte UI and re-authenticate via OAuth to allow Airbyte the permissions to access custom objects.

  • If you are using OAuth on OSS or Private App auth go into the HubSpot UI where you created your Private App or OAuth application and add the crm.objects.custom.read scope to your app's scopes. See HubSpot's scopes documentation.

Then, go to the schema tab of your connection and click refresh source schema to pull in those new streams for syncing.

Limitations & Troubleshooting​

Expand to see details about HubSpot connector limitations and troubleshooting.

Rate limiting​

The connector is restricted by normal HubSpot rate limits. The burst limit applies per app, and the daily limit is shared across all apps within the same HubSpot account.

Product tierBurst (per 10 seconds)Daily (per account)
Free & Starter100250,000
Professional190625,000
Enterprise1901,000,000
API Limit Increase add-on250+1,000,000 per add-on (max 2)

Custom properties sync slowly​

If you use custom properties in HubSpot, syncs take longer. Airbyte doesn't alert you to the presence of custom properties, but you can check if you're using them with HubSpot's UI.

Troubleshooting​

  • Enabling streams: Some streams, such as workflows, require specific scopes before they can be read. If the authenticated user does not have the necessary permissions, the connector logs a warning and skips the stream.

  • HubSpot object labels In HubSpot, a label can be applied to a stream that differs from the original API name of the stream. HubSpot's UI shows the label of the stream, whereas Airbyte shows the name of the stream. If you are having issues seeing a particular stream your user should have access to, search for the name of the HubSpot object instead.

  • Unnesting top level properties: Since version 1.5.0, in order to offer users access to nested fields, we also denest the top-level fields into individual fields in the destination. This is most commonly observed in the properties field, which is now split into each attribute in the destination.

    For instance:

    {
      "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)

    If you authenticate using a Private App access token and receive a 401 Unauthorized error, the connector fails immediately with a configuration error asking you to update your token. Private App tokens are static and cannot be refreshed, so retrying won't help. To resolve this, generate a new access token in your HubSpot Private App settings and update the connector configuration.

    If you authenticate using OAuth, the connector automatically refreshes expired tokens and retries the request. No action is needed unless the error persists, in which case you should re-authenticate the connector.

  • 403 Forbidden Error

    • HubSpot has scopes for each API call.

    • Each stream is tied to a scope and will need access to that scope to sync data.

    • Review HubSpot's OAuth scope documentation.

    • Additional permissions:

      feedback_submissions: Service Hub Professional account

      marketing_emails: Market Hub Starter account

      workflows: Sales, Service, and Marketing Hub Professional accounts

  • Check out common troubleshooting issues for the HubSpot source connector on our 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):

    • If you notice missing records during incremental syncs, it may be due to irregularities in HubSpot's API behavior.
    • To mitigate this, configure the CRM Search Lookback Window in the source settings. This re-fetches data for a specified number of minutes before the state from the previous sync, helping to capture missing records.

  • Missing records in property history streams (deals_property_history, contacts_property_history, companies_property_history):

    • HubSpot calculated properties (formula fields, rollup summaries, analytics properties) can emit timestamps ahead of user-initiated changes, causing the sync cursor to advance past records that have not yet been synced.
    • To mitigate this, configure the Property History Lookback Window in the source settings. A value of 43200 (30 days) is recommended. Since these streams use Append + Deduped sync mode, duplicate records from the lookback period are handled automatically.

  • Destination type conversion errors on dynamic number / boolean properties (for example, JSON → NUMERIC, JSON → BOOL, or decimal-precision / scale errors on fields like hs_hd_ticket_ids, zendesk_requester_id, hs_task_send_default_reminder, or any companies.properties.* field):

    • HubSpot sometimes declares a property as number or boolean but returns values that cannot be cast to that type — for example, semicolon-separated IDs ("3092727991;3881228353;15895321999") in a number field, multi-value text in a boolean field, or numbers beyond the declared precision. When that happens the connector emits the raw string, but because the published schema still says number / boolean, 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. When this option is on, the connector declares every HubSpot dynamic property that would otherwise be number or boolean as string, so the affected values land in the destination as strings rather than failing type conversion.
    • The toggle only affects HubSpot dynamic properties.* fields. Static schema fields and non-property fields are not changed.
    • After enabling the toggle you must refresh both the schema and the data, otherwise the new string type will not reach the destination. In the Airbyte UI:
      1. Open the affected connection.
      2. Click Refresh source schema and save the updated catalog — the affected columns should now be string.
      3. Trigger a Refresh data sync (or clear the affected streams and run a new sync) so the destination tables are rewritten with the new column type and previously-rejected records are re-emitted as strings.
    • The same steps apply if you later disable the toggle — refresh the schema and the data so the destination column types match the new catalog.

IP allow list​

If you use Airbyte Cloud and your organization restricts access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.

Reference​

Config fields reference

Field
Type
Property name
object
credentials
array<object>
association_streams
array<object>
custom_object_association_streams
boolean
enable_experimental_streams
integer
lookback_window
integer
num_worker
integer
property_history_lookback_window
string
start_date
boolean
treat_numbers_and_booleans_as_strings

Changelog​

Expand to review
VersionDatePull RequestSubject
6.7.02026-06-1176396Add treat_numbers_and_booleans_as_strings config toggle to coerce dynamic number/boolean properties to string
6.6.12026-06-1079636Add 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.02026-06-0871259Add association streams for standard and custom objects, including optional OAuth scopes needed to support them
6.5.52026-04-2876323Add failure_type classification to list_memberships error handler response filters
6.5.42026-04-2176848Fix OAuth optional_scopes to align with connector streams
6.5.32026-04-2176073Update CDK to pre-release with deadlock fix
6.5.22026-04-2176641Update dependencies
6.5.12026-04-2076395Emit 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.02026-04-1475281Add new list_memberships stream via V3 Lists API
6.4.42026-04-1376276Rename "concurrent workers" to "concurrent threads" in connector spec
6.4.32026-04-0876149Added missing OAuth scopes crm.objects.users.read and settings.users.read for the users stream
6.4.22026-04-0676096Remove registry version overrides pinning to 6.3.1, fix stream count test assertions
6.4.12026-04-0375574Add oauth_connector_input_specification with granular scopes and optional_scopes
6.4.02026-04-0170920Add new stream Users
6.3.52026-03-3175665Update dependencies
6.3.42026-03-3075595Fixed HTTP 429 responses mapped to RETRY instead of RATE_LIMITED, enabling correct rate-limit handling
6.3.32026-03-2675452Fixed HTTP 401 errors retrying indefinitely for Private App Token authentication
6.3.22026-03-1774526Update dependencies
6.3.12026-03-0974410Promoting release candidate 6.3.1-rc.1 to a main version.
6.3.1-rc.12026-03-0374032fix(source-hubspot): use v3 properties API for CRM search streams
6.3.02026-03-0361703Add new stream account_details
6.2.22026-02-2473909Update dependencies
6.2.12026-02-1773491Update dependencies
6.2.02026-03-0361704Add new properties stream
6.1.12026-02-1070486Update dependencies
6.1.02026-02-0672906Promoting release candidate 6.1.0-rc.2 to a main version.
6.1.0-rc.22026-02-0372799Bump the CDK version which fixed a bug where streams without incremental showed a cursor
6.1.0-rc.12025-12-0969782Allow for user defined cursor field key in the configured catalog for incremental streams
6.0.152025-11-2570053Update dependencies
6.0.142025-11-2469803Add missing fields in Marketing Emails stream for Avro/Parquet conversions
6.0.132025-11-1969749Fix retrieving associations for CRMSearch streams
6.0.122025-11-1969203Add lookback window
6.0.112025-11-1869381Update dependencies
6.0.102025-11-0369145Promoting release candidate 6.0.10-rc.1 to a main version.
6.0.10-rc.12025-10-3068610Add APIBudget
6.0.92025-10-2969077Promoting release candidate 6.0.9-rc.1 to a main version.
6.0.9-rc.12025-10-2768665Improve performance following CDK release 7.4.1
6.0.82025-10-2768662Promoting release candidate 6.0.8-rc.1 to a main version.
6.0.8-rc.12025-10-2263744Switch all CRMSearch streams to use incremental endpoint for server-side filtering, even during full refresh
6.0.72025-10-2168582Promoting release candidate 6.0.7-rc.1 to a main version.
6.0.7-rc.12025-10-2068159Upgrade to latest version of CDK 7.3.7 to get the bug fix for missing custom properties during incremental syncs
6.0.62025-10-1467911Update dependencies
6.0.52025-10-0767400Update dependencies
6.0.42025-09-3066409Update dependencies
6.0.32025-09-2566700Revert to 6.0.1
6.0.22025-09-1565947Set fallback target type to 'string' for numbers and booleans
6.0.12025-09-0966100Update dependencies
6.0.02025-09-0265100Migrate 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.202025-08-2565513Add missing datetime format
5.8.192025-08-2365327Update dependencies
5.8.182025-08-0964603Update dependencies
5.8.172025-08-0364197Update dependencies
5.8.162025-07-2663898Update dependencies
5.8.152025-07-2163341Bump memory on Discover to 1GB
5.8.142025-07-1963499Update dependencies
5.8.132025-07-1263115Update dependencies
5.8.122025-07-0862866Handle non-numeric values in fields with declared numeric type
5.8.112025-07-0762838Promoting release candidate 5.8.11-rc.1 to a main version.
5.8.11-rc.12025-07-0262481For CRMSearch streams, fix retry behavior for the underlying associations HttpRequester to retry 401 errors
5.8.102025-06-2862179Update dependencies
5.8.92025-06-2161842Update dependencies
5.8.82025-06-1460640Update dependencies
5.8.72025-06-1161543Fix pagination for contacts and other CRM Search streams when paginating past 10,000 records streams
5.8.62025-06-1061502Set cursor based pagination for CRM object streams
5.8.52025-06-0261326Additional change for millisecond float timestamps
5.8.42025-05-3061013Fix Typo
5.8.32025-05-3061007Bump memory on Check to 1600mi
5.8.22025-05-2960962Fix bug to allow millisecond timestamps coming in as a float string to be parsed into a datetime.
5.8.12025-05-2860937Retry 401 Unauthorized errors since token might have just expired.
5.8.02025-05-2860855Migrate to manifest-only
5.7.02025-05-2760919Promoting release candidate 5.7.0-rc.2 to a main version.
5.7.0-rc.22025-05-2360881Ignore 403 errors for dynamic streams to prevent sync failures
5.7.0-rc.12025-05-2260830Migrate CustomObjects streams
5.6.02025-05-2160338Migrate CRM search streams: contacts, deal_splits, leads, tickets
5.5.02025-05-2160812Migrate CRM search companies stream
5.4.02025-05-2059727Migrate CRM object streams: goals, product, line_items
5.3.02025-05-1660249Migrate engagements_calls, engagements_emails, engagements_meetings, engagements_notes, engagements_tasks to low code
5.2.02025-05-1560306Promoting release candidate 5.2.0-rc.1 to a main version.
5.2.0-rc.12025-05-1459127Migrate deals to low code
5.1.02025-05-1460276Promoting release candidate 5.1.0-rc.1 to a main version.
5.1.0-rc.12025-05-1358105Migrate deals_archived, forms, form_submissions, owners, owners_archived to low-code
5.0.02025-05-1259673Deprecate 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.22025-05-0959755Add missing cursor format for workflows stream state migration
4.12.12025-05-1059810Update dependencies
4.12.02025-05-0958592Migrate incremental streams: email_events, engagements, subscription_changes
4.11.02025-05-0759216Migrate workflows to low code
4.10.02025-05-0759195Migrate deal_pipelines to low code
4.9.02025-05-0758135Migrate campaigns to low code
4.8.02025-05-0659693Promoting release candidate 4.8.0-rc.1 to a main version.
4.8.0-rc.12025-04-3058092Migrate companies_property_history, contacts_property_history and deals_property_history to low code
4.7.02025-04-3059165Promoting release candidate 4.7.0-rc.2 to a main version.
4.7.0-rc.22025-04-2859118Add empty string state migration
4.7.0-rc.12025-04-2358083Migrate ticket_pipelines to low code
4.6.42025-04-2258138Use short-hand custom object type name path for custom object streams.
4.6.32025-04-1958226Update dependencies
4.6.22025-04-1858137Promoting release candidate 4.6.2-rc.1 to a main version.
4.6.2-rc.12025-04-1357534Migrate marketing_emails and email_subscriptions to low code
4.6.12025-04-1257694Update dependencies
4.6.02025-04-1157572Promoting release candidate 4.6.0-rc.1 to a main version.
4.6.0-rc.12025-03-3156919Update CDK to v6
4.5.62025-03-2956647Update dependencies
4.5.52025-03-2656416Disabled blog_comment and all form-types for Forms and FormSubmissions stream
4.5.42025-03-2555822add userIdIncludingInactive to owners and owners_archived streams
4.5.32025-03-2455245Add conversionId to form_submissions schema
4.5.22024-12-1449141Improves Forms stream by adding the formTypes query parameter to support all form types. This enhancement also propagates to the FormSubmission stream.
4.5.12025-03-2253818Update dependencies
4.5.02025-03-1054177Add option to cast fields from stream json schema per list of fields
4.4.92025-02-0152729Update dependencies
4.4.82025-01-2552295Update dependencies
4.4.72025-01-1151146Update dependencies
4.4.62025-01-0450898Update dependencies
4.4.52024-12-2850669Update dependencies
4.4.42024-12-2150138Update dependencies
4.4.32024-12-1448984Update dependencies
4.4.22024-12-1048480Adds individual read scopes to LineItems Stream
4.4.12024-11-2548662Starting 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.02024-11-1848548Promoting release candidate 4.4.0-rc.1 to a main version.
4.4.0-rc.12024-11-1848472Adds 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.02024-11-1544481Add Leads stream
4.2.262024-11-0448199Update dependencies
4.2.252024-10-2947028Update dependencies
4.2.242024-10-1246827Update dependencies
4.2.232024-10-0546494Update dependencies
4.2.222024-09-2846160Update dependencies
4.2.212024-09-2344899Fix incremental search to use primary key as placeholder instead of lastModifiedDate
4.2.202024-09-2145753Update dependencies
4.2.192024-09-1445018Update dependencies
4.2.182024-08-2443762Update dependencies
4.2.172024-08-2144538Fix issue with CRM search streams when they have no associations
4.2.162024-08-2042919Add support for Deal Splits
4.2.152024-08-0843381Fix associations retrieval for Engagements streams (calls, meetings, notes, tasks, emails) in Incremental with existing state
4.2.142024-07-2742688Update dependencies
4.2.132024-07-2042264Update dependencies
4.2.122024-07-1341766Update dependencies
4.2.112024-07-1041558Update dependencies
4.2.102024-07-0941286Update dependencies
4.2.92024-07-0841045Use latest CDK version possible
4.2.82024-07-0640923Update dependencies
4.2.72024-06-2540441Update dependencies
4.2.62024-06-2240126Update dependencies
4.2.52024-06-1739432Remove references to deprecated state method
4.2.42024-06-1038800Retry hubspot _parse_and_handle_errors on JSON decode errors
4.2.32024-06-0639314Added missing schema types for the Workflows stream schema
4.2.22024-06-0438981[autopull] Upgrade base image to v1.2.1
4.2.12024-05-3038024Retry when attempting to get scopes
4.2.02024-05-2438049Add resumable full refresh support to contacts_form_submissions and contacts_merged_audit streams
4.1.52024-05-1738243Replace AirbyteLogger with logging.Logger
4.1.42024-05-1638286Added default schema normalization for the Tickets stream, to ensure the data types
4.1.32024-05-1338128contacts_list_memberships as semi-incremental stream
4.1.22024-04-2436642Schema descriptions and CDK 0.80.0
4.1.12024-04-1135945Add integration tests
4.1.02024-03-2736541Added test configuration features, fixed type hints
4.0.02024-03-1035662Update Deals Property History and Companies Property History schemas
3.3.02024-02-1634597Make start date not required, sync all data from default value if it's not provided
3.2.02024-02-1535328Add mailingIlsListsIncluded and mailingIlsListsExcluded fields to Marketing emails stream schema
3.1.12024-02-1235165Manage dependencies with Poetry.
3.1.02024-02-0534829Add Contacts Form Submissions stream
3.0.12024-01-2934635Fix pagination for CompaniesPropertyHistory stream
3.0.02024-01-2534492Update marketing_emails stream schema
2.0.22023-12-1533844Make property_history PK combined to support Incremental/Deduped sync type
2.0.12023-12-1533527Make query string calculated correctly for PropertyHistory streams to avoid 414 HTTP Errors
2.0.02023-12-0833266Add ContactsPropertyHistory, CompaniesPropertyHistory, DealsPropertyHistory streams
1.9.02023-12-0433042Add Web Analytics streams
1.8.02023-11-2332778Extend PropertyHistory stream to support incremental sync
1.7.02023-11-0132035Extend the Forms stream schema
1.6.12023-10-2031644Base image migration: remove Dockerfile and use the python-connector-base image
1.6.02023-10-1931606Add new field aifeatures to the marketing emails stream schema
1.5.12023-10-0431050Add type transformer for Engagements stream
1.5.02023-09-1130322Unnest stream schemas
1.4.12023-08-2229715Fix python package configuration stream
1.4.02023-08-1129249Add OwnersArchived stream
1.3.32023-08-1029248Specify threadId in engagements stream to type string
1.3.22023-08-1029326Add primary keys to streams ContactLists and PropertyHistory
1.3.12023-08-0829211Handle 400 and 403 errors without interruption of the sync
1.3.02023-08-0128909Add handling of source connection errors
1.2.02023-07-2727091Add new stream ContactsMergedAudit
1.1.22023-07-2728558Improve error messages during connector setup
1.1.12023-07-2528705Fix retry handler for token expired error
1.1.02023-07-1828349Add unexpected fields in schemas of streams email_events, email_subscriptions, engagements, campaigns
1.0.12023-06-2327658Use fully qualified name to retrieve custom objects
1.0.02023-06-0827161Fix 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.02023-06-2627726License Update: Elv2
0.8.42023-05-1726082Fixed bug with wrong parsing of boolean encoded like "false" parsed as True
0.8.32023-05-3126831Remove authSpecification from connector specification in favour of advancedAuth
0.8.22023-05-1626418Add custom availability strategy which catches permission errors from parent streams
0.8.12023-05-2926719Handle issue when state value is literally "" (empty str)
0.8.02023-04-1016032Add new stream Custom Object
0.7.02023-04-1024450Add new stream Goals
0.6.22023-04-2825667Fix bug with Invalid Date like 2000-00-00T00:00:00Z while settip up the connector
0.6.12023-04-1021423Update scope for DealPipelines stream to only crm.objects.contacts.read
0.6.02023-04-0724980Add new stream DealsArchived
0.5.22023-04-0724915Fix field key parsing (replace whitespace with uderscore)
0.5.12023-04-0522982Specified date formatting in specification
0.5.02023-03-3024711Add incremental sync support for campaigns, deal_pipelines, ticket_pipelines, forms, form_submissions, form_submissions, workflows, owners
0.4.02023-03-3122910Add email_subscriptions stream
0.3.42023-03-2824641Convert to int only numeric values
0.3.32023-03-2724591Fix pagination for marketing emails stream
0.3.22023-02-0722479Turn on default HttpAvailabilityStrategy
0.3.12023-01-2722009Set AvailabilityStrategy for streams explicitly to None
0.3.02022-10-2718546Sunsetting API Key authentication. Quotes stream is no longer available
0.2.22022-10-0316914Fix 403 forbidden error validation
0.2.12022-09-2617120Migrate to per-stream state.
0.2.02022-09-1316632Remove Feedback Submissions stream as the one using unstable (beta) API.
0.1.832022-09-0116214Update Tickets, fix missing properties and change how state is updated.
0.1.822022-08-1815110Check if it has a state on search streams before first sync
0.1.812022-08-0515354Fix Deals stream schema
0.1.802022-08-0115156Fix 401 error while retrieving associations using OAuth
0.1.792022-07-2815144Revert v0.1.78 due to permission issues
0.1.782022-07-2815099Fix to fetch associations when using incremental mode
0.1.772022-07-2615035Make PropertyHistory stream read historic data not limited to 30 days
0.1.762022-07-2514999Partially revert changes made in v0.1.75
0.1.752022-07-1814744Remove override of private CDK method
0.1.742022-07-2514412Add private app authentication
0.1.732022-07-1314666Decrease number of http requests made, disable Incremental mode for PropertyHistory stream
0.1.722022-06-2414054Extended error logging
0.1.712022-06-2414102Removed legacy AirbyteSentry dependency from the code
0.1.702022-06-1613837Fix the missing data in CRM streams issue
0.1.692022-06-1013691Fix the URI Too Long issue
0.1.682022-06-0813596Fix for the property_history which did not emit records
0.1.672022-06-0713566Report which scopes are missing to the user
0.1.662022-06-0513475Scope crm.objects.feedback_submissions.read added for feedback_submissions stream
0.1.652022-06-0313455Discover only returns streams for which required scopes were granted
0.1.642022-06-0313218Transform contact_lists data to comply with schema
0.1.632022-06-0213320Fix connector incremental state handling
0.1.622022-06-0113383Add line items to deals stream
0.1.612022-05-2513381Requests scopes as optional instead of required
0.1.602022-05-2513159Use RFC3339 datetime
0.1.592022-05-1012711Ensure oauth2.0 token has all needed scopes in "check" command
0.1.582022-05-0412482Update input configuration copy
0.1.572022-05-0412198Add deals associations for quotes
0.1.562022-05-0212515Extra logs for troubleshooting 403 errors
0.1.552022-04-2812424Correct schema for ticket_pipeline stream
0.1.542022-04-2812335Mock time slep in unit test s
0.1.532022-04-2012230Change spec json to yaml format
0.1.522022-03-2511423Add tickets associations to engagements streams
0.1.512022-03-2411321Fix updated at field non exists issue
0.1.502022-03-2211266Fix Engagements Stream Pagination
0.1.492022-03-1711218Anchor hyperlink in input configuration
0.1.482022-03-1611105Fix float numbers, upd docs
0.1.472022-03-1511121Add partition keys where appropriate
0.1.462022-03-1410700Handle 10k+ records reading in Hubspot streams
0.1.452022-03-0410707Remove stage history from deals stream to increase efficiency
0.1.442022-02-249027Add associations companies to deals, ticket and contact stream
0.1.432022-02-2410576Cast timestamp to date/datetime
0.1.422022-02-2210492Add date-time format to datetime fields
0.1.412022-02-2110177Migrate to CDK
0.1.402022-02-1010142Add associations to ticket stream
0.1.392022-02-1010055Bug fix: reading not initialized stream
0.1.382022-02-039786Add new streams for engagements(calls, emails, meetings, notes and tasks)
0.1.372022-01-279555Getting form_submission for all forms
0.1.362022-01-227784Add Property History Stream
0.1.352021-12-249081Add Feedback Submissions stream and update Ticket Pipelines stream
0.1.342022-01-209641Add more fields for email_events stream
0.1.332022-01-148887More efficient support for incremental updates on Companies, Contact, Deals and Engagement streams
0.1.322022-01-138011Add new stream form_submissions
0.1.312022-01-119385Remove auto-generated properties from Engagements stream
0.1.302021-01-109129Created Contacts list memberships streams
0.1.292021-12-178699Add incremental sync support for companies, contact_lists, contacts, deals, line_items, products, quotes, tickets streams
0.1.282021-12-158429Update fields and descriptions
0.1.272021-12-098658Fix config backward compatibility issue by allowing additional properties in the spec
0.1.262021-11-308329Remove 'skip_dynamic_fields' config param
0.1.252021-11-238216Add skip dynamic fields for testing only
0.1.242021-11-097683Fix name issue 'Hubspot' -> 'HubSpot'
0.1.232021-11-087730Fix OAuth flow schema
0.1.222021-11-037562Migrate Hubspot source to CDK structure
0.1.212021-10-277405Change of package import from urllib to urllib.parse
0.1.202021-10-267393Hotfix for split_properties function, add the length of separator symbol ,(%2C in HTTP format) to the checking of the summary URL length
0.1.192021-10-266954Fix issue with getting 414 HTTP error for streams
0.1.182021-10-185840Add new marketing emails (with statistics) stream
0.1.172021-10-146995Update discover method: disable quotes stream when using OAuth config
0.1.162021-09-276465Implement OAuth support. Use CDK authenticator instead of connector specific authenticator
0.1.152021-09-236374Use correct schema for owners stream
0.1.142021-09-085693Include deal_to_contact association when pulling deal stream and include contact ID in contact stream
0.1.132021-09-085834Fix array fields without items property in schema
0.1.122021-09-025798Treat empty string values as None for field with format to fix normalization errors
0.1.112021-08-265685Remove all date-time format from schemas
0.1.102021-08-175463Fix fail on reading stream using API Key without required permissions
0.1.92021-08-115334Fix empty strings inside float datatype
0.1.82021-08-065250Fix issue with printing exceptions
0.1.72021-07-274913Update fields schema
Was this page helpful?