Change Deal Stage

pipedrive.change_deal_stage
ActionCRM & salesconnection required

Calls the Pipedrive API with the connection's credentials.

Move a deal to another pipeline stage with PATCH /api/v2/deals/{id}. Read the stage ids first with Pipedrive: List Stages.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Pipedrive
Secret shape
the Pipedrive API token, or {"api_token": "…"}
Config it needs
company_domain
Resolved by
config.connection_id, else node.connection_id

Configuration

4 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
Pipedrive id of the deal to move.
stringYes———
stage_id
Id of the stage to move the deal into.
stringYes———
pipeline_id
Id of the pipeline the stage belongs to. Only needed when the deal is moving between pipelines.
stringNo———
status
Lifecycle of the deal.
stringNo—one of "open", "won", "lost", "deleted"—

Output

One shape.

result

The provider's response object, as returned.

Extra keys beyond the ones listed can appear.

{}

Notes

  • A stage id belongs to exactly one pipeline; moving across pipelines needs both.

See Change Deal Stage run in a workflow.

In a technical demo we add the Pipedrive connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.