A new Custom Object Associations report returns one row per association between any two HubSpot object types, custom objects included - so every associated record is extractable, and any two HubSpot tables can be joined on a real key.

HubSpot stores a record's relationships as associations, not as properties. Until now the connector extracted associations only as a fixed contact-and-company pair, so any other relationship - a custom object to a custom object, a meeting to a custom object, a deal to a ticket - was out of reach. The new Custom Object Associations report makes all of them extractable.

Why a property cannot answer this

A common reason for reaching for this report: a custom-object table appears to return only one value where the record clearly has several. That is usually not truncation. Each HubSpot property holds a single value by its own data model, so a property that looks like a list of related records is really one property per slot, each maintained by your own HubSpot automation. No extraction setting can make such a property hold an array - the multi-value data lives in the associations, which is what this report reads.

What the report returns

One row per association, with a schema that is the same for every HubSpot portal:

• The two object types involved, as the object type you started from and the object type it is associated with.
• Both record IDs, which are the join keys into your other HubSpot tables.
• The association types, carrying HubSpot's category, type ID and label. The label is what distinguishes a primary association from an ordinary one, so labelled relationships survive extraction intact.

Two things to know before you build on it

• Associations carry IDs, not names. A row tells you that record 26086627869 is associated with your starting record - not what that record is called. To get the name, extract the associated object with the Custom Object report as well and join the two tables on the ID. Both halves are self-serve; no setup request is needed.
• Association labels come from your own portal. The label text is whatever was typed into HubSpot when the association type was created, and it appears in your data verbatim - including any typo. If a label looks wrong in a report, correct it in HubSpot rather than in the extract.

An association carries no timestamp of its own and HubSpot offers no date filter on it, so the report refreshes in full on each run rather than reading an incremental window.