HubSpot Feeds

HubSpot is a cloud-based CRM platform that unifies marketing, sales, service, and content management around a shared database of CRM objects such as contacts, companies, and deals. The HubSpot Feeds connector is a source-only ELT connector that ingests multiple HubSpot CRM objects as a set of feeds from the HubSpot CRM v3 API. Select the standard objects you want — including Companies, Contacts, Deals, Invoices, Leads, Line Items, Products, Quotes, Tickets, and Users — and Nexla ingests each selected object as its own feed on a schedule, using either a full-refresh or an incremental-sync strategy.

Power end-to-end data operations for your HubSpot Feeds API with Nexla. Our bi-directional HubSpot Feeds connector is purpose-built for HubSpot Feeds, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to HubSpot Feeds or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your HubSpot Feeds workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

The HubSpot Feeds connector reads from the HubSpot CRM v3 API. You can connect using any of three authentication methods, and the credential fields you supply depend on the method you choose:

• Nexla public app (OAuth2): Authorize Nexla's HubSpot app directly from the credential screen. No client credentials or tokens are entered by hand — you approve access in HubSpot and are redirected back to Nexla. Choose this method for the fastest setup.
• Your own HubSpot app (OAuth2): Use a HubSpot developer app that you own, supplying its Client ID, Client Secret, and scopes. Choose this method when your organization requires the integration to run under an app you control.
• HubSpot private app (access token): Use a private app access token generated inside your HubSpot account. Choose this method for a simple, token-based connection that does not require a developer account.

Whichever method you use, the connecting identity must have read access to the CRM objects you plan to ingest.

Create a HubSpot private app access token

Private apps are the simplest way to obtain a long-lived access token. You must be a super admin in the HubSpot account to create one.

1. Sign in to your HubSpot account as a super admin.

2. Click the settings (gear) icon in the top navigation bar.

3. In the left sidebar, navigate to Integrations > Private Apps.

4. Click Create a private app.

5. On the Basic Info tab, enter a name and optional description for the app (for example, Nexla Integration).

6. Open the Scopes tab and add the read scopes for the CRM objects you plan to ingest — for example, crm.objects.contacts.read, crm.objects.companies.read, crm.objects.deals.read, crm.objects.line_items.read, crm.objects.quotes.read, and tickets. Grant only the scopes you need.

7. Click Create app in the top right, and confirm creation in the dialog.

8. On the app's Auth tab, under Access token, click Show token, then Copy to copy the token.

   Important

   Copy and store the access token securely. HubSpot displays the full token only once; afterward you can view only a masked version or generate a new token.

Create a HubSpot OAuth2 app

Use this option if you plan to authenticate with your own HubSpot app rather than the Nexla public app.

1. Sign in to (or create) a HubSpot developer account.

2. From the developer dashboard, click Create an app.

3. On the App info tab, enter a name and other basic details for the app.

4. Open the Auth tab to view the app's Client ID and Client secret. Copy both values for use in your Nexla credential.

5. On the same tab, add the read scopes required for the CRM objects you plan to ingest.

Treat the private app access token and the OAuth2 Client Secret as sensitive secrets. Store them securely, grant only the scopes you need, and rotate them if they are exposed. For more information, see the HubSpot private apps documentation, the HubSpot OAuth documentation, and the HubSpot API overview.

Authenticate

Credentials required

HubSpot OAuth2 Authentication

Use this authentication method for 3-legged OAuth2 authentication using your own Hubspot App.

Field	Required	Secret	Description
Client ID	Yes	Yes	Your HubSpot App Client ID
Client Secret	Yes	Yes	Your HubSpot App Client Secret
Scopes	Yes	No	Space-separated list of required scopes (e.g., crm.objects.contacts.read)

Hubspot Private App Authentication

Use this authentication method to connect to Hubspot using the Hubspot private app.

Field	Required	Secret	Description
Private App Access Token	Yes	Yes	Please enter the access token for your Hubspot private app.

A third method, Nexla Public App Authentication, connects to HubSpot using Nexla's public HubSpot app via OAuth2. It has no user-supplied credential fields — you authorize access to your HubSpot account directly from the credential screen and are redirected back to Nexla.

Create a credential in Nexla

1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

   Resource descriptions are recommended but are not required. Use them to identify the HubSpot account, environment, or access level represented by this credential.

3. Select the authentication method you want to use:

   • Nexla Public App Authentication: Click the authorization option, sign in to HubSpot, and approve access for Nexla's HubSpot app. You are redirected back to Nexla once access is granted. No further fields are required.

   • HubSpot OAuth2 Authentication: Enter the Client ID and Client Secret from your HubSpot developer app, confirm the Scopes to request, then complete the OAuth authorization prompt to link the app to your HubSpot account.

   • Hubspot Private App Authentication: Enter the access token you generated in Prerequisites in the Private App Access Token field.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation and can be selected for use with HubSpot Feeds flows.

Use as a data source

How This Connector Works

The HubSpot Feeds connector is a source-only, multi-object ELT connector. Rather than configuring one endpoint at a time, you select the HubSpot CRM objects you want, and Nexla ingests each selected object as its own feed from the HubSpot CRM v3 API.

• Discovery: When you create the source, Nexla lists the standard HubSpot objects available from your account so you can choose which ones to ingest.

• Sync strategy: Each feed can be ingested with one of two strategies — a Full Refresh that reads the complete current set of records for the object on every run, or an Incremental Sync that reads only records changed within a lookback window.

• Primary key: HubSpot's internal hs_object_id is used as the primary key to uniquely identify records within each feed.

• Parallel ingestion: Selected feeds are ingested in parallel, so a single source can pull many HubSpot objects on the same schedule.

Create a New Data Flow

1. To create a new data flow, navigate to the Integrate section, click the New Data Flow button, select the ELT flow type, and click Create.

2. Select the HubSpot Feeds connector tile from the list of available connectors. Then, select the credential that will be used to connect to your HubSpot account and click Next; or, create a new HubSpot Feeds credential for use in this flow.

Select the Objects to Ingest

After authenticating, Nexla lists the standard HubSpot objects available from the connector. Select one or more of the following objects to ingest. Each selected object becomes its own feed and is ingested on the configured schedule.

• Companies — Business or organization records in the CRM.
• Contacts — Individual people tracked in the CRM.
• Deals — Sales opportunities and their pipeline stages.
• Invoices — Invoice records.
• Leads — Lead records.
• Line Items — Individual product line items associated with deals or quotes.
• Products — Products defined in the product library.
• Quotes — Sales quotes.
• Tickets — Customer service tickets.
• Users — HubSpot user records.

The connector reads from HubSpot's CRM v3 objects API and can also ingest custom objects by their object type ID (for example, 2-xxxxxx) where your account defines them. HubSpot object endpoints are paginated; Nexla follows HubSpot's paging.next.after cursor automatically while reading each feed, so a full refresh ingests all available pages for the selected objects.

For each source, choose the sync strategy that applies to the selected feeds:

• Full Refresh: Retrieves the complete current set of records for each selected object on every run. Use this strategy for a complete snapshot, or for objects that do not support incremental filtering.

• Incremental Sync: Retrieves only records modified within a lookback window, using a HubSpot property such as hs_lastmodifieddate to identify changes. Configure the Incremental Syncs Lookback Time to set how far back each run should look; Nexla recommends time macros such as {now} or {now-1}.

Not every object supports incremental sync. The Users feed is ingested with a full refresh even when Incremental Sync is selected for the source.

Schedule and Activate

• Use the default sync schedule or adjust the schedule in the source settings before activating the flow. On each run, every selected feed is ingested according to its configured sync strategy.

Reference

For object schemas, property definitions, and additional detail on each HubSpot CRM object, see the HubSpot CRM objects API reference and the HubSpot API overview.