Last updated: December 4, 2023
Available with any of the following subscriptions, except where noted:
Marketing Hub Professional, Enterprise
|
Sales Hub Professional, Enterprise
|
Service Hub Professional, Enterprise
|
Operations Hub Professional, Enterprise
|
Trigger a workflow enrollment when an event occurs on a record. For example, when a link is clicked in an email or when a page is visited.
- Previously created workflows using filter based or scheduled triggers can be changed to use event enrollment workflows by removing the triggers and then selecting event triggers.
- Some functionality available in the workflows tool is not available on workflows using event enrollment triggers. This includes: enrollment testing functionality, and scheduled trigger functionality. These will continue to work in all workflows that are not using event based triggers.
- Event triggers can only use A/B marketing and automated emails (emails sent using automation tools like workflows) for enrollment. Batch marketing emails sent using the email tool are not currently supported as event enrollment triggers.
- Call event triggers can only be used with calls initiated from HubSpot.
Set event enrollment triggers
- In your HubSpot account, navigate to Automation > Workflows.
- Click the name of the workflow or create a new workflow.
- In the workflow editor, click Set up triggers.
- In the left panel, select the when an event occurs. Set up the trigger, then click Apply filter.
- To further refine your trigger, click Add refinement filters. You can select additional properties to refine the objects that you would like to enroll in the workflow.
Please note: when using refining filter criteria, the refining criteria must be fulfilled at the time the event from the main trigger occurs.
- By default, records will only enroll in a workflow the first time they meet the enrollment triggers. To enable re-enrollment, under the Should [object] be re-enrolled in this workflow? section, select Yes, re-enroll every time the trigger occurs.
- Add additional enrollment triggers as required.
Please note: all event enrollment triggers will be separated using the OR operator. This means that only one of the event enrollment triggers must occur for the record to enroll in the workflow.
- When you're done, click Save.
Event enrollment triggers
Learn more about event workflow enrollment triggers in the table below:
| Workflow type | Tool | Event | Details |
| Contact | Ads | Ad interaction | Triggers when an ad is interacted with. |
| Contact | Calls | Call ended | Triggers when a call initiated through HubSpot ends. |
| Contact | Calls | Call started | Triggers when a call is initiated through HubSpot. |
| All workflow types | CRM | Object created | Triggers when a new object is created in the CRM. This event does not have any associated properties, therefore refinement criteria will need to be used to filter out unwanted objects from enrollment. |
| All workflow types | CRM | Property value changed | Triggers when a property value is updated on an object in the CRM. This trigger represents exactly one property changing from one value to another. In contrast to list-based filters, it doesn’t take into account historical operators like Updated in last [X] days. |
| Contact | Marketing email | Clicked link in email | Triggers when a contact clicks a link in a marketing email. |
| Contact | Marketing email | Email bounced | Triggers when a marketing email is sent to a contact and bounces. |
| Contact | Marketing email | Email delivered | Triggers when a marketing email is delivered to a contact. |
| Contact | Marketing email | Email sent | Triggers when a marketing email is sent to a contact. |
| Contact | Marketing email | Opened email | Triggers when a contact opens a marketing email. |
| Contact | Marketing email | Replied to email | Triggers when a contact replies to a marketing email. |
| Contact | Marketing email | Updated email subscription status | Triggers when a contact updates their email subscription status. |
| Contact | Form | Form interaction | Triggers when a contact clicks on a text field in the form. This event will trigger before a form submission, since the user needs to interact with the form in order to submit it. However, a user may interact with a form without submitting it. |
| Contact | Form | Form submission | Triggers when a form is submitted. When configuring your triggers by URL, take note of the below elements: Example URL: https://www.hubspot.com/search Base URL: the URL without the protocol or query parameters. (e.g. www.hubspot.com/search) URL domain: the domain only. (e.g. hubspot.com) URL path: the section after the domain (e.g. /search) |
| Contact | Form | Form view | Triggers when a form is viewed by a contact. The user that viewed the form must already be a contact in the CRM. Visitors that have not yet converted into contacts will not trigger an enrollment with this event. |
| Contact, company, deal and custom object | List | List membership changed | Triggers when an object is added or removed from a list. |
| Contact | Meetings | Meeting booked | Triggers when a meeting is booked with a contact in the account. |
| Contact | Meetings | Meeting outcome change | Triggers when a meeting outcome is changed in the account. |
| Contact | Sales documents | Contact finished viewing a document | Triggers when a contact has finished viewing a sales document. This occurs when the user completes the view by clicking out of the document. |
| Contact | Sales documents | Contact viewed a document | Triggers when a sales document is viewed by a contact. This represents the initial view of a document, regardless of whether the contact finished viewing it. |
| Contact | Sales documents | Document shared with contact | Triggers when a sales document is shared with a contact. |
| Contact | Sequences | Contact booked a meeting through a sequence | Triggers when a contact books a meeting through a sequence. |
| Contact | Sequences | Contact enrolled in a sequence | Triggers when a contact is enrolled in a sequence. |
| Contact | Sequences | Contact finished sequence | Triggers when a contact finishes a sequence. |
| Contact | Sequences | Contact unenrolled from sequence | Triggers when a contact is unenrolled from a sequence. |
| Contact | Sequences | Contact unenrolled from sequence via workflow | Triggers when a contact is unenrolled from a sequence via a workflow. Other unenrollment sources do not trigger this event. |
| Contact | Sequences | Contact unenrolled from sequence manually | Triggers when a contact is manually unenrolled from a sequence. Other unenrollment sources do not trigger this event. |
| Contact | Website | CTA (Beta) click | Triggers when a CTA or Web interactive is clicked. |
| Contact | Website | CTA (Beta) viewed | Triggers when a CTA or Web interactive is viewed. |
| Contact | Website | CTA click (legacy) | Triggers when a (legacy) CTA is clicked. |
| Contact | Website | CTA view (legacy) | Triggers when a (legacy) CTA is viewed. |
| Contact | Website | Page visited | Triggers when a contact views a landing page or website page. If a user views a page and has not yet converted from a visitor to a contact, this will not trigger the workflow. |
| Contact | Workflows | Achieved workflow goal | Triggers when a contact meets a workflow goal. |
| All workflow types | Workflows | Enrolled in workflow | Triggers when an object is enrolled in a workflow. |
| All workflow types | Workflows | Unenrolled from workflow | Triggers when an object is unenrolled from a workflow. |
Frequently Asked Questions
What are filter based criteria triggers?
Filter based criteria triggers are enrollment triggers that have been available since the workflows tool was created. They trigger workflows based on current information in an account.
What is the difference between event triggers and filter based criteria triggers?
Event triggers: trigger when an occurrence happens. For example, when a contact’s city changes to Dublin, do [X] action.
Filter triggers: trigger when a criteria is met. For example, contact’s whose city is equal to Dublin, do [X] action.
Event triggers can be used if you want to trigger actions in a workflow only when an event occurs. You can use this to send an email when a form has been filled out or when a CTA has been clicked.
View some of the differences between filter based triggers and event based triggers below:
| Trigger | Filter based trigger behaviour | Event based trigger behaviour |
| Is not a member of a list (Contact workflows) | Contacts that were either removed from a list OR added to a portal and not added to a list were enrolled in this workflow. | There are two events, Object Created event and Removed from a list event. You can add both events using “OR” when configuring your trigger. This means that you can further refine contacts that enter the workflow. |
| Re-enrollment | By default, objects are enrolled the first time they meet the criteria or you can configure the re-enrollment criteria. | You can enroll the object only once or each time the event occurs. |
| Associated object property data | You can access cross-object data when setting up your data in the Add filters step. Using the data panel, you can retrieve an associated object property in a workflow. |
|
| Has not filter (for example, (has not filled out a form, has not viewed a page, has not opted into a subscription etc.) | Workflows can be triggered if if an event has not occurred. | Events are based on something happening or an occurrence, therefore there isn’t a way to determine an event not happening. However, you can use the if/then branch in the workflow to determine if an event has occurred or not. |
Can I create workflows for events that have NOT occurred?
There isn't a way to determine an event not happening. However, within the workflow you can use the if/then branches to determine an answer.
