> 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-object-properties.md).

# Get Object Properties

Fetches all field definitions for a HubSpot record type (tickets, contacts, companies or deals), including custom fields and the values they accept. Useful for finding which fields exist before updating records.

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

## Inputs

| Field         | Type   | Required/default | Meaning                                             |
| ------------- | ------ | ---------------- | --------------------------------------------------- |
| `object_type` | string | Required         | The object type (e.g. tickets, contacts, companies) |

## 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                                                                                                               |
| --------------------- | --------------- | --------------------------------------------------------------------------------------------------------------------- |
| `fields`              | list of objects | Property definitions for the selected object type, rather than values on an individual record.                        |
| `fields[].name`       | string          | Internal property name to use in reads, filters and updates.                                                          |
| `fields[].label`      | string          | Human-readable property label.                                                                                        |
| `fields[].type`       | string          | Property data type, such as `string`, `number` or `enumeration`.                                                      |
| `fields[].fieldType`  | string          | HubSpot field control type, such as a text input or dropdown.                                                         |
| `exists`              | boolean         | True when at least one property definition is returned.                                                               |
| `llm_triage_metadata` | string          | Text summary of property names, IDs, descriptions and available choices or data types; `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 property definitions, not values on a particular record. Use each property's internal `name` in reads/writes; labels are display text. `llm_triage_metadata` includes enumeration choices as label/value pairs when available.

Unknown object types or no returned definitions give `exists: false`, an empty fields list and `No entries found` metadata. HubSpot may return additional definition fields through the open output model.

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).