Skip to content

docs(hubspot): add FAQ for Retrieve associated objects returning No data - #2292

Merged
george-dilthey merged 1 commit into
mainfrom
docsbot/doc-2038-intercom-tag-0824-f07f860c
Aug 26, 2026
Merged

docs(hubspot): add FAQ for Retrieve associated objects returning No data#2292
george-dilthey merged 1 commit into
mainfrom
docsbot/doc-2038-intercom-tag-0824-f07f860c

Conversation

@george-dilthey

Copy link
Copy Markdown
Contributor

What changed

Added a new FAQ entry to docs/hubspot-integration-overview.md explaining why the HubSpot "Retrieve associated objects" action returns No data even when the association exists in HubSpot. The entry explains the type/ID mismatch root cause and gives a concrete Contact→Deal example with fix steps.

Why

Intercom conversation #215475556467216: a customer (Aryan Arora) was trying to retrieve deals associated with a HubSpot contact using the "Retrieve associated objects" action. The column returned {"results":[],"totalFound":0} and Clay showed No data, even though the association existed in HubSpot. Fin escalated to a human agent.

The human agent (Krithik) investigated with the support copilot and identified the root cause: the customer's From Object Type was set to Company while From Object ID was mapped to a contact's ID (or vice versa). Because Clay passes both values directly to HubSpot's CRM v4 API without any validation that they match, HubSpot hits the wrong endpoint path and returns empty results. The docs had no FAQ covering this scenario — only a FAQ about the 20-result limit.

The existing FAQ "Why does 'Retrieve associated objects' return at most 20 results, even when HubSpot shows more?" covers a different "no results" scenario (too many results, not a type/ID mismatch). The new FAQ fills the gap for the zero-results-despite-existing-association case.

Source link(s)

Uncertainties

None. The behavior is confirmed by code (verifier PASS) and the root cause is conclusively established from the support copilot Slack thread.

Related observations

The support copilot thread also noted that a duplicate HubSpot deal (343191749325) was created as a side effect — the customer's table had a "Create Deal" step that ran because the lookup returned empty. This is a user-table configuration issue, not a docs issue.

Closes DOC-2038

@linear-code

linear-code Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

DOC-2038

@george-dilthey
george-dilthey marked this pull request as ready for review August 26, 2026 14:51
@george-dilthey
george-dilthey merged commit 2adfb76 into main Aug 26, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant