Are you referring to the contact object or lead object?
For the lead object, no, there aren't lead pipeline rules yet, like there would be for deal pipelines. I do however assume that the product team is working on these.
Imports, forms, APIs, the Salesforce integration, and the Set a property value action in a chatflow or workflow can only set a record's default Lifecycle stage property forward. To set the lifecycle stage backward via these tools, you will first need to clear the record's existing lifecycle stage value. The value can be cleared manually, or may be automatically cleared via a workflow or an integration that syncs contact data.
Yeah, I’ve run into the same issue before — definitely frustrating when leads can be moved backward without any guardrails.
Just a heads-up: HubSpot recently released a beta feature for Pipeline Rules on Leads that lets you restrict stage regressions, similar to what's available for Deals. Super helpful!
If you want to try it out, you can go to your Product Updates page and search for “pipeline rules for lead” under All Product Updates to request access.
Hopefully this helps cut down on those accidental stage changes!
Yeah, that can be annoying. I’ve wanted the same guardrails in Leads. Quick question: are you using permissions to lock down who can edit lead stages? HubSpot doesn’t have built-in rules to block stage regressions like it does for deals, but one workaround I’ve used is a custom workflow that flags or resets leads if someone tries to move them backward, less ideal, but it catches mistakes.
Are you referring to the contact object or lead object?
For the lead object, no, there aren't lead pipeline rules yet, like there would be for deal pipelines. I do however assume that the product team is working on these.
Imports, forms, APIs, the Salesforce integration, and the Set a property value action in a chatflow or workflow can only set a record's default Lifecycle stage property forward. To set the lifecycle stage backward via these tools, you will first need to clear the record's existing lifecycle stage value. The value can be cleared manually, or may be automatically cleared via a workflow or an integration that syncs contact data.