Set event enrollment triggers
Last updated: March 6, 2024
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 |
Set workflow enrollment triggers to automatically enroll records when an event is completed. Event triggers can be used if you want to trigger actions in a workflow only when an event occurs.
For example, you can use this to send an email when a form has been filled out or when a CTA has been clicked. Learn more about the differences between event triggers and filter-based criteria.
- 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.
Before you get started
When using event enrollment triggers, please note the following:- You cannot test record enrollment using event enrollment triggers. When testing enrollment, only filters in the AND only enroll contacts that also meet these filters used section will be taken into account.
- You cannot use scheduled triggers with event enrollment triggers.
- Call event triggers can only be used with calls initiated from HubSpot.
- When using marketing emails to set your event enrollment triggers:
- Only A/B marketing and automated marketing emails can be used for event enrollment.
- If a specific marketing email is not defined, actions taken on all marketing emails, including batch marketing emails, can cause a record to meet the event enrollment trigger.
Set event enrollment triggers
When setting up event enrollment triggers, all 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.To set up your 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.
- In the Add Trigger panel, select an event trigger.
- Within the same trigger group, click + Add trigger to further define your trigger. For example, you can further specify Ad interaction event triggers by Ad Network or Interaction Type.
- To add another trigger group, click + Add trigger group and continue setting up your trigger group.
- After setting up your event triggers, click Done.
- To further refine the records enrolled in the workflow based on additional filters, in the AND only enroll contacts that also meet these filters section, click + Add filter.
- You can select additional properties to refine the records that you would like to enroll in the workflow.
- Your event triggers must be saved before you can add additional refinement filters.
-
- When using refining filter criteria, the record must also meet these filters when 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 turn on re-enrollment, under the Should [object] be re-enrolled in this workflow? section, select Yes, re-enroll every time the trigger occurs.
- When you're done, click Save.
Change your workflow enrollment trigger type
If you've previously created a workflow using When a filter criteria is met or Based on a schedule triggers, you can update the workflow to use When an event occurs triggers. To change your workflow trigger type
- In your HubSpot account, navigate to Automation > Workflows.
- Click the name of the workflow or create a new workflow.
- In the workflow editor, click the [Object] enrollment trigger
- In the left panel, click Change trigger type.
- In the dialog box, click Confirm.
- Continue setting up your event enrollment trigger.
Event enrollment triggers
It is not possible to enroll records that did not complete an event. For example, you cannot enroll contacts who did not submit a form. However, you can use if/then branches in the workflow to determine if an event has occurred or not. Learn more about event workflow enrollment triggers in the table below:
Workflow type | Category | 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. This will not trigger if the call is manually logged. |
Contact | Calls | Call started | Triggers when a call is initiated through HubSpot. This will not trigger if the call is manually logged. |
All workflow types | CRM | Object created | Triggers when a new object is created in the CRM. This event does not have any associated properties. You must use refinement criteria to filter out unwanted objects from enrollment. |
All workflow types | CRM | Property value changed | Triggers when a property value is updated on a record in the CRM. This trigger represents exactly one property changing from one value to another. Unlike list-based filters, it does not account for historical operators like Updated in last [X] days. |
Contact | Clicked link in email | Triggers when a contact clicks a link in a marketing email. When further defining your email event enrollment triggers, please note the following:
|
|
Contact | Email bounced | Triggers when a marketing email is sent to a contact and bounces. | |
Contact | Email delivered | Triggers when a marketing email is delivered to a contact. | |
Contact | Email sent | Triggers when a marketing email is sent to a contact. | |
Contact | Opened email | Triggers when a contact opens a marketing email. | |
Contact | Replied to email | Triggers when a contact replies to a marketing email. | |
Contact | 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 contact views a form. The user that viewed the form must already be a contact in the CRM. Visitors who have not yet converted into contacts will not trigger an enrollment. |
Contact, company, deal and custom object | List | List membership changed | Triggers when a record is added or removed from a list. |
Contact | Meetings | Meeting booked | Triggers when a contact books a meeting. |
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 contact views a sales document. 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 contact clicks a CTA or Web interactive. |
Contact | Website | CTA (Beta) viewed | Triggers when a contact views a CTA or Web interactive. |
Contact | Website | CTA click (legacy) | Triggers when a contact clicks a CTA (legacy). |
Contact | Website | CTA view (legacy) | Triggers when a contact views a CTA (legacy). |
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. When configuring your triggers by URL, take note of the below elements: Example URL: https://www.hubspot.com/search. |
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. |
Differences between event triggers and filter-based criteria
Review the differences between filter-based triggers and event-based triggers in the table 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 are 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 an event has not occurred. | Events are based on something happening or an occurrence. As a result, it is not possible to determine if an event did not occur. However, you can use an if/then branch in the workflow to determine if an event has occurred or not. |