I started with tickets
Could an unstructured request become a usable category while a record is already moving through HubSpot? In my synthetic ticket demo, the decision step completed in about one second.
A HubSpot experiment
Bring Jev intoyour HubSpotworkflows.
I’ve been experimenting with Jev to make small decisions inside HubSpot workflows, like sorting enquiries, routing tickets, and tagging feedback. I’ve wrapped it in a workflow action and made it available for you to try.
Choose a property, give Jev some instructions, and see what it makes of your records.
An ongoing experiment. Currently limited to 100 requests per HubSpot portal per day.
Record enrolled
Classify with Jev
Use the result
What I’m exploring
Small decisions seemed like a good place to start.
One focused decision
I wanted to see what a small, specific AI action could do inside an everyday workflow.
Using existing choices
Jev works with the options in a HubSpot property, so I didn’t need to add a second list of categories.
A small workflow action
Your property is the starting point.
Pick the HubSpot property your team already reports on. Give Jev a few plain-English rules and the record details it should consider. Jev chooses a valid answer from that property's options.
- 1Choose your property
Use the categories already in your portal.
- 2Describe the decision
Write the guidance you would give a teammate.
- 3Use the result
Update the record or branch to the right follow-up.
A few ideas to try
A few things you could try.
Route incoming tickets
Read a customer request, choose the right team, and let your workflow create the follow-up.
Sort new enquiries
Turn free-text enquiries into the lead types and priorities your team already uses.
Try categorising feedback
Give recurring feedback a consistent label so it is easier to report on and act on.
Here’s one workflow I’ve tried
From a new ticket to the right follow-up.
I tried Jev with support, sales, and marketing requests. It selected the matching property value, and the HubSpot workflow created a task linked to the ticket. An uncertain result has its own review path.
The shown workflow uses synthetic tickets and a demo-only enrollment rule. It is an example to adapt to your categories and process.
Keep your workflow in control
Decide what happens with the result.
Jev can return a decision for your workflow to use, or update the property when you choose. Set a confidence threshold and send uncertain cases for review.
Use your own choicesNo duplicate category list
Choose when to updateDecision only or property update
See daily usage100 requests per HubSpot portal per day
Why I’m sharing it
I’m curious what you’ll try.
I’m curious what other people will do with this. If you have a workflow where a little classification could be useful, give it a try. I’d love to hear what worked, what didn’t, and what you tried that I hadn’t thought of.
Send me feedbackGood to know
Questions before you try it?
Do I have to create new HubSpot properties?
No. Select a property you already use. Jev reads its available choices and returns one of those values. You can also create a dedicated property if you want to keep a new classification separate.
Does Jev change the record automatically?
You choose. Jev can return a decision for later workflow steps, or update the selected property when the result meets your confidence threshold.
What happens when Jev is unsure?
Set a minimum confidence for updates and add a review path in your workflow. Your team stays in control of what happens to uncertain records.
Can I try Jev today?
Yes. I’ve made the experiment available to try from the HubSpot workflow action. It currently has a limit of 100 requests per HubSpot portal per day.
