Short answer: Drop the "Pipedrive → New Organization" 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": "Acme Inc","action": "create","entity": "organization","org_id": 1,"address": null,"user_id": "31343385","website": null,"added_at": "2026-04-11T10:00:00Z","industry": null,"linkedin": null,"owner_id": 31343385,"entity_id": "1","label_ids": [],"company_id": "19410833","updated_at": "2026-04-11T10:00:00Z","visible_to": "3","occurred_at": "2026-04-11T10:00:00Z","country_code": null,"annual_revenue": null,"employee_count": null}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| name | string | "Acme Inc" |
| action | string | "create" |
| entity | string | "organization" |
| org_id | number | 1 |
| address | null | null |
| user_id | string | "31343385" |
| website | null | null |
| added_at | string | "2026-04-11T10:00:00Z" |
| industry | null | null |
| null | null | |
| owner_id | number | 31343385 |
| entity_id | string | "1" |
| label_ids | array | [] |
| company_id | string | "19410833" |
| updated_at | string | "2026-04-11T10:00:00Z" |
| visible_to | string | "3" |
| occurred_at | string | "2026-04-11T10:00:00Z" |
| country_code | null | null |
| annual_revenue | null | null |
| employee_count | null | null |
One trigger. 7+ downstream actions. Zero glue.