eSign Documents supports integration with Confluence Automation workflows.
-
For an example of using Automation to send email on an eSign Document event see How to integrate Confluence Automation Rules with eSign Document Events
-
For details on the capabilities of Atlassian Cloud Automation, see https://support.atlassian.com/cloud-automation/docs/confluence-cloud-automation/. Contact Atlassian support for development guidance.
Webhook Events
The following Events in eSign can initiate customer Automation Rules. These webhooks are configured in Space Settings
|
Event |
Description |
webhook.body.eventType |
|---|---|---|
|
On Start |
When a new document revision is started |
START |
|
On Approve |
When a reviewer approves a document revision |
APPROVE |
|
On Reject |
When a reviewer rejects a document revision |
REJECT |
|
On Finalize |
When a document revision has been approved by all reviewers |
FINALIZE |
|
On Release |
When a document revision has been published to the release location. Note the contentid here references the releaseCopy. |
RELEASE |
|
On Training |
When a user has recorded training completion against a document. |
TRAIN |
Webhook Data
eSign sends the following information to Automation with each event. This data can be used in Automation smart values, or to control the rule as it is processed.
-
Access individual fields in Automation smart values like {{ webhook.body.contentTitle }}
-
Print out all fields (useful for development) using {{ webhook.body }}.
Sample Data Payload
{
eventType: "RELEASE", // see table above for eventType values
spaceKey: "DR",
contentId: "46379...",
contentRole: "RELEASE",
contentTitle: "Corporate Product Development Lifecycle POL001(03)",
docId="POL003",
docName="Corporate Product Development Lifecycle",
docRevDesc="Revision 3 introducing new section of AI testing",
docSlug="DC003(03)",
docType="Policy"
status="RELEASED",
statusTs="2025-12-19T20:12:16Z",
userId="5dbde7604ff1...",
userName="John Hancock"
}