Automate page creation with hierarchy and date-based labels.

Question

Hi,

We create two pages weekly, each containing the 'Page Properties Report' macro, and we want to automate this process. I have created a global template that includes the Page Properties Report macro, which can be used in the automation. However, I need assistance with the following requirements:

Requirement 1:

When the automation runs, the pages should be created under their respective parent pages.
For example:

* Pages "Release 2024.12.03" and "Release 2024.12.04" should be created under the parent page 'Release 2024' > 'Release 2024.12'.
* Next month, when the rule runs, pages "Release 2025.01.03" and "Release 2025.01.04" should be created under 'Release 2025' > 'Release 2025.01'.

The parent page "Release 2025" can be created manually, but the monthly and weekly pages need to be automated.

Requirement 2:

When the pages are published, the 'Page Properties Report' macro should automatically update the 'label' filters with the creation date of the page.
for eg:

* If the page is created on January 3, 2025, the macro should use the label filter 20250103.
* Similarly, for January 4, 2025, the label filter should be 20250104.

Sushil Ranjan_csk0y5 · Answer

Hi Bill,

Apologies for the delayed response, yes I was working on this and achieved this task after lots for RnD, and yes it was indeed a valuable learning experience for me.

Steps for my rule:
1. Scheduled trigger
2. Send Web Request: looking for dynamic parent page
3-5. Audit log {webResponse.body} : to get page title & id
6. Send Web Request: Creating page under webResponse.body.results,id

tricky part was to edit the page and update the label with dynamic date.
for that we learned to add "View Storage Format" of the page (JSON Scape), modify the label date like {{yyyymmdd}} under body of custom data of the rule.

edit: same way we created separate rules for Monthly {{yyyy.MM}} & Yearly Release {{yyyy}} page.

Thanks for all you help.

Regards
Sushil

Bill Sheboy · Answer

Hi @Sushil Ranjan

I am following up to learn if you are still working on this one or if the suggestions resolved it.  If resolved, please mark this question as "answered" to help others with similar needs find solutions faster.  Thanks!

Kind regards,
Bill

Bill Sheboy · Answer

Thank you for the additional information.

To dynamically set the parent page in the action, you could try creating a variable for the parent page name (based on the current date) and then entering the variable in the action.

If that action will not take a variable for the parent page, you will instead need to use the Send Web Request action to call the REST API endpoint for page creation.

For your second question, you are correct there is no automation action to "edit page", as that would likely be quite complex regarding formatting.  Instead, you could use the Send Web Request action to call the REST API endpoint to first get the page content, make changes to the returned content, and finally to make a second call to the edit page endpoint.  As the specifics of your content impact how to do this, you will likely need to experiment to get this to work as needed.

Here are some references that should help do this:

* how-to article for calling a REST API endpoint from a rule: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828
* endpoint to create a page: https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-page/#api-pages-post
* endpoint to get a page: https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-page/#api-pages-get
* endpoint to update page: https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-page/#api-pages-id-put
* examples of different page scenarios: https://developer.atlassian.com/cloud/confluence/rest-api-examples/