Hi Community,
I am starting to use the Confluence automation rules since they are now available for Confluence Standard (already using Jira automation rules since long).
Since Confluence Standard only include 100 runs per month, I have to be careful on the triggers for these rules, thus mainly want to use scheduled triggers.
With one rule that shall check for one space for every newly created pages (only for the first initial version) within a given time frame (weekly) and send a notification about these pages.
I have tried different approaches in how to check for all pages from a specific space and then check if it is a newly created version (or created within a timeframe), but I get errors, since either the pages cannot be found or then the CQL condition is wrong. See:
How can I correctly setup the automation rule that checks all pages of a space and send a notification if it is a newly created page (first version) without having too many rules that eat up too much of the max automation rule run limit?
Do you guys see another approach then to use the scheduled trigger for this case?
Thanks in advance!
Cheers,
Simon
Hi @Simon Sahli,
Would this Lookup action work?
I don't know your exact use case, but if you want to remind people to check the compliance of pages from a specific space, have you considered using Jira issues instead? You could create a recurring issue and include a Confluence search in the description (eg, https://yoursite.atlassian.net/wiki/search?spaces=ABC&lastModified=custom&from=2025-01-01)
Hope this helps!
- Manon
thanks a lot for your response and indeed this work for fetching the right pages, which currently works well for one newly created page.
One question though, if I have multiple newly created pages, which will be mostly the case, how can I create ONE notification with all page titles, and ideally the link to all the pages, that got recently created?
Which smart values should I use in the notification action for this case?
Thanks again!
/Simon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great, thanks for getting back to me!
The lookup action is great for that, here's how you can get the title and URL (and any other smart value you want from the page):
{{#lookupPages}}
* {{title}}
* {{url}}
{{/}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Manon Soubies-Camy , perfect, this is exactly what I needed.
This setup, in different variations, I will use for many use-cases, considering the limitations of the amount of automation runs that are possible the Confluence Standard subscription and therefore the need to control the amount of runs with scheduled jobs, rather then other triggers that might create a lot of runs.
I highly appreciate your response, thanks a lot!
Cheers,
Simon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.