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.
Drop it on the canvas. Configure a couple of fields. Publish.
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"}
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" |
One trigger. 7+ downstream actions. Zero glue.