• [Wébinaire 13 novembre 2025] Comment l’IA optimise la performance marketing in HubSpot ?

    S'inscrire

Sales Hub Tools

Monjogard
Contributeur | Partenaire solutions Elite
Contributeur | Partenaire solutions Elite

Field dependencies in Playbooks

Résolue

Would be very useful with some smartness to questions in Playbooks (similar to dependent fields in HubSpot forms), e.g. ff answer is  X on question 1, show question 1B, otherwise move on to question 2.

 

A Playbook can become quite tedious for a sales rep to scroll through when not all questions are relevant to the conversation.

 

Also great if a Playbook could update properties on multiple objects within the same Playbook. Now a feature!

2 Solutions acceptées
Monjogard
Solution
Contributeur | Partenaire solutions Elite
Contributeur | Partenaire solutions Elite

Field dependencies in Playbooks

Résolue
0 Votes
hhiggins
Solution
Équipe de développement de HubSpot
Équipe de développement de HubSpot

Field dependencies in Playbooks

Résolue

Hi everyone! My name is Hallie, and I'm an Associate Program Manager on the CXM team here at HubSpot. I wanted to share an update that this is now live for playbooks! You can read more about the feature in this product update. Attached is a screenshot showing more information about using conditional properties in playbooks (in addition to the screenshot in this comment) : 

Screenshot 2025-04-21 at 10.43.50 AM.png

Voir la solution dans l'envoi d'origine

0 Votes
63 Réponses
WinnieHien
Équipe de développement de HubSpot
Équipe de développement de HubSpot

Field dependencies in Playbooks

Résolue

Hey everyone!

 

A while back I commented here about conditional/“dependent” fields in Playbooks. I wanted to circle back because we’ve made some progress and have more clarity now.

We’re actively working on Process Guides — the next evolution of Playbooks — and one of the biggest new capabilities is conditional sections (showing/hiding steps based on previous answers). This is meant to solve the exact pain point many of you have raised here: long, rigid Playbooks that are hard to use on live calls.

I’ve shared more details and a focused question in a new Ideas thread here:
👉 Process Guides: Conditional Sections as a Replacement for Playbooks

Would love for you to take a look and let us know: would conditional sections (plus a few core features) be enough for you to fully switch from Playbooks? Your feedback there will help us decide what’s truly needed before GA.

Thanks to everyone who’s shared input here already — it’s been super helpful in shaping where we go next. 

 

Best, 

Winnie 

Product Manager, Playbooks & Process Guides

cc: @lauragil@TDeGuzman@ErikaJ@BBellon@Brandon7051@MdeWit9@HHutson@ChrisBreitbach@SlimBob@Aleena_Malik@DouglasW@AaronBoatin@CDouglas4@JenPickard@nelmsbrad@BSegal@DPeacock@AKnechtl0@BLewty@MFerret


Tagging y'all because your feedback showed you're really interested in conditional sections. Would love to hear what you think! 

lauragil
Participant

Field dependencies in Playbooks

Résolue

I would love to see HubSpot take Playbooks to the next level by introducing conditional sections, if/then logic branching, and multi-step flows. These additions would significantly enhance the flexibility and power of Playbooks across Sales, Service, and Onboarding teams.
 
Imagine Playbooks that adapt dynamically based on user inputs; guiding reps through smart, context-aware conversations or processes. For example:

  • If a customer selects “Enterprise” then show advanced qualification questions.
  • If a rep logs a technical issue, then automatically load the troubleshooting steps.
  • If onboarding step A is complete, only then show step B with relevant instructions.

This would turn Playbooks into truly interactive workflows, helping ensure consistency while saving reps time and reducing errors. A more intelligent Playbooks tool could easily become a central hub for guided processes in HubSpot.

 

This need has become even more clear from my experience using Playbooks internally. I created the questions in the order steps should be followed, but users often repeat steps or skip some by mistake. A recurring piece of feedback is that seeing the entire Playbook at once can feel overwhelming. On top of that, having to skip steps manually (as per instructions) based on previous answers can be confusing; especially when users are in a rush, which increases the risk of missing critical steps.

 

What do you think @hhiggins @WinnieHien ??? Would love to hear your thoughts!

 

hhiggins
Solution
Équipe de développement de HubSpot
Équipe de développement de HubSpot

Field dependencies in Playbooks

Résolue

Hi everyone! My name is Hallie, and I'm an Associate Program Manager on the CXM team here at HubSpot. I wanted to share an update that this is now live for playbooks! You can read more about the feature in this product update. Attached is a screenshot showing more information about using conditional properties in playbooks (in addition to the screenshot in this comment) : 

Screenshot 2025-04-21 at 10.43.50 AM.png

0 Votes
WinnieHien
Équipe de développement de HubSpot
Équipe de développement de HubSpot

Field dependencies in Playbooks

Résolue

Hi, I'm Winnie the Playbooks PM. We just went into Private Beta with Conditional Properties in Playbooks this week. It allows for dependent fields or conditional property options in Playbooks. 

 

The rollout is for property based conditional logic. It does not include section based conditional logic nor if/then branching.  

 

If conditional sections or if/then logic branching is what you're looking for, I'd love to learn more! That isn't possible in current Playbooks given the way it was built so my team is actively exploring a new feature we're calling Process Guides for enforcing process in HubSpot. A big part of this feature will be conditional sections / steps and multi-step flows.   

 

We're gathering input from customers on what the top processes they care about are. Check out the loom linked in this survey to see a demo of an early proof of concept and and help us out by filling out the survey by Dec 15th, 2024!

 

The survey is open to any HubSpot customer or prospect. This data will help us decide if we're can move ahead with this project, so please help us out by filling out the survey! 

SkeeStylus
Contributeur de premier rang | Partenaire solutions Platinum
Contributeur de premier rang | Partenaire solutions Platinum

Field dependencies in Playbooks

Résolue

@Monjogard where are you seeing this?  Clearly this is in Private Beta.  Mind sharing?  Event if its just the KB articel?


Small Juan Headshot HubSpot CommunityJuan C. Perez

HubSpot Enthusiast | Certified Implementation Specialist
Subscribe to weekly product updates in 3 snack-sized bitesBook A Meeting Icon

Was was this helpful? Great, mark it as a solution.



0 Votes
SkeeStylus
Contributeur de premier rang | Partenaire solutions Platinum
Contributeur de premier rang | Partenaire solutions Platinum

Field dependencies in Playbooks

Résolue

@Monjogard is that a deep state private beta lol.  Because I don't see that.  Please share a link, even the KB article if you can. 


Small Juan Headshot HubSpot CommunityJuan C. Perez

HubSpot Enthusiast | Certified Implementation Specialist
Subscribe to weekly product updates in 3 snack-sized bitesBook A Meeting Icon

Was was this helpful? Great, mark it as a solution.



0 Votes
Monjogard
Solution
Contributeur | Partenaire solutions Elite
Contributeur | Partenaire solutions Elite

Field dependencies in Playbooks

Résolue

Now in beta!!

Screenshot 2024-11-21 at 14.50.39.png

0 Votes
TDeGuzman
Participant | Partenaire solutions Diamond
Participant | Partenaire solutions Diamond

Field dependencies in Playbooks

Résolue

Yes, similar to forms -- would love to be able to show/set a mandatory field depending on a response from another field.   

DHill5
Contributeur

Field dependencies in Playbooks

Résolue

Desperately need this for playbooks to be truly effective as a discovery tool.

0 Votes
ErikaJ
Participant | Partenaire solutions Platinum
Participant | Partenaire solutions Platinum

Field dependencies in Playbooks

Résolue

Absolutely critical to making playbooks worth using for live scenarios. When trying to convert a series of Yes or No questions into a playbook, it's difficult for teams to navigate where they should go next when they have to search through the playbook for the correct next step. 

Courtney_Clark
Participant

Field dependencies in Playbooks

Résolue

Developers... please work on this. 🙂

0 Votes
BBellon
Participant

Field dependencies in Playbooks

Résolue

Playbooks are a very cool feature but practically useless without conditional questions.

0 Votes
SkeeStylus
Contributeur de premier rang | Partenaire solutions Platinum
Contributeur de premier rang | Partenaire solutions Platinum

Field dependencies in Playbooks

Résolue

We can do this in qualifying leads on chatbots and would be helpful to have branching logic in playbooks.


Small Juan Headshot HubSpot CommunityJuan C. Perez

HubSpot Enthusiast | Certified Implementation Specialist
Subscribe to weekly product updates in 3 snack-sized bitesBook A Meeting Icon

Was was this helpful? Great, mark it as a solution.



0 Votes
MRuff4
Participant

Field dependencies in Playbooks

Résolue

+1

0 Votes
McBainKD
Contributeur

Field dependencies in Playbooks

Résolue

+1 just came across the need for this today!!

0 Votes
Dr_Aur
Participant

Field dependencies in Playbooks

Résolue

We need this !!!!

0 Votes
JMannessen1
Participant | Partenaire solutions Platinum
Participant | Partenaire solutions Platinum

Field dependencies in Playbooks

Résolue

+1 Would be great and usefull! 

0 Votes
lauragil
Participant

Field dependencies in Playbooks

Résolue

Is this feature on the roadmap?

0 Votes
AdminEpicDanta
Participant | Partenaire solutions Platinum
Participant | Partenaire solutions Platinum

Field dependencies in Playbooks

Résolue

This is 100% needed. 

0 Votes
LauGil
Participant | Partenaire solutions Platinum
Participant | Partenaire solutions Platinum

Field dependencies in Playbooks

Résolue

This is necesary! 

0 Votes