HubSpot

Stream HubSpot CRM objects, engagements, associations, property history, marketing assets and lists into Streamkap with a HubSpot service key or a legacy Private App access token.

The HubSpot source reads CRM objects, engagements, commerce objects, their associations and property history, pipelines, owners, users, marketing assets, lists and email activity from your HubSpot portal. Each resource you select becomes a topic named source_<id>.hubspot.<resource>.

Prerequisites

• A service key, which a Super admin or a user with Developer tools access can create, or the access token of an existing legacy Private App.
• The read scope of each resource you select, listed below. Streamkap never writes to your portal.
• For some resources, a HubSpot hub or tier: custom objects, deal splits, leads, goals, feedback submissions, workflows and campaigns exist only on portals that have them. A service key can be granted only scopes its creating user holds.

Required Scopes

Each CRM object, custom objects included, also needs its schema read scope, crm.schemas.<object>.read (for example crm.schemas.contacts.read). Streamkap reads the object’s property list with it to pick up custom and new properties. properties reads the property lists of every object the source syncs.

You don’t have to get the scopes right by inspection: select your resources and click Test access. It names the scope each unreadable resource needs. See Test connection and Test access.

HubSpot Setup

Use either credential below.

1. Create a Service Key

1. In HubSpot, go to Development → Keys → Service keys.
2. Create a key, for example named Streamkap, with the read scope of each resource you want to sync.
3. Copy the key.

2. Or Use an Existing Private App

HubSpot is removing the ability to create new legacy Private Apps. If you already have one for Streamkap, you can use its token:

1. In HubSpot, go to Development → Legacy apps and open your app.
2. On the Scopes tab, check that it has the read scope of each resource you want to sync.
3. On the Auth tab, click Show token and copy it.

Streamkap Setup

1. Create the Source

• Navigate to Add Connectors.
• Choose HubSpot.

2. Connection Settings (Auth Tab)

• Source name: A unique name for this source, for example hubspot-prod.
• Access token: The service key or the legacy Private App token.

Optionally click Test connection, then click Next.

3. Settings Tab

• Resources: The HubSpot objects to sync. The default is contacts and deals. Add a preset offers:
  • Core CRM: contacts, companies, deals, owners, pipelines, pipeline_stages, associations_contacts_companies, associations_contacts_deals, associations_companies_deals.
  • Sales activity: Core CRM plus calls, meetings, notes, tasks, line_items, products, associations_deals_line_items, associations_deals_calls, associations_deals_meetings, associations_deals_notes and associations_deals_tasks. It leaves out emails, which need the sales-email-read scope.
  • Service: contacts, companies, owners, tickets, ticket_pipelines, ticket_pipeline_stages, associations_contacts_tickets, associations_companies_tickets, notes and tasks.
  • Forms and lists: contacts, forms, form_submissions, lists and list_memberships. It leaves out marketing emails and campaigns, which need Marketing Hub.
• Sync all properties: On by default. Syncs every property of each object, including custom properties and ones added later. Turn it off to sync only the properties you select, for example to keep an existing topic’s record width.
• Properties (shown when Sync all properties is off, on a saved source): The properties to sync, by internal name rather than label. Each object’s hs_object_id and last-modified date are always synced. A name must exist on at least one selected object, or the save is rejected.
• API version: Keep 2026-03, the default. v3 (legacy) is only for sources created on it.
• Backfill start date: See Backfill start date. It bounds the CRM objects, custom objects, property history, form_submissions, email_events and subscription_changes. Every other resource is a whole list and always syncs in full.

4. Review and Create

Check the summary and click Create. Streamkap validates the credential against HubSpot before it saves the source. Then send the topics to a destination: see Send topics to a destination.

Editing the Source

For the changes every API source shares, see Editing an API source.

Rotating the Access Token

On the Auth tab, click Replace, paste the new token and save. Saving clears an authentication failure and any per-resource scope suspension at once. Test connection on a saved source tests the stored token, so you don’t need to re-enter it to check it.

Custom Objects

Custom objects aren’t offered on the create form: Streamkap lists them with the saved credential. After creating the source, open its Settings tab, where the Resources picker adds your custom objects by their fully qualified name (p<portal-id>_<name> or 2-<object-type-id>). You can also type the name.

If the Settings tab says it couldn’t read your custom-object definitions, the credential lacks crm.schemas.custom.read. Nothing else is affected.

Supported Resources

CRM object records keep HubSpot’s shape: properties sit in a nested properties object beside the top-level id, createdAt, updatedAt and archived.

Behavior & Limits

Polling

The core CRM objects, engagements, commerce objects, custom objects, property history, owners, the deal and ticket pipelines and their stages, email_events and subscription_changes are read every poll (five minutes by default). goal_targets, discounts, fees, taxes, associations and the other whole lists are read hourly, form_submissions every 15 minutes and list_memberships every six hours. Each poll re-reads the last 10 minutes of changes, because HubSpot’s search index lags its writes.

Deletes

• Archived records: a sweep every 6 hours reads HubSpot’s archived records and sends each as a delete. It covers every CRM object except invoices and subscriptions, plus custom objects. HubSpot keeps archived records listed for about 90 days.
• Merges and permanent purges, including GDPR erasures, leave no archived record. A daily reconciliation lists each object’s live IDs and deletes the ones that are gone. On a large object it spreads over several runs. One pass can name about 1,600 vanished records per object; past that, the status says so and the rest stay in your destination. This pass is the only delete signal for invoices and subscriptions.
• Whole lists (owners, pipelines and stages, associations, list memberships, forms, lists and the other re-read resources): a row missing from a complete read is deleted. A deactivated owner is an update with archived = true, not a delete.
• Property history, form submissions, email events and subscription changes only add rows.

See Deletes for how deletes reach your destination.

Rate Limits and Daily Quota

The connector stays below HubSpot’s 5-a-second search limit. It also reads the portal’s daily API budget and stops for the day once 90% is used, by Streamkap and your other integrations together. HubSpot doesn’t report the budget on every response, so the connector can pass 90% slightly before it stops. The source shows Throttled with a message such as “HubSpot daily API quota is 92% used” and resumes at the next UTC midnight with no data lost.

Read Cost

Three kinds of resource grow with your data: associations re-read the whole <from> side of their pair hourly, list_memberships re-reads every list’s members every six hours, and property history reads each changed record’s history. None is preselected. As a guide, a Professional portal syncing the core objects, engagements, three association pairs over 100,000 records, a million list memberships and the marketing feeds uses 18% to 32% of its daily budget, mostly on associations.

Missing Scopes

A missing scope pauses only that resource; the rest keep streaming. The source shows Broken, and its status names each resource and the scope to add. A paused resource is retried on its own, so it recovers once you grant the scope; saving the source retries it at once. properties skips an object whose schema scope is missing and keeps syncing the others.

An invalid or revoked token stops all syncing until you replace it or reconnect. See Connector status.

Troubleshooting

Related Documentation

• API sources - how API sources work, Test access, editing, delivery and status
• Salesforce - the other CRM API source