Short answer: Drop the "Pipedrive → New Deal" 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.
{"title": "Big Deal","value": 10000,"action": "create","entity": "deal","org_id": null,"status": "open","deal_id": 7,"user_id": "31343385","added_at": "2026-04-11T10:00:00Z","currency": "USD","owner_id": 31343385,"stage_id": 6,"entity_id": "7","person_id": null,"company_id": "19410833","occurred_at": "2026-04-11T10:00:00Z","pipeline_id": 2,"expected_close_date": null}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| title | string | "Big Deal" |
| value | number | 10000 |
| action | string | "create" |
| entity | string | "deal" |
| org_id | null | null |
| status | string | "open" |
| deal_id | number | 7 |
| 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 | "7" |
| person_id | null | null |
| company_id | string | "19410833" |
| occurred_at | string | "2026-04-11T10:00:00Z" |
| pipeline_id | number | 2 |
| expected_close_date | null | null |
One trigger. 7+ downstream actions. Zero glue.