- Integrations
- /
- Pipedrive
- /
- Actions
- /
- Update Deal
ActionPipedriveUpdated May 2026
How do I update a Pipedrive deal?
Short answer: Drop the "Pipedrive → Update Deal" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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
Other Pipedrive actions.
Action
Create Deal
Creates a new deal in the Pipedrive sales pipeline with title, value, currency, person, organization, stage, expected close date, and owner. The entry point for converting qualified leads into pipeline.
ActionCreate Person
Creates a new person (contact) in Pipedrive with name, email, phone, organization, owner, and any custom fields. Used to push inbound leads into the CRM.
ActionGet Deal
Retrieves a Pipedrive deal by ID with title, value, stage, person, organization, owner, and custom fields. The standard read after a trigger fires with an ID.
ActionGet Person
Returns a Pipedrive person by ID with their emails, phones, organization, owner, and custom fields. Used to enrich trigger payloads or render contact UI.
ActionList Deals
Lists deals from Pipedrive with filters for owner, stage, status (open/won/lost), and update time. Used for pipeline reports, forecasting, and warehouse exports.
ActionList Persons
Lists persons (contacts) from Pipedrive with filters for owner and update time. Used for CRM sync into your ESP or for cohort exports.
Send update deal from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.