...
| Info |
|---|
Confluence Automation is a powerful tool that is supported available in certain editions of Confluence Premium and above. Online help for atomation automation is available here: https://support.atlassian.com/cloud-automation/docs/confluence-cloud-automation/ For information and support on Automation please contact Atlassian. |
...
Select Incoming webhook, then Next.
...
Then select For each: add a branch > Branch Rule / related entities.
Add the following CQL query to the branch rule to allow automation to find the context page.
...
https://support.atlassian.com/cloud-automation/docs/confluence-cloud-automation/
Step
...
2 - Add actions to the Rule - Send email
Select THEN: Add an action > Send email
Complete the 3 email fields with something like this:the following. Any smart values from the Confluence page or eSign Document (webhook.body) can be added as content.
Field | Example |
|---|---|
To | <your name> |
Subject | Document {{webhook.body.docId}} revision {{webhook.body.docRev}} has been released |
Content | This document has been released. Access it here: {{page.url}} eSign Document information: |
...
Press Next.
Step 2B - Add actions to the Rule - Apply label
Select THEN: Add an action > Apply label
In this example, add a dynamic label containing the document Id with the following code:
...
Field
...
Example
...
labels
...
{{webhook.body.docId}}
...
Press Next
Press Turn on Rule and give it , then Turn on Rule
Give the rule a name (e.g. “Document Release - Notify and Label”Email Notify”)
Step 3 - Link this Webhook to
...
Document Release
...
In Automation Rule, click on the Incoming Webhook trigger and “Copy URL” to get the Webhook URL into the clipboard.
...
Step 4 - Test the Automation Rule
Take a document revision through the release process in eSign Document. If the rule integration is successful, an email will be sent with a link to the release copy.
If it doesn’t work, check the Automation Rule audit log. It can help troubleshoot.
...
| Info |
|---|
TIP - Add a delay for Release events. In some of our testing the Confluence rule was sometimes unable to find the new Released page as it was created moments before by eSign. Adding the 30s delay action after the webhook trigger node appeared to resolve that issue. |
Appendix: Additional Resources
Action - Apply label
In this example, add a dynamic label containing the document Id with the following code:
Field | Example |
|---|---|
labels | {{webhook.body.docId}} |
...
| Info |
|---|
Note that Confluence Automation rules run as the Actor configured in the Rule details. Rules that change pages are restricted by page security. For example, eSign can be configured to lock down released pages. In this scenario the Apply label action may be blocked by confluence security. |