Skip to main content
New Idea

Remove Watchers through Workflow Automator

Related products:Freshservice
  • October 3, 2025
  • 5 replies
  • 128 views

JaySpeer
Contributor
Forum|alt.badge.img+3

Through the Workflow Automator, we have the ability to add watchers but we do not have the ability to remove watchers.

For some background, all service items that require approval for our organization get sent to an Automation Agent Group until the request has been approved or rejected. The reason behind this is that our organization has accepted that IT will not work on items without the approval when approval is required so we use our Automation Agent Group as a triage space since some of our request items have true automation through web requests to fulfil the request. The gap we have is that often times, the approver responds to the request with questions that will drive their approval decision and no one regularly monitors the requests pending approval. 

Since there is an Action in the WFA to add a watcher, our idea was to build a custom object that will identify who the IT Business Partner for each department is and add them as a watcher to field any questions for requests coming from their respective teams while it’s pending approval. Once an approval decision has been received, we’d like to remove them as watchers so they aren’t receiving unneeded notifications.

We would love the ability to either remove individual watchers or all watchers through the WFA so that after the Approval Status changes from Requested, we can update appropriately.

5 replies

Forum|alt.badge.img+1
  • Community Debut
  • October 3, 2025

At the moment, Workflow Automator only supports adding watchers, not removing them. The workaround would be to handle notifications outside of the watcher mechanism (e.g., via conditional email actions or custom objects tied to request status). If removing watchers is important for your flow, I’d suggest raising it as a feature request — your use case (temporary watchers during approval) is a strong example of where the current limitation creates noise.


DanielRuff
Top Contributor ⭐
Forum|alt.badge.img+9
  • Top Contributor ⭐
  • October 9, 2025

Does anyone know how to handle this at the moment? I haven’t found a way through the API either. We want to automatically remove watchers when a ticket is moved to a restricted group. ​@Daniel Söderlund ?


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

Does anyone know how to handle this at the moment? I haven’t found a way through the API either. We want to automatically remove watchers when a ticket is moved to a restricted group. ​@Daniel Söderlund ?

Sorry, I haven’t found any way to do this. I have customer who is looking for it as well. Like when a ticket get moved to to a restricted group they need to make sure no one are watching or are shared outside the group. 


DanielRuff
Top Contributor ⭐
Forum|alt.badge.img+9
  • Top Contributor ⭐
  • October 9, 2025

Yes, that’s exactly the use case I’m currently exploring. Unfortunately, it’s not even possible via the API.

The only workaround I can think of is creating a note that helps the agent in the restricted group understand whether the ticket was routed directly to them or passed through another group first.


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

It’s the conclusion we came to