Update Deal: Pipedrive action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Deal ID deal_id	string	Required	Deal ID. Example: 1
Title title	string	Optional	Title
Value value	string	Optional	Value
Stage ID stage_id	string	Optional	Stage ID
Status status	options	Optional	Status. Options: Open, Won, Lost, Deleted
Expected Close Date expected_close_date	string	Optional	Expected Close Date. e.g. "YYYY-MM-DD"

Sample request

{
  "deal_id": "e.g. 1",
  "title": "{{trigger.title}}",
  "value": "{{trigger.value}}",
  "stage_id": "{{trigger.stage_id}}",
  "status": "{{trigger.status}}"
}

Returns

{
  "data": {
    "id": 1,
    "title": "Updated Deal",
    "status": "won"
  },
  "success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Update Deal.

What does the Update Deal action do in Pipedrive?

Updates an existing Pipedrive deal: title, value, stage, status, expected close date, owner, or custom fields. Only the fields you pass are changed.

What inputs does Update Deal require?

Required: Deal ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Pipedrive returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Update Deal support batch operations?

Yes. Run Update Deal inside a Loop node to process arrays. Tiny Command handles Pipedrive's rate limits automatically so you don't have to throttle manually.

More actions