Hi Community,
I am trying to create an automation rule that checks whether a Confluence page has been updated within the last hour. I attempted to use a schedule trigger with CQL, but discovered that the schedule trigger in Confluence automation does not support queries.
Is there another way to accomplish this task using Confluence automation?
Appreciate your help
Hi @Jiecai.Peng Trevor here from the Confluence automation team. Here is a working example of an automation rule that logs the titles of pages edited within the last hour:
If you want to access info about the page through smart values, the 'related entities' branch outputs the {{cqlResult}} smart value, which supports these fields:
If you need to access other smart value fields, we may be able to find a workaround. Just let me know!
Also, if your use case allows it, I would recommend you run the rule less frequently than every hour. If there is any delay in the rule executing, then it is possible for some piece of content that was updated exactly 60 minutes ago to slip through the cracks. For example, you could do the same rule but have it run every day and update the CQL like so: type = page AND lastmodified > now("-1d")
@Jiecai.Peng We have built an app that supports custom notifications in a super-flexible way.
You can define a flexible schedule, a CQL query, customize the email template and choose the recipients like this:
The CQL query in your case would be:
updated > now("-1h")
Would this meet your requirements?
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.
Have you had success with this Automation @Riley Venable I believe Im getting the same error.
CQL condition
Error in execution:
No CQL-compatible content found in the rule context; there is nothing to check against the CQL query. The CQL condition component can only follow components that involve CQL-compatible content, such as the blogpost published trigger, the publish new page action, or the related entities branch.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @James Totah I believe that rule will work if you replace the 'CQL condition' component with a 'Branch rule / related entities' component (and use the same CQL query).
The 'CQL condition' is a filter, it is used to stop or continue the rule execution based on the properties of the CQL content that last appeared in the rule. In the case of a scheduled trigger, there is no particular content to check against the CQL query.
The 'related entities' branch is more like a search mechanism, it allows you to find any piece of content you want based on the CQL query. In this case it looks like that is what you're looking for.
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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.