Pipeline Stage checks for specific property value

HubSpot Ideas
1

I think it would be a good idea to allow the possibility of setting a stage based on specific property values. Example: deal property that is a single checkbox must be marked ‘yes’ to place into a specific stage.

2

Hello @KRhoads ,

If I’m understanding properly, I would say this is already possible in HubSpot.

Here’s some explanations:

  • You could build a deal-based workflow that triggers whenever the checkbox becomes checked.
  • Whenever that happens, you could use the “set property” action and change the “deal stage” so that it goes exactly in the stage you want.

You could either create other workflows for other checkboxes and/or values, or add if/then branches to this one workflow so it also checks other possibilities.

I hope this helps!

3

Hello @SamStAmour ,

Thanks for the idea. To clarify, I am suggesting that HubSpot should make it possible to require a specific value for the user to change the stage.

Example:
Let’s say I have a deal stage “request urgent quote” and I have a property called “priority” that can have any of the following values: “high”, “medium”, “low”.
I would want the “priority” property to be filled out with a value of “high” in order for the user to place the deal into the “request urgent quote” stage.
In this example, right now in HubSpot I can only require that the user mark any value for the “priority” property, but I cannot require that they mark the value of the “priority” property as “high”. They could effectively place the deal in “request urgent quote” stage with it having a “low” priority.

We can move deals automatically between stages based on property values, but we can’t lock down the movement of a stage manually by a user based on specific property values.

4

@KRhoads Gotcha! Could be interesting in certain cases indeed.

5

We would also benefit from being able to set not only required properties at pipeline stage changes, but require sepcific property values at stage changes.

Our use case:

We are a SaaS company using a ticket pipeline for following up churn, where there are 3 roles involved when a customer wishes to terminate. We have 3 properties for each of these roles (in addition to the ticket’s owner), each with an own “Status” property with dropdown values of “Not started, In progress, Complete”. We would like to require that all 3 of these properties are set to “Complete” in order to set the ticket to closed.