Skip to main content
Solved

Don't want automations triggered in workspaces that are set to "Do not track on pipeline"

  • June 3, 2026
  • 5 replies
  • 32 views
EP1
Forum|alt.badge.img

I use multiple Workspaces inside a Project. The first and main one with the Client to send their contract and get payments etc. Then another one with my internal employees, Team Workspace. Finally, we may also have a Contractor Workspace for things that are only for a contractor that we are handling directly for the client (as opposed to the client booking them). 

The thing I’d like to see is for Honeybook NOT to create automations that are for the Pipeline in these side workspaces. I have them set to “Not Tracked” or “Do not track on pipeline” to indicate that there is no need for a “sale” when I’m talking with a cake baker or my own employees. But I do send them files, sometimes they are files that need to be filled or signed like a W9 or an Independent Contractor Agreement. This triggers our pipeline sales automation which I always have to turn off, which is annoying.

I would like a feature request or a product update that would make it so no automations get triggered if the Workspace type is not the Client workspace and/or if the pipeline stage is set to “Do not track on pipeline”.

 

Thanks!

(Also, when do I stop being a Newcomer lol! I’ve been on HB since 2016)

Best answer by Alyssa Nance

I don’t use workspaces a ton in my business and neither do most of my clients, so I have never even considered the fact that an automation might trigger on those separate workspaces with the 2.0 builder. This is such a great point to bring up! So I think it would be so beneficial to be able to have a setting to control these scenarios specifically.

However, in the meantime, you could try using tags as a workaround. When you create the workspace, you can add a “team member”, “contractor”, or whatever you need to name the tag(s) to designate that workspace separate from when you want your automations to run. Then in the automation builder, you can add the “project tags added” conditional step and tell it which tag(s) you want to look for in that particular automation. Then you’d want all the rest of your actual automation steps to flow down the “no” path of that “project tags added” condition so that any workspace with the tag(s) goes down the “yes” path and ends the run.

If you’ve already gotten your automations built out, it should be as easy as opening up any automation that could potentially get triggered inside the “do not track” workspaces, and just add that condition step at the top.

 

Let me know if that all makes sense or if a video walkthrough might help!

5 replies

Alicia Bauer
Forum|alt.badge.img+4

​@EP1 -  This is a really interesting use case, and I can definitely see how it would become frustrating. If a workspace is marked as "Do Not Track on Pipeline" or is being used strictly for internal team members or contractors, it seems reasonable to expect it wouldn't trigger client-facing sales automations that are tied to pipeline activity.

I know there are currently some ways to control automation behavior through things like pipeline stages, automation conditions, and tags, but those don't necessarily address the specific issue you're describing where a non-client workspace is still triggering sales-related automations.

This would make a great feature request because it's very specific and easy for others with similar workflows to identify with and upvote. Having automations respect the workspace type or "Do Not Track" status could help prevent a lot of manual cleanup and reduce the risk of automations firing where they aren't needed.

And as for the "Newcomer" badge 😂, that's actually tied to your activity in the Community, not how long you've been a HoneyBook customer. If you haven't been posting, commenting, or engaging much in the Community, you'll keep the newer badge even if you've been a HoneyBook user since 2016. I'd say you've definitely earned more than "Newcomer" status by now! 💛

Alicia, Brand and Web Designer + Honeybook Pro
    EP1
    Forum|alt.badge.img
    • EP1
    • Author
    • Newcomer
    • June 4, 2026

    Thank you ​@Alicia Bauer super helpful! (FYI you show up as Newcomer to me too even with 395 replies! đŸ€”) 

    Alicia Bauer
    Forum|alt.badge.img+4

    ​@EP1 - Ha ha! I guess we will all be newbies forever! 💛

    Alicia, Brand and Web Designer + Honeybook Pro
    Alyssa Nance
    Forum|alt.badge.img+3
    • Alyssa Nance
    • Newcomer
    • Answer
    • June 11, 2026

    I don’t use workspaces a ton in my business and neither do most of my clients, so I have never even considered the fact that an automation might trigger on those separate workspaces with the 2.0 builder. This is such a great point to bring up! So I think it would be so beneficial to be able to have a setting to control these scenarios specifically.

    However, in the meantime, you could try using tags as a workaround. When you create the workspace, you can add a “team member”, “contractor”, or whatever you need to name the tag(s) to designate that workspace separate from when you want your automations to run. Then in the automation builder, you can add the “project tags added” conditional step and tell it which tag(s) you want to look for in that particular automation. Then you’d want all the rest of your actual automation steps to flow down the “no” path of that “project tags added” condition so that any workspace with the tag(s) goes down the “yes” path and ends the run.

    If you’ve already gotten your automations built out, it should be as easy as opening up any automation that could potentially get triggered inside the “do not track” workspaces, and just add that condition step at the top.

     

    Let me know if that all makes sense or if a video walkthrough might help!

    Alyssa Nance | Grace & Flow Systems | Systems Strategist
      EP1
      Forum|alt.badge.img
      • EP1
      • Author
      • Newcomer
      • June 11, 2026

      This makes sense to me, and I will definitely be looking for the fix, as the workaround adds extra steps. Cumulatively there are lots of workarounds for other things in HB, so every extra step adds load and labor. HB should always be looking at how to cut down the amount of work us solopreneurs need to do.

      Terms & PrivacyAccessibility statement

      © 2025 HoneyBook Inc.