Short answer: Drop the "HubSpot → Contact Property Changed" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in HubSpot, 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.
{"event": "contact.propertyChange","object_id": 12345}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| event | string | "contact.propertyChange" |
| object_id | number | 12345 |
One trigger. 23+ downstream actions. Zero glue.