- Integrations
- /
- HubSpot
- /
- Triggers
- /
- Ticket Updated
TriggerHubSpotReal-timeUpdated May 2026
How do I trigger when a HubSpot ticket property changes?
Short answer: Drop the "HubSpot → Ticket Updated" 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.
Anatomy
What this trigger looks like in a workflow.
Drop it on the canvas. Configure a couple of fields. Publish.
In the builder
Trigger
Ticket Updated
When the matching event happens
ticket updatedticket property changedon ticket updatedwatch for ticket updatedticket modifiedwhen ticket status changes in hubspot
What this trigger returns
for the curiousYou 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": "hs_pipeline_stage","attemptNumber": 0,"propertyValue": "2","subscriptionId": 12345,"subscriptionType": "ticket.propertyChange"}
Output shape
Fields available to downstream nodes.
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 | "hs_pipeline_stage" |
| attemptNumber | number | 0 |
| propertyValue | string | "2" |
| subscriptionId | number | 12345 |
| subscriptionType | string | "ticket.propertyChange" |
Pairs with
Drop these actions after Ticket Updated.
FAQ
Questions about Ticket Updated.
How does the Ticket Updated trigger work in HubSpot?
Fires when a ticket property changes in HubSpot. Combine with a property filter to react only on key transitions (e.g. pipeline stage to Closed).
Is the Ticket Updated trigger real-time?
Yes. Ticket Updated uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in HubSpot.
What data does Ticket Updated return?
The full event payload from HubSpot. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter Ticket Updated so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need HubSpot admin permissions to use Ticket Updated?
For most HubSpot accounts a standard user can authorize the trigger. Some HubSpot plans require an admin to enable third-party webhooks. Check HubSpot's docs if the trigger fails to register.
More triggers
Other HubSpot triggers.
Trigger
New Company
Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.
TriggerCompany Deleted
Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.
TriggerCompany Property Changed
Fires when a specific company property changes in HubSpot. Use a property filter to react only on changes you care about (e.g. lifecycle stage).
TriggerNew Contact
Fires when a new contact is created in HubSpot. The standard inbound hook for routing, enrichment, and welcome flows.
TriggerContact Deleted
Fires when a contact is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.
Build a workflow on this trigger.
One trigger. 23+ downstream actions. Zero glue.