TriggerPipedriveReal-timeUpdated May 2026
How do I trigger when a Pipedrive deal is lost?
Short answer: Drop the "Pipedrive → Deal Lost" 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 Lost
When the matching event happens
watch for deal loston deal lostwhen deal lostwhen a deal is marked as lostnew deal lost
What this trigger returns
for the curiousYou 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": "lost","deal_id": 13,"user_id": "31343385","added_at": "2026-04-11T10:00:00Z","currency": "USD","owner_id": 31343385,"stage_id": 6,"entity_id": "13","lost_time": "2026-04-11T10:05:00Z","person_id": null,"close_time": "2026-04-11T10:05:00Z","company_id": "19410833","updated_at": "2026-04-11T10:05:00Z","lost_reason": "TC test","occurred_at": "2026-04-11T10:05:00Z","pipeline_id": 2,"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.
| Field | Type | Example |
|---|---|---|
| title | string | "Renewal Q2" |
| value | number | 999 |
| action | string | "change" |
| entity | string | "deal" |
| org_id | null | null |
| status | string | "lost" |
| deal_id | number | 13 |
| user_id | string | "31343385" |
| added_at | string | "2026-04-11T10:00:00Z" |
| currency | string | "USD" |
| owner_id | number | 31343385 |
| stage_id | number | 6 |
| entity_id | string | "13" |
| lost_time | string | "2026-04-11T10:05:00Z" |
| person_id | null | null |
| close_time | string | "2026-04-11T10:05:00Z" |
| company_id | string | "19410833" |
| updated_at | string | "2026-04-11T10:05:00Z" |
| lost_reason | string | "TC test" |
| occurred_at | string | "2026-04-11T10:05:00Z" |
| pipeline_id | number | 2 |
| expected_close_date | null | null |
Pairs with
Drop these actions after Deal Lost.
FAQ
Questions about Deal Lost.
How does the Deal Lost trigger work in Pipedrive?
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.
Is the Deal Lost trigger real-time?
Yes. Deal Lost uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Pipedrive.
What data does Deal Lost 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 Lost 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 Lost?
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.
TriggerNew 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.
TriggerDeal Updated
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.
TriggerDeal 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.
TriggerNew 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.
