Overview

eSign can be integrated with Confluence (or Jira) Automation rules to extend and customize eSign usage within your environment.

This capability is introduced through webhooks. The general configuration approach is as follows:

1. Create a new Rule in Confluence or Jira Automation triggered off a webhook.

2. Add one or more actions to the Rule.

3. Link the Rule into eSign by copying the webhook URL to the appropriate event in eSign App Settings.

Signature Events

Any or all of the following events can be linked to a webhook trigger in Atlassian Automation.

• Start Signatures

• Signature Invite

• Execute Signature

• Finalize Signatures

Enable the webhooks in eSign App Settings, available to Confluence Administrators under Apps > Manage Apps.

Webhook Data

The webhook provides details of the page, space, user and signature state of the page. Atlassian Automation can access any or all of these fields using the {{ field }} syntax.

Tip: To see all fields for testing, set up an email action (to self) that includes the following expansion syntax in the body. Note that Jira and Confluence Automation have different syntax for accessing webhook data.

Confluence Automation

Event {{ webhook.body.eventType }} received by Confluence automation rule.

This email contains all webhook data: {{ webhook.body }}

Jira Automation

Event {{ webhookData.eventType }} received by Jira automation rule.

All webhook data: {{ webhookData}}.

Webhook Data Fields

Notes