Problem

Customers can't access Confluence page watchers via smart values for automation, unlike in Jira where watchers' details are easily retrievable.

• issue.watchers.displayName - Returns the watcher's display name.

• issue.watchers.emailAddress - Returns the watcher's email address.

 
Even though, we have the 'Manage watchers' action:

This action adds or removes specific people or groups as watchers on a page or blog post, as defined by the trigger.

Select (or type) which watchers to add or which ones to remove.

This gap limits automation's potential for notifications and watcher management in Confluence.

Suggested Solution

Implement smart values for accessing page watchers' information in Confluence Cloud, similar to Jira's functionality.

This would enable dynamic watcher management and the inheritance of watchers for child pages through automation 

Why This Is Important

Accessing page watchers through smart values would enhance automation in Confluence by allowing for personalized notifications and efficient watcher management. 

Workaround

A possible workaround involves using the "Manage watchers" action in automation for adding or removing watchers.

For more advanced management, the Confluence Cloud REST API offers endpoints for managing page watches (https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content-watches/) ,which could be merged with the 'Send web request' Action, if applicable.

While serviceable, these methods lack the convenience and integration that smart values could provide.