TriggerPipedriveReal-timeUpdated May 2026

How do I trigger when a Pipedrive person changes?

Short answer: Drop the "Pipedrive → Person 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.

Use this trigger All 8 Pipedrive triggers

Anatomy

What this trigger looks like in a workflow.

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

In the builder

Trigger

Person Updated

When the matching event happens

person modifiedwhen a person is updatedwhen person updatedon person updatedperson changedwatch for person updatednew person 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.

{
  "name": "Jane Doe",
  "action": "change",
  "emails": [
    {
      "value": "jane@example.com",
      "primary": true
    }
  ],
  "entity": "person",
  "org_id": null,
  "phones": [],
  "user_id": "31343385",
  "added_at": "2026-04-11T10:00:00Z",
  "owner_id": 31343385,
  "entity_id": "7",
  "label_ids": [],
  "last_name": "Doe",
  "person_id": 7,
  "prev_name": "Jane Doe",
  "company_id": "19410833",
  "first_name": "Jane",
  "updated_at": "2026-04-11T10:00:00Z",
  "visible_to": "3",
  "occurred_at": "2026-04-11T10:00:00Z",
  "prev_last_name": "Doe"
}

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
name	string	"Jane Doe"
action	string	"change"
emails	array	[{"value":"jane@example.com","primary":true}]
entity	string	"person"
org_id	null	null
phones	array	[]
user_id	string	"31343385"
added_at	string	"2026-04-11T10:00:00Z"
owner_id	number	31343385
entity_id	string	"7"
label_ids	array	[]
last_name	string	"Doe"
person_id	number	7
prev_name	string	"Jane Doe"
company_id	string	"19410833"
first_name	string	"Jane"
updated_at	string	"2026-04-11T10:00:00Z"
visible_to	string	"3"
occurred_at	string	"2026-04-11T10:00:00Z"
prev_last_name	string	"Doe"

Pairs with

Drop these actions after Person Updated.

Add Labels to Message

Gmail · Email

Raw API Request

Slack · Communication

Add Sheet Tab

Google Sheets · Spreadsheets & Databases

Create Company

HubSpot · CRM & Sales

FAQ

Questions about Person Updated.

How does the Person Updated trigger work in Pipedrive?

Fires when a person (contact) is updated in Pipedrive. Use to re-enrich, re-sync to your ESP, or kick off a workflow when key custom fields change.

Is the Person Updated trigger real-time?

Yes. Person Updated uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Pipedrive.

What data does Person 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 Person 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 Person 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 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.

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.

Build a workflow on this trigger.

One trigger. 7+ downstream actions. Zero glue.

Try for free Request a demo

How do I trigger when a Pipedrive person changes?

What this trigger looks like in a workflow.

Fields available to downstream nodes.

Drop these actions after Person Updated.

Questions about Person Updated.

Other Pipedrive triggers.

Build a workflow on this trigger.

Be the first to know what's next.