Integrations
Check whether records can be sent to HubSpot
Reports whether your HubSpot account is connected, which record types your workspace has set up to send, and whether the connected account is the one that setup was built for. Read-only — call it before offering to send anything.
Authorization
Responses
200objectReadiness per record typeShow attributesHide attributes
configuredPortalIdstring | nullrequiredThe HubSpot account your workspace's setup was built for. When this differs from portalId, pushes are refused.
connectedbooleanrequiredmaxRecordsPerPushnumberrequiredobjectsobject[]requiredShow child attributesHide child attributes
codestringentityenumThe kind of Model Match record the ids refer to — originator for loan officers, agent for real estate agents. Required, and checked against what your workspace configured: if they disagree the request is refused rather than writing records built from the wrong mapping.
agentoriginatormappedFieldCountnumbermatchOnstringThe HubSpot field used to match existing records.
objectenumrequiredWhich kind of HubSpot record to write. Your workspace decides which Model Match records feed each one.
contactcompanyreadybooleanrequiredreasonstringportalIdstring | nullrequiredThe HubSpot account you have connected, when known.
portalMismatchbooleanrequired400objectValidation error401objectUnauthorized403objectForbidden (authenticated, but missing required context — e.g. no active organization)404objectNot found413objectResponse payload too large — detail endpoint capped to fit Lambda response limits503objectSearch timed out or the cluster is overloaded — retry after `Retry-After` seconds.