Get List
hubspot.get_list
ActionCRM & salesconnection required
Calls the HubSpot API with the connection's credentials.
Read one list's definition with GET /crm/v3/lists/{listId} — its name, size, processing type and processing status.
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 |
|---|---|---|---|---|---|
list_id The HubSpot record id of the list to read. | string | Yes | — | — | 101 |
include_filters Also return the list's filter-branch definition. | boolean | No | false | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"include_filters": false,
"list_id": "101"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
listId The list's id. | string | — |
name The list's name. | string | — |
objectTypeId The object type the list holds, e.g. "0-1". | string | — |
processingType MANUAL, DYNAMIC or SNAPSHOT. | string | — |
processingStatus Whether the list is currently processing. | string | — |
size How many records the list holds. | number | — |
{
"listId": "",
"name": "",
"objectTypeId": "",
"processingStatus": "",
"processingType": "",
"size": 0
}See Get List 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.