List Properties
hubspot.list_properties
ActionCRM & salesconnection required
Calls the HubSpot API with the connection's credentials.
List every property defined on an object type with GET /crm/v3/properties/{objectType}, custom properties included. This is how a workflow discovers the internal names the other nodes need.
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, 1 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 whose properties to list, for example contacts or deals. | string | Yes | — | — | contacts |
archived List archived property definitions instead of live ones. | boolean | No | false | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"archived": false,
"object_type": "contacts"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
results The definitions HubSpot returned. | array | — |
count How many definitions came back. | number | — |
{
"count": 0,
"results": []
}Notes
- Sensitive-data properties are left out unless the portal grants the private app the sensitive-data scopes.
See List Properties 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.