Skip to main content
Use the @bijection/connectors/hubspot entrypoint to declare HubSpot resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

CRM objects

pull: List, archived reconciliation and unconditional updates

The following example matches configuration standard.
The function references identify application policy queries. Implement those policies in your application; the references alone grant no authority.

Configuration: standard

Case: hubspot/objects/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: hubspot. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: records
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: readOnly

Case: hubspot/objects/pull/readOnly. Connection and resource configuration are declared by this exact case. Credential kind: hubspot. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Directional associations

pull: Keyed fanout over one direction

The following example matches configuration standard.

Configuration: standard

Case: hubspot/associations/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: hubspot. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: associations
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection holds a hubspot credential (hubspot.credential), normally a private-app bearer token for https://api.hubapi.com. Identity is the account’s numeric portalId. objects.pull reads one CRM object type through the list endpoint (crm/objects/2026-09/<object>), retaining id, createdAt, updatedAt and each selected property as HubSpot’s own text or null. A list is a live observation: its end withdraws nothing and claims no snapshot. Search is never used, because search lags and is capped. Deletion comes only from reconciliation: the active point read of an archived record answers a non-JSON 404, which stays unresolved, and the follow-up archived=true read must return the same id with archived: true before the record is withdrawn. update sends PATCH with { properties }. HubSpot applied a deliberately mismatched If-Match, so the write is declared unconditional: competing writers inside HubSpot are not fenced. There is no idempotency key, so delivery is a single attempt, and reconciliation can only report an unknown outcome. associations.pull reads one direction only. HubSpot names the same relationship forward and in reverse (association types 341 and 342), so reading both directions would count each pair twice. A listing of from records is the discovery; each parent’s association pages are walked with the cursor the host retains for that parent. Removing an association changes neither endpoint, and a pass claims no coverage, so a removed association is not withdrawn. A 429 is honoured through Retry-After. Nothing here has run against HubSpot or been qualified; see the validation scenarios for what is checked.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.