I am trying to create a newsletter that will be sent for specific content that was published in Confluence pages in the past month and will be sent at the beginning of each month with last month's materials.
I tried to write the cql according to the documentation and I am getting an error when running the cql although when I press the validation it seems ok and it even found 3 contents.
type = page AND label = trend_report_compliance AND created > startOfMonth("-1M") AND created < startOfMonth()
I received an error message after running the automation
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 blog post published trigger, the publish new page action, or the related entities branch.
Can anyone assist?
Thanks,
Tami
Hi @Tami Dubi
For a question like this, context is important for the community to help. Please post the following:
Until we see those...
To do what you ask with CQL and summarize the results, I believe you may need to use the Send Web Request action to call the REST API endpoint for searching the content, and then parsing the response: https://developer.atlassian.com/cloud/confluence/advanced-searching-using-cql/
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Scheduled Trigger for Confluence does not provide pages / content to the rule, and so the error is indicating that: there is no content to test with the CQL.
I believe that condition may only be used when there is content, such as with a page trigger or branch on related entities with the CQL. Neither of those would help with your scenario of sending a newsletter summary...which is why I suggested using the REST API with the CQL.
If you want to try that, please see the linked documentation I provided and this how-to article for calling the REST API from a rule: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy ,
Thanks, the rest API isn't an option that we can currently use.
The whole point in automation is the ability to create - no-code- solutions in Confluence.
Thanks for the effort.
If someone have any idea on how to implement it in the automation rules limitations please let me know
Best,
Tami
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Confluence rules are quite new compared to the Jira automation features, and so they [Atlassian] are likely still identifying candidate usage scenarios to improve the features. Additionally, rules rely upon the REST API, which at least allows customers to try to close gaps in what is currently available using the Send Web Request action.
In the mean time, you could investigate the Atlassian Marketplace for addon apps which may provide the type of reporting you need: https://marketplace.atlassian.com/
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.