HubSpot Trigger

Start a workflow when any HubSpot CRM record is created or one of its properties changes. It appears as HubSpot Trigger in the workflow builder and works across contacts, companies, deals, tickets, tasks, communications, meetings, emails, and services in one flexible node.

What It Does

Watches the HubSpot object type you choose and fires either when a new record of that type is created, or when a property on an existing record changes. For updates, you can watch a single property and add a condition on how its value changed.

When It Fires

Fires on every qualifying event, there is no per-record enrollment memory. If the same record qualifies more than once, such as a deal stage cycling back to Closed Won, the workflow runs again each time. Use a downstream deduplication node if you need once-per-record behavior. Property and value filters only apply to Updated events, not Created events. If you need to watch multiple properties on the same object type, add multiple trigger nodes.

Configuration

Configure the node with these settings:

Field	What it controls
Event Type	`created` or `updated`. Required.
Object Type	The HubSpot object to watch: `contacts`, `companies`, `deals`, `tickets`, `tasks`, `communications`, `meetings`, `emails`, or `services`. Required.
Watched Property	The property to monitor on Updated events. Required whenever `filterOperator` or `filterValue` is set.
Filter Operator	How to compare the watched property's value: `changes_to`, `changes_from`, `changes_to_any_of`, `changes_from_any_of`, `is_greater_than`, `is_less_than`, `crosses_above_threshold`, `crosses_below_threshold`, `changes_to_true`, `changes_to_false`, `is_set`, or `contains`. Required whenever `filterValue` is set.
Filter Value	The value to compare against. Required for operators that compare against a value.
Pipeline	Optionally scope the trigger to a specific pipeline, for object types that use pipelines, such as deals or tickets.

Outputs

The node passes these values downstream. Check the Outputs tab on the configured node to confirm exact paths.

Variable	Type	Description	Example
`hubspot`	`object`		`{{nodeId.hubspot}}`
`hubspot.event_type`	`string`	"created" or "updated"	`{{nodeId.hubspot.event_type}}`
`hubspot.object_type`	`string`	HubSpot object type identifier	`{{nodeId.hubspot.object_type}}`
`hubspot.object_id`	`string`	HubSpot record ID of the affected object	`{{nodeId.hubspot.object_id}}`
`hubspot.portal_id`	`string`	HubSpot account/portal ID	`{{nodeId.hubspot.portal_id}}`
`hubspot.occurred_at`	`string`	ISO 8601 timestamp of the event	`{{nodeId.hubspot.occurred_at}}`
`hubspot.watched_property`	`string \| null`	Internal name of the watched property. Required when using filterOperator or filterValue on Updated triggers; null for Created triggers.	`{{nodeId.hubspot.watched_property}}`
`hubspot.watched_property_value`	`string \| null`	New value of the watched property at trigger time	`{{nodeId.hubspot.watched_property_value}}`
`hubspot.watched_property_previous_value`	`string \| null`	Previous value before the change, null for Created triggers	`{{nodeId.hubspot.watched_property_previous_value}}`
`hubspot.properties`	`object`	Full key-value map of all properties on the record	`{{nodeId.hubspot.properties}}`
`hubspot.associations`	`object \| null`	Associated HubSpot records hydrated for the event, or null when association lookup fails	`{{nodeId.hubspot.associations}}`

Example Workflow

Set objectType to deals, eventType to updated, watchedProperty to the deal stage property, and filterOperator to changes_to with filterValue set to your Closed Won stage ID. The workflow fires only when a deal moves into that stage, then logs a note on the associated company.

Deal Updated
Company Updated
Contact Updated

Need More Help?

Reach the AskElephant support team by:

clicking the Support tab on the right side of your screen,
emailing [email protected],
or using @askelephant support in your dedicated Slack channel.