List Pipeline Stages
hubspot.list_pipeline_stages
ActionCRM & salesconnection required
Calls the HubSpot API with the connection's credentials.
List one pipeline's stages in display order with GET /crm/v3/pipelines/{objectType}/{pipelineId}/stages. The stage ids this returns are what `dealstage` and `hs_pipeline_stage` want on a write.
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 pipeline belongs to, usually deals or tickets. | string | Yes | — | — | deals |
pipeline_id Id of the pipeline; read the ids with hubspot.list_pipelines. | string | Yes | — | — | default |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"object_type": "deals",
"pipeline_id": "default"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
results The definitions HubSpot returned. | array | — |
count How many definitions came back. | number | — |
{
"count": 0,
"results": []
}Notes
- HubSpot refuses a stage *label* on a write; only these stage ids work.
See List Pipeline Stages 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.