# Use NEW custom behavioral event as a Workflow trigger

**URL:** <https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198>\
**Category:** HubSpot Ideas\
**Tags:** workflows\
**Created:** [June 1, 2021, 7:31am UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198 "2021-06-01T07:31:00Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sambo](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/sambo/32/34870_2.png) [@Sambo](https://community.hubspot.com/u/Sambo)\
**Post date:** [June 1, 2021, 7:31am UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/1 "2021-06-01T07:31:00Z")

</div>

There is a new Behavioral Event functionality for Marketing Enterprise, and the old one is marked as a “legacy”. The new one supports only **Delay until event happens** feature on workflows. [Knowledgebase article](https://knowledge.hubspot.com/analytics-tools/create-custom-behavioral-events) explains how it works, but currently, you can’t use events for anything else but delays.

We want to use Behavioral Events also as **a trigger** – not delay. For example, when event X happens, we want a Slack notification.

This is an important feature for especially **Sales and Service,** when something critical happens. Also, Marketing people can benefit from this. When notification reaches proper persons, they can serve better customers in real-time.

---

<div class="post-metadata">

**Author:** ![mcraciun](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mcraciun/32/48852_2.png) [@mcraciun](https://community.hubspot.com/u/mcraciun)\
**Post date:** [June 1, 2021, 2:19pm UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/2 "2021-06-01T14:19:38Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![vgupta2](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/vgupta2/32/29368_2.png) [@vgupta2](https://community.hubspot.com/u/vgupta2)\
**Post date:** [June 27, 2021, 5:43pm UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/3 "2021-06-27T17:43:08Z")

</div>

New to Hubspot and trying to upgrade our implementation - it’s shocking to me that this feature doesn’t exist.

---

<div class="post-metadata">

**Author:** ![AMarquardt](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/amarquardt/32/97852_2.png) [@AMarquardt](https://community.hubspot.com/u/AMarquardt)\
**Post date:** [June 29, 2021, 3:12pm UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/4 "2021-06-29T15:12:32Z")

</div>

@vgupta2 from what I can tell, you can do it, as long as you’re using the “legacy” behavioral events, it’s just odd that they rolled out a new feature with LESS functionality.

---

<div class="post-metadata">

**Author:** ![vgupta2](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/vgupta2/32/29368_2.png) [@vgupta2](https://community.hubspot.com/u/vgupta2)\
**Post date:** [June 29, 2021, 3:15pm UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/5 "2021-06-29T15:15:48Z")

</div>

@AMarquardt thanks! Yup I looked into it - my challenge with legacy behavioral events is that they can’t carry much data with them, so I am limited in personalization of outreach in the workflow

---

<div class="post-metadata">

**Author:** ![tomwright1982](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tomwright1982/32/79644_2.png) [@tomwright1982](https://community.hubspot.com/u/tomwright1982)\
**Post date:** [July 3, 2021, 3:54am UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/6 "2021-07-03T03:54:57Z")

</div>

I’m guessing this must be a temporary omission since the new behavioural events are still in beta? Could the Hubspot Team provide a rough idea of what this will be available so I can plan whether to implement using legacy or the new events please?

---

<div class="post-metadata">

**Author:** ![fdorval](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/fdorval/32/53612_2.png) [@fdorval](https://community.hubspot.com/u/fdorval)\
**Post date:** [August 3, 2021, 3:33pm UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/7 "2021-08-03T15:33:06Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![BVergess](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bvergess/32/29892_2.png) [@BVergess](https://community.hubspot.com/u/BVergess)\
**Post date:** [August 3, 2021, 7:14pm UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/8 "2021-08-03T19:14:41Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![jimthornton](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jimthornton/32/95715_2.png) [@jimthornton](https://community.hubspot.com/u/jimthornton)\
**Post date:** [August 5, 2021, 8:53pm UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/9 "2021-08-05T20:53:12Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![KDupont](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kdupont/32/99782_2.png) [@KDupont](https://community.hubspot.com/u/KDupont)\
**Post date:** [August 26, 2021, 4:39pm UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/10 "2021-08-26T16:39:31Z")

</div>

I am very interested to know about this as well. I think this has to do with that they try to take certain triggers out of the enterprise plan. Like send webhook and other wf triggers and force you to buy the operations hub as well.

---

<div class="post-metadata">

**Author:** ![Daniel1991](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/daniel1991/32/32521_2.png) [@Daniel1991](https://community.hubspot.com/u/Daniel1991)\
**Post date:** [September 9, 2021, 7:08am UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/11 "2021-09-09T07:08:20Z")

</div>

We also use a lot of Custom behaviour events to track our users on our web app, and it’s frustarting with the lack of customization with the workflows on this.

We want to have the ablity to have an If/Then with the trigger of a behaviour event in the last X amount of days so we know who’s active or not. Right now, we have nothing that can give us this.

---

<div class="post-metadata">

**Author:** ![JacquelineOng](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jacquelineong/32/78108_2.png) [@JacquelineOng](https://community.hubspot.com/u/JacquelineOng)\
**Post date:** [September 13, 2021, 12:48am UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/12 "2021-09-13T00:48:14Z")

</div>

Posting on behalf of a customer who’s using custom behavioural events here:  
_I want to create, tasks, trigger email sequences, assign leads, update lifecycle stages based on the events which are being triggered._

---

<div class="post-metadata">

**Author:** ![TristanGray](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tristangray/32/62359_2.png) [@TristanGray](https://community.hubspot.com/u/TristanGray)\
**Post date:** [September 13, 2021, 12:55am UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/13 "2021-09-13T00:55:18Z")

</div>

Blows my mind that some fool at hubspot has removed the ability to trigger workflows based on events. What a stupid decision

---

<div class="post-metadata">

**Author:** ![CTrujillo](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ctrujillo/32/52876_2.png) [@CTrujillo](https://community.hubspot.com/u/CTrujillo)\
**Post date:** [September 20, 2021, 1:20pm UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/14 "2021-09-20T13:20:45Z")

</div>

I figured that you can create 2 workflows that are the exact same, both wait for and trigger each other after stop waiting.

WF: waiting for event #1

1) Enrollment trigger: Manual, enable re-enrollment

2) Delay until the event happens. 1825 days.

3) enroll in another workflow: waiting for event #2

WF: waiting for event #2

1) Enrollment trigger: Manual, enable re-enrollment

2) Delay until the event happens. 1825 days.

3) enroll in another workflow: waiting for event #1

Opinions?

---

<div class="post-metadata">

**Author:** ![CTrujillo](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ctrujillo/32/52876_2.png) [@CTrujillo](https://community.hubspot.com/u/CTrujillo)\
**Post date:** [September 21, 2021, 2:54pm UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/15 "2021-09-21T14:54:25Z")

</div>

Never mind!!!

 ![CTrujillo_0-1632236028285.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/d/7/d7e140443f3d64b6178328c5ad80f7351d899707.png)

---

<div class="post-metadata">

**Author:** ![JLee76](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jlee76/32/99782_2.png) [@JLee76](https://community.hubspot.com/u/JLee76)\
**Post date:** [October 18, 2021, 1:25am UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/16 "2021-10-18T01:25:12Z")

</div>

we would love to have custom behavioral events mapped onto property fields so we can use marketing automations for this (if customer conducts action X, send email Y)

---

<div class="post-metadata">

**Author:** ![Bausbrooks](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bausbrooks/32/30191_2.png) [@Bausbrooks](https://community.hubspot.com/u/Bausbrooks)\
**Post date:** [October 20, 2021, 8:28pm UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/17 "2021-10-20T20:28:08Z")

</div>

Absolutely this should be implemented. I’m really not sure why this wasn’t the initial reason behind the change.  
In the meantime, I am trying to use the behaviors to reflect on contact properties. Ideally, I’d use the custom event as a trigger to increase the field by +1.  
Any ideas for workarounds?

---

<div class="post-metadata">

**Author:** ![CTrujillo](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ctrujillo/32/52876_2.png) [@CTrujillo](https://community.hubspot.com/u/CTrujillo)\
**Post date:** [October 20, 2021, 9:33pm UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/18 "2021-10-20T21:33:04Z")

</div>

I created a workflow that everybody is enrolled with 256 DELAYS UNTIL EVENT IS TRIGGERED. Every time is triggered, something is happening (increase a counter, email is triggered, alert to an internal team member)  
I hope we dont get to 256 before the final solution is implemented

---

<div class="post-metadata">

**Author:** ![Cnadler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/cnadler/32/17554_2.png) [@Cnadler](https://community.hubspot.com/u/Cnadler)\
**Post date:** [October 26, 2021, 9:27pm UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/19 "2021-10-26T21:27:11Z")

</div>

+1 - custom behavioral events was sold as a robust feature but not being able to use it in workflows or lists is a real problem.

---

<div class="post-metadata">

**Author:** ![derekcavaliero](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/derekcavaliero/32/24634_2.png) [@derekcavaliero](https://community.hubspot.com/u/derekcavaliero)\
**Post date:** [November 1, 2021, 7:03pm UTC](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198/20 "2021-11-01T19:03:57Z")

</div>

I really don’t understand how a beta of this feature was rolled out without support for use in (arguably) the most important functionality HubSpot offers (workflows and automation). Right now its just a very clunky version of something you can do much more effieciently via Google Analytics.

[Next page](https://community.hubspot.com/t/use-new-custom-behavioral-event-as-a-workflow-trigger/38198.md?page=2)
