> 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-property-details.md).

# Get Property Details

Fetches the definition of one specific field on a HubSpot record type, including the values it accepts. Useful for checking which values a field allows before updating it.

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

## Inputs

| Field           | Type   | Required/default | Meaning                                      |
| --------------- | ------ | ---------------- | -------------------------------------------- |
| `object_name`   | string | Required         | The object name (e.g. tickets)               |
| `property_name` | string | Required         | The property name (e.g. hs\_pipeline\_stage) |

## 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                                                                                                   |
| --------------------- | ------- | --------------------------------------------------------------------------------------------------------- |
| `field`               | object  | Definition of the requested property, rather than its value on an individual record.                      |
| `field.name`          | string  | Internal property name to use in reads, filters and updates.                                              |
| `field.label`         | string  | Human-readable property label.                                                                            |
| `field.type`          | string  | Property data type, such as `string`, `number` or `enumeration`.                                          |
| `field.fieldType`     | string  | HubSpot field control type, such as a text input or dropdown.                                             |
| `exists`              | boolean | True when the requested property definition is returned.                                                  |
| `llm_triage_metadata` | string  | Text summary of the property name, ID, description and available choices; `No entries found` when absent. |

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

## Behavior and limits

Looks up one property's definition using `object_name` and `property_name`. This does not read that property's value from a ticket. Enumeration choices are described in `llm_triage_metadata` and may also be present as additional fields on the definition.

An unknown property or object type gives `exists: false` and a default field object.

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