Update company or contact fields within playbook

In our company we use playbooks to instruct sales and customer service employees.

In certain stages of the process we need then to check on company properties. It would be great if the playbook could show the current value of these properties and allow the user to enter them directly from the playbook.

In other words, not only enter  properties with predetermined values, but being able to create forms for ALL properties of the company/contact.


Especially since you can only display a limited number of properties on the default company page. It proves quite hard for sales people to manually browse/filter through ALL properties to find and fill in the proper ones (which vary per case). So playbooks would really resolve this in a very elegant way.

HubSpot updates
2 Replies
Regular Contributor

Currently, playbooks allow us to "Use a set of answers that saves to a property." This maps to the Contact, Company or Deal properties for a record as you fill in the playbook. The playbook is also prepopulated if the value was previously known. Awesome.


It would be wonderful if properties that do not have predetermined options, like Single-line and Multi-line Text, could also be used in Playbooks. This would allow us to collect all info, and have info prepopulated, for all property types. 

Please and thank you.

Regular Contributor

Having the ability to leverage playbooks to update values in non-dropdown/multi-select fields would be extremely useful and helpful for a variety of reasons:

  • Reporting:  Since we can't really leverage and report off of notes, being able to fill in numeric properties via playbooks can help front line folks (Sales reps and Support agents) quickly fill in this data during the normal course of interacting with a prospect or customer without having to search on the All Properties view of that record
  • Cross-Object Data Capture:  While this is possible now within a single playbook for pre-determined items, making this available for free form properties would be a huge timesaver for front line personnel to capture information across multiple objects

Please consider this on the roadmap.  The lack of this is actually inhibiting us from using Playbooks currently.