> For the complete documentation index, see [llms.txt](https://docs.ebbot.ai/ebbot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/actions/get-association-types.md).

# Get Association Types

Fetches the possible relationship types between two kinds of HubSpot records, for example between tickets and contacts. Use this to find the correct association type ID before associating objects.

**Action identifier:** `get_association_types`. **Reference checked:** 29 September 2026.

## Inputs

| Field              | Type   | Required/default | Meaning                            |
| ------------------ | ------ | ---------------- | ---------------------------------- |
| `from_object_type` | string | Required         | Source object type (e.g. tickets)  |
| `to_object_type`   | string | Required         | Target object type (e.g. contacts) |

## Output shape

Paths are relative to this action's output. Select them from the builder's variable picker; do not add a `ticket` wrapper to actions that return top-level fields. Nullable property fields and empty defaults are not proof that a value was retrieved.

| Path                  | Type            | Meaning                                                                                                      |
| --------------------- | --------------- | ------------------------------------------------------------------------------------------------------------ |
| `results`             | list of objects | Association type definitions for the requested source-to-target object pair.                                 |
| `results[].typeId`    | integer         | Association type ID for this direction and category.                                                         |
| `results[].label`     | string \| null  | Display label; null for an unlabelled association.                                                           |
| `results[].category`  | string          | HubSpot association category, such as `HUBSPOT_DEFINED` or `USER_DEFINED`.                                   |
| `exists`              | boolean         | True when at least one type definition is returned; false for no definitions or an unknown object-type pair. |
| `llm_triage_metadata` | string          | Text summary of labels, type IDs and categories; `No entries found` when empty.                              |

Open property/record objects may include additional HubSpot fields. Inspect the returned data rather than assuming every declared field is populated.

## Behavior and limits

Returns association types for the specified ordered object-type pair. The reverse direction can use a different type ID. Preserve `category` as well as `typeId` when interpreting results; the list may include user-defined labels.

No returned types or an unknown pair gives `exists: false`. This flag concerns returned type definitions, not existence of two individual CRM records. Unlabelled entries are described as `Unlabeled` in metadata.

See [Troubleshooting](/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/troubleshooting.md) for request errors and retry behavior, or return to the [action catalog](/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/actions.md).