Short answer: Drop the "HubSpot → New Conversation" 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.
{"eventId": 100,"objectId": 1234567,"portalId": 62515,"sourceId": "userId:12345","occurredAt": 1712835600000,"changeSource": "CRM","propertyName": "","attemptNumber": 0,"propertyValue": "","subscriptionId": 12345,"subscriptionType": "conversation.creation"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| eventId | number | 100 |
| objectId | number | 1234567 |
| portalId | number | 62515 |
| sourceId | string | "userId:12345" |
| occurredAt | number | 1712835600000 |
| changeSource | string | "CRM" |
| propertyName | string | "" |
| attemptNumber | number | 0 |
| propertyValue | string | "" |
| subscriptionId | number | 12345 |
| subscriptionType | string | "conversation.creation" |
One trigger. 23+ downstream actions. Zero glue.