TriggerPipedriveReal-timeUpdated June 2026

How do I trigger when a Pipedrive deal changes?

Short answer: Drop the "PipedriveDeal Updated" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Pipedrive, not on a polling schedule.

Anatomy

What this trigger looks like in a workflow.

Drop it on the canvas. Configure a couple of fields. Publish.

In the builder
Trigger
Deal Updated
When the matching event happens
on deal updatedwhen a deal is updateddeal modifiedwhen deal updateddeal changedwatch for deal updatednew deal updated
What this trigger returns
for the curious

You don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.

{
"title": "Renewal Q2",
"value": 999,
"action": "change",
"entity": "deal",
"org_id": null,
"status": "open",
"deal_id": 13,
"user_id": "31343385",
"added_at": "2026-04-11T10:00:00Z",
"currency": "USD",
"owner_id": 31343385,
"stage_id": 6,
"entity_id": "13",
"person_id": null,
"company_id": "19410833",
"prev_value": 50,
"updated_at": "2026-04-11T10:05:00Z",
"occurred_at": "2026-04-11T10:05:00Z",
"pipeline_id": 2,
"prev_status": "open",
"prev_owner_id": 31343385,
"prev_stage_id": 6,
"expected_close_date": null
}
Output shape

Fields available to downstream nodes.

Every field below can be referenced by name in any action or filter that comes after this trigger.

FieldTypeExample
titlestring"Renewal Q2"
valuenumber999
actionstring"change"
entitystring"deal"
org_idnullnull
statusstring"open"
deal_idnumber13
user_idstring"31343385"
added_atstring"2026-04-11T10:00:00Z"
currencystring"USD"
owner_idnumber31343385
stage_idnumber6
entity_idstring"13"
person_idnullnull
company_idstring"19410833"
prev_valuenumber50
updated_atstring"2026-04-11T10:05:00Z"
occurred_atstring"2026-04-11T10:05:00Z"
pipeline_idnumber2
prev_statusstring"open"
prev_owner_idnumber31343385
prev_stage_idnumber6
expected_close_datenullnull
FAQ

Questions about Deal Updated.

How does the Deal Updated trigger work in Pipedrive?
Fires whenever any field on a Pipedrive deal changes (stage, value, owner, expected close date, custom fields). Combine with a field filter to react only on specific transitions.
Is the Deal Updated trigger real-time?
Yes. Deal Updated uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Pipedrive.
What data does Deal Updated return?
The full event payload from Pipedrive. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter Deal Updated so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need Pipedrive admin permissions to use Deal Updated?
For most Pipedrive accounts a standard user can authorize the trigger. Some Pipedrive plans require an admin to enable third-party webhooks. Check Pipedrive's docs if the trigger fails to register.
More triggers

Other Pipedrive triggers.

Trigger
Activity Added
Fires when a new activity (call, meeting, task, email) is created in Pipedrive. Use to mirror activities into a calendar or to enforce activity-based SLAs.
Trigger
New Deal
Fires when a new deal is added in Pipedrive. Used to celebrate new pipeline in Slack, kick off enrichment, or auto-assign the deal owner.
Trigger
Deal Lost
Fires when a deal is marked as lost in Pipedrive. Common use: log the lost-reason, add the contact to a churn-saver sequence, or trigger a manager review for large lost deals.
Trigger
Deal Won
Fires when a deal is marked as won in Pipedrive. The Closed-Won hook: provision customer, generate contract, post to Slack, kick off onboarding.
Trigger
New Organization
Fires when a new organization is added in Pipedrive. Use for firmographic enrichment, parent-account matching, or to seed a customer record elsewhere.

Build a workflow on this trigger.

One trigger. 7+ downstream actions. Zero glue.