add an automation that adds a label to a new page based on a page property

Question

hello ,

I like to  add an automation that adds a label to a new page based on a page property,

or on the value of a variable.

The variable (list) I put in the page property.

we use atlassian cloud premium. I followed the rovo example but that does not work.
like using add label : {{page.properties.<property name>.lowercase}}.

what should I do??

Veronika Chachkova I Stiltsoft · Answer

Hi, @Ruud Kluit @James Gamble is right, it seems that native Confluence automation has a limitation here: the available smart values don't expose values from a Page Properties macro as {{page.properties.}}. So using native features to dynamically create a label based on a Page Properties value doesn't appear to be possible with the current automation syntax. On the other hand, if you are open to using third-party apps, Handy Macros could be a useful tool. With one of the macros, Handy Status, you can link a status to a page label when configuring the macro. Every time the status changes, the corresponding page label is automatically updated. You can also use a label prefix (e.g. status-draft, status-approved) for better traceability. If you need several statuses/labels on the same page, you can add multiple Handy Status macros with the required settings. Cheers, Veronika from Stiltsoft

James Gamble · Answer

Hola Ruud,

The smart value you’re trying to use isn’t currently supported. Confluence Automation exposes smart values for things like page title, labels, owner, parent, dates, and other page metadata. Still, it doesn’t expose values stored inside the Content Properties/Page Properties macro as something like {{page.properties.<name>}}. Atlassian has an open suggestion specifically for this limitation.

That means the Add label action itself can accept smart values, but Automation has no native smart value that can read the property value you’ve placed inside the page. Atlassian’s current list of supported Confluence smart values is here.

If that property is the source of truth, I don’t see a clean native-only way to make the label dynamic today. I’d vote for and watch AUTO-1158, since it requests exactly the ability to retrieve Page Properties values from Confluence Automation.

If you can change the design, I’d store the value somewhere Automation can already read, such as an existing page label, rather than duplicating it inside the Page Properties macro. Otherwise, you’d be moving into REST API parsing, which is much more complicated than the Automation you’re trying to build.

Thanks,

James