Change Deal Stage

hubspot.change_deal_stage
ActionCRM & salesconnection required

Calls the HubSpot API with the connection's credentials.

Move one deal to a pipeline stage with PATCH /crm/v3/objects/deals/{dealId}. This is the narrow, safe form of Update Deal: it sends only the stage, so no other property can be overwritten by accident.

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

3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
deal_id
The HubSpot record id of the deal to move.
stringYes——101
dealstage
Id of the stage to move the deal to — the stage id, never its label. Read the ids with hubspot.list_pipeline_stages.
stringYes——appointmentscheduled
pipeline
Id of the pipeline the stage belongs to. Required when the target stage is in a different pipeline from the deal's current one.
stringNo———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "deal_id": "101",
  "dealstage": "appointmentscheduled"
}

Output

One shape.

result

FieldTypeExample
id
The record's HubSpot object id.
string—
properties
The record's properties, keyed by HubSpot property name.
object—
createdAt
When the record was created, ISO 8601 UTC.
string—
updatedAt
When the record was last modified, ISO 8601 UTC.
string—
archived
True when the record sits in the recycling bin.
boolean—
{
  "archived": false,
  "createdAt": "",
  "id": "",
  "properties": {},
  "updatedAt": ""
}

See Change Deal Stage 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.