Using a single Playbook multiple times on the same record

HubSpot Ideas

Status: Not Currently Planned

Status history

1

We work with clients again and again on multiple projects. We need to be able to save the same playbook to a record multiple times. Example, let’s say there’s a project planning playbook where we go through a set of questions that we ask the client and have pre-call research. We want to save this at the company level. We need this now, and for the project that comes up in a month, and we’ll need it again a month after that. Currently you have to clear our the data field by field which is confusing. And there’s no way to see all of your playbook submissions in one spot.

2

We have set ‘Notes’ / ‘Playbooks’ with Team Only permissions however we have found an error:

  • Once a Playbook has been submitted for a Contact, any User (even outside of the original User’s Team who submited the Playbook) can click into the Playbook and see what was previous submitted - the Playbook auto-fills the previous response.

I have raised this issue with HubSpot support who have confirmed the issue is currently under discussed with the dev team to edit this function in the future. A timeline has not been set so I have been advised to log this issue in the Ideas Forum.

Thank you.

3

I need this as well. We’re using playbooks to log every call and generate a custom object for the call log record so that we can generate reports with the call log data. Unfortunately, whenever I generate the object, it auto-associates it to the next instance of that playbook on the same company record. This won’t work because we have pre-call and post-call reports. Additionally, those reports get generated multiple times per year.

4

May 21, 2026 06:25 AM

Hi everyone,

I’m Winnie, the Product Manager for HubSpot Playbooks.

Thank you for taking the time to share this idea. We genuinely read and consider everything submitted on the communtity forum.

After review, we don’t have plans to build this right now. This is actually something we find interesting, but we have higher-priority work in flight that we need to see through first. It’s on our radar for future consideration.

When we explored this idea previously, we had to balance showing current data (what’s captured in Property fields) easily, with the option to reset to blank if it’s a new entry. If this is something that’s still important to you, could you share back your thoughts on this: If you had the option to reset to blank, are there still certain questions you’d want populated with current property data?
For questions that don’t have property updates, I think the ask is clear. The abiltiy to clear the draft stage or reset to default.

We revisit our roadmap regularly, and customer ideas like this one do influence what we prioritize. Please continue to leave comments and upvotes. I usually reach back out on the Community Forum and will DM folks that have commented to jump on calls to learn more about the use case, or to recruit for early beta testing.

Thanks, Winnie

5

Just jumping in to say I highly agree with this request. We are struggling with playbooks geting opened before all consult prep work is complete and then it retaining old prep work no the new ones. And when it doesnt show the current value, i is completely useless to our team. We’d also like to be able to save the fields without logging the event (example: we are doing call prep. The rep opens the playbook to prepare and sees some errors, requests the sales assistant fixes them, but when the fields are updated, the playbook does not update to the new field. It retains the old information until the log is made.