Automation Rule to update de-activated page owners from Parent page

[#1]

IF you have tons of pages with de-activated owners in your Confluence org, with automation rule you can now run a scheduled task to update them with parent page owners (active ones of course).

AUTOMATION RULE: Updating page owners from Parent page
Description: If a child page has a de-activated owner, it gets updated with the parent page's active owner.
Scope: Single Confluence space (space ID)

TRIGGER
- Scheduled: weekly, every Thursday at 18:30 (Europe/Berlin)

FLOW
For each page in the space whose owner is a deactivated user:

1. Fetch page details
GET https://yoursite.atlassian.net/wiki/api/v2/pages/{{page.id}}
(Basic auth, Content-Type: application/json)

2. Create variable "PageVersion" = {{webResponse.body.version.number.plus(1)}}
(current page version + 1, needed for the later update)

3. Continue only if the response status = 200.

4. Continue only if {{webResponse.body.parentType}} = "page".

5. Create variable "parentPageId" = {{webResponse.body.parentId}}

6. Continue only if parentPageId is not empty.

7. Fetch parent page details
GET https://yoursite.atlassian.net/wiki/api/v2/pages/{{parentPageId}}

8. Create variable "parentOwnerId" = {{webResponse.body.ownerId}}

9. Look up the parent owner's user profile
GET https://yoursite.atlassian.net/wiki/rest/api/user?accountId={{parentOwnerId}}

10. Continue only if {{webResponse.body.accountStatus}} = "active".

11. Update the child page's owner
PUT https://yoursite.atlassian.net/wiki/api/v2/pages/{{page.id}}
Body:
{
"id": "{{page.id}}",
"status": "current",
"title": "{{page.title}}",
"ownerId": "{{parentOwnerId}}",

[Koloman Pfeffer]

Hi @Natalia Lezhai

Thanks for the guide and the suggestion to make such a rule, definitely very useful to reduce pages owned by noone.

A few things I found when recreating this myself: 

• Encode the authorization in base64 in Powershell, otherwise you could get 404 errors
  • Guide on how to do that here: https://community.atlassian.com/forums/Automation-articles/Jira-Automation-Linking-a-Confluence-page-with-Jira-issues/bc-p/2969949#M1846
• You will need the authorization and content-type header on each web request
• The body of the PUT web request got cut off in the original post and it should look like this, otherwise you'll get an error:
  {
  "id": "{{page.id}}",
  "status": "current",
  "title": "{{page.title}}",
  "ownerId": "{{parentOwnerId}}",
  "version": {"number": {{PageVersion}}
  }
  }
• For anyone asking what this looks like, here's my flow (for now with a manual trigger and without the branch to act on each page with a deactivated account): 

[Steve Rhodes]

I like this idea, but for the people on Confluence Standard I wonder if this is possible by using python or Google Apps Script. Thanks for the idea though. I'll look into it.