Skip to content

HubSpot

The test-estate safety rule: stand the test estate up only beside a test instance, never a production deployment. Its systems are throwaway test services with published credentials: change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.

Grade D · dataset: API (the vendor’s response payloads) · type hubspot

What it is

A HubSpot account read over the CRM v3 API. In the test estate it holds companies and the deals behind customer orders.

Grade

D. Dataset and model: the quickstart dataset and its expected model ship. There is no vendor system to stand up for this type; load the dataset and fetch it.

See the grade table for all 32 types.

Settings and credentials

From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.

Names
Typehubspot
Settingsnone
Credentialsapi_key

The test connection

Quillmere CRM (HubSpot)

SettingTest value
(none)

Credentials: api_key. In the test estate, every credential is change-me. Credentials are write-only: they go into the sealed credential bundle and are never returned.

Stand up the test system

The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.

  1. Download hubspot.zip and unzip it. It holds the vendor’s response payloads and expected.json.
  2. A HubSpot free-tier account can hold these objects.
  3. Open the payloads next to expected.json: every field the expected model names is in the payload, with the join keys described below.

What FACE finds

FACE reads no catalogue for this type. The dataset is CRM v3 object list responses, and the expected model is their record shape.

DatasetKindDomainPrimary keyRowsFields
companiescrm_objectcustomersid67
dealscrm_objectordersid2410

expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.

How it joins the Quillmere universe

This source carries 3 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.

Universe entityFields hereAlso in
customercompanies.properties.customer_number, deals.properties.customer_numberfiles, kafka, oms, postgres, redshift, salesforce, sap, snowflake
customer_podeals.properties.customer_pofiles, kafka, oms, postgres, snowflake
orderdeals.properties.order_numberdocument, files, kafka, oms, postgres, sap, snowflake

Evidence it holds for the planted anomalies:

  • ANOM-4, A duplicate customer PO. hubspot/crm_v3_objects_deals.json in hubspot.zip, look for "customer_po": "PO-0002-4194".

See all connectors at once for the walkthrough across every source.

Download

This is one of 25 zips: the 7 streaming types ship as replay recordings instead.

What is in the zip
  • hubspot/crm_v3_objects_companies.json
  • hubspot/crm_v3_objects_deals.json
  • hubspot/expected.json

The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.