Get Property
hubspot.get_property
ActionCRM & salesconnection required
Calls the HubSpot API with the connection's credentials.
Read one property definition with GET /crm/v3/properties/{objectType}/{propertyName}, including the allowed options of a dropdown or radio property.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- HubSpot
- Secret shape
- the HubSpot private-app token, or {"token": "…"}
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
object_type The object type the property belongs to. | string | Yes | — | — | contacts |
property_name The property's internal name, not its label. | string | Yes | — | — | lifecyclestage |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"object_type": "contacts",
"property_name": "lifecyclestage"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
name The property's internal name. | string | — |
label The property's label as shown in HubSpot. | string | — |
type The stored data type: string, number, enumeration, … | string | — |
fieldType How HubSpot renders it: text, select, date, … | string | — |
groupName The property group the property sits in. | string | — |
options The allowed values, for an enumeration property. | array | — |
{
"fieldType": "",
"groupName": "",
"label": "",
"name": "",
"options": [],
"type": ""
}See Get Property run in a workflow.
In a technical demo we add the HubSpot connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.