Property-based automation in HubSpot triggers a workflow the moment a specific CRM field changes. That change is the enrollment signal. No form submission is required. The system responds directly to what happens in your data.
This is the most precise way to automate follow-up in HubSpot. The trigger is tied to something that already carries meaning in your process: a lifecycle stage moving forward, or a deal property being set by a rep or an integration.
Go to Automation, then Workflows. Create a new workflow and choose the object type that holds the property you want to watch.
Under “When should contacts be enrolled?”, select Filter-based enrollment. Add a filter for the property you want to track. Set the condition to “is known”, “equals”, or “changed to”. To re-enroll on every change, tick “Re-enroll contacts every time this trigger is met”.
Add the steps that should run after enrollment. A typical workflow notifies a rep and updates a second property or creates a task. Each action executes once the trigger fires.
Use the Test tab to simulate enrollment for a specific contact. Confirm the trigger condition is met and the action preview shows what you expect.
Toggle the workflow live. Any record matching the trigger condition from this point forward will enroll automatically.
What types of property changes can trigger a workflow?
HubSpot supports property-based triggers across all object types. The most useful applications in practice:
- Lifecycle stage changes: enroll a contact when they move from Lead to Marketing Qualified Lead, or from MQL to Opportunity.
- Deal stage updates: create a task or send a notification when a deal reaches a specific pipeline stage.
- Custom property values: fire a workflow when a rep selects a product type, service tier, or region from a dropdown field.
- Contact owner assignment: start an introductory sequence the moment a contact is assigned to a new sales rep.
- Company property updates: enroll all associated contacts when the parent company’s account tier or industry is updated.
Date properties work differently. They use a date-trigger type and execute on a schedule relative to the date value. A renewal reminder workflow uses a date trigger, not a property-change trigger.
When does property-based automation work better than form-based enrollment?
Form submissions are the right trigger when a contact has taken an explicit action: requesting a demo or filling out a contact form on your website. Property-based triggers cover the scenarios that happen inside your CRM without any visitor action.
A rep manually qualifying a lead does not submit a form. A deal moving through pipeline stages does not submit a form. A billing integration updating a field does not submit a form. These events only exist as property changes, and property-based automation is the only way to respond to them automatically.
Teams that build their sales follow-up on HubSpot automation workflows typically start with form triggers and then move the most important sequences to property triggers once they see how reliably those fires match the intended moment.
How do you prevent enrolling the same contact twice?
HubSpot’s default behavior is single enrollment. Once a contact enters a workflow, they will not re-enter even if the trigger condition is met again later.
To allow re-enrollment, enable it in the trigger settings. You can configure re-enrollment to fire on every property change, which is useful for workflows that should respond each time a deal stage advances or each time a contact’s tier is updated.
The risk with re-enrollment is stacking duplicate tasks or triggering the same notification sequence multiple times in a short window. Adding a time-based delay and a branch condition that checks whether a previous enrollment is still active reduces this. The HubSpot workflow enrollment guide covers suppression and branching in detail.
Can you trigger a workflow from a custom property you built yourself?
Yes. A custom property you created behaves exactly like any default HubSpot property in the workflow trigger builder. The object type must match: a custom contact property triggers contact-based workflows; a custom deal property triggers deal-based workflows.
Property type matters for the filter condition. Text properties support “equals” and “contains”. Dropdown properties support “is known” and “equals any of”. Number properties support threshold comparisons like “is greater than” and “is less than”. Date properties use the date trigger path.
Teams building structured pipelines with HubSpot custom properties typically design them with automation in mind from the start. Using dropdown fields rather than free text makes trigger conditions deterministic and reduces the chance of a typo causing a trigger to miss.
What is the difference between “property is” and “property changed to”?
These two filter conditions control who gets enrolled and when.
- “Property is [value]”: HubSpot evaluates the current value at the moment you turn the workflow on, and enrolls any record already matching the condition. This can produce a large initial batch if your database already contains matching records.
- “Property changed to [value]”: enrollment only fires at the moment of change. Records that already held this value before the workflow went live are not enrolled. This is the right choice when you want the workflow to apply only going forward.
Using “property is” with re-enrollment enabled and a broad filter can result in runaway enrollment. Always preview first and review the enrollment history view after going live to confirm only the intended records are entering.
How do you troubleshoot a property trigger that is not enrolling contacts?
The most common reasons a trigger fails to enroll:
- The workflow is paused or off.
- The contact is suppressed by a list or exclusion filter in the “Don’t enroll” settings.
- Re-enrollment is disabled and the contact was already enrolled once.
- The property change happened before the workflow was activated and re-enrollment is off.
- The filter uses “is known” but the property was populated via an import that left the field blank.
Open the contact record and check the Activity tab for workflow enrollment events. If none appear, open the workflow and review the Enrollment history view. HubSpot logs the reason a contact was considered but not enrolled when a suppression rule or filter mismatch applied.
Frequently asked questions
Can a property-based workflow update the same property that triggers it?
Yes, but this creates a loop. If the workflow writes a value back to the trigger property that re-meets the enrollment condition, the contact re-enrolls and the workflow runs again. Use a branch condition to check whether the update has already been applied before writing to the field, or restrict re-enrollment to properties the workflow itself does not modify.
Do property-based triggers work on company and deal objects?
Yes. Company-based and deal-based workflows use the same trigger builder. Custom fields work the same way as default ones.
Does using property triggers affect the HubSpot workflow enrollment limits?
Property triggers count toward the same enrollment quotas as any other trigger type. The limits vary by subscription tier. This is an independent informational resource produced by a HubSpot Platinum Partner. HubSpot is a trademark of HubSpot, Inc.
Planning a HubSpot setup or integration in the region?
Contact us