ActionPipedriveUpdated September 2026

How do I update a Pipedrive deal?

Short answer: You can update deal in Pipedrive by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Pipedrive Update Deal action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Update Deal in Pipedrive — start free All 7 Pipedrive actions

Update Deal in Pipedrive — start free

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.

Triggered by

Apps that pair well as the trigger for Update Deal.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Pipedrive

2 Google Sheets triggers

HubSpot → Pipedrive

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Pipedrive returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Update Deal support batch operations?

Run Update Deal inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Pipedrive's rate limits.

More actions