---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Set up triggers for the Docusign eSignature spoke

# Set up triggers for the Docusign eSignature spoke {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
Set up the trigger to generate the callback URL on your ServiceNow instance.

## Before you begin

* Request an Integration Hub subscription.
* Activate and set up the Docusign eSignature spoke.
* Role required: admin.
{#setup-ext-triggers-docusign__ul_f2z_gln_c2c}

## Enable system property for client credentials grant type {#ariaid-title2}

Create or enable the glide.oauth.inbound.client.credential.grant_type.enabled system property to use the OAuth client credentials grant type for inbound integrations from the Docusign OAuth client to ServiceNow instance.

### Before you begin

Role required: admin

### About this task

For more information about client credentials grant type, see [Client Credentials](https://www.servicenow.com/docs/access?context=client-credentials&version=australia&pubname=australia-platform-security&ft:locale=en-US).

### Procedure

1. Navigate to AllSystem PropertiesAll Properties.
2. Search for the <kbd class="ph userinput">glide.oauth.inbound.client.credential.grant_type.enabled</kbd> system property.
3. Open the record.
4. For Value, enter <kbd class="ph userinput">true</kbd>.
5. Right-click the form header and click Save.

## Create an application registry to authenticate the inbound calls {#ariaid-title3}

Create an application registry in the ServiceNow instance to authenticate the inbound calls.

### Before you begin

Role required: admin

### Procedure

1. Navigate to AllSystem OAuthApplication Registry.
2. Click New.
3. Select Create an OAuth API endpoint for external clients.
4. On the form, fill in the fields.  
   {#app-reg-inbound-docusign__table_jyr_bfl_b2c__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name to identify the application registry record. For example, <kbd class="ph userinput">Docusign External Trigger</kbd>. |
   | OAuth Application User | User role to which the OAuth token flow is mapped. Important: By default, this field is not displayed on the Application Registries form. Configure the form layout to see the field on the form. For information about configuring the form layout, see [Configuring the form layout](https://www.servicenow.com/docs/access?context=configure-form-layout&version=australia&pubname=australia-platform-administration&ft:locale=en-US). |
   [Table 1. Application Registries form]

   {#app-reg-inbound-docusign__table_jyr_bfl_b2c}
5. Right-click the form header and click Save.  
   Application registry record is created and value of Client Secret is generated.

   Copy and record the values of Client ID and Client Secret for
   later use.

## Activate the trigger definition on ServiceNow instance {#ariaid-title4}

Activate the trigger definition to generate the callback URL on your ServiceNow instance.

### Before you begin

Role required: flow_designer and connection_admin.

### About this task

Docusign uses the callback URL to securely send the payload to the ServiceNow
instance.

### Procedure

1. Navigate to AllProcess AutomationWorkflow Studio.
2. Select the Integrations tab.
3. Toggle and enable the Inbound tab.
4. Locate the Docusign eSignature Spoke card and select View Details.  
5. Select Configure.  
6. On the form, fill these values.  
   {#activate-ext-trigger-docusign__table_ykp_fkl_b2c__entry__2}

   | Field | Description |
   |-|-|
   | Required roles | Roles using which the flow will be triggered. For example, select admin. |
   | Application Registry | Select the application registry you had created to authenticate inbound calls. For example, select Docusign External Trigger. |
   [ ]

   {#activate-ext-trigger-docusign__table_ykp_fkl_b2c}

7. Click Activate.  
   The endpoint is activated and the value of URL is generated.

   Copy and record the value of URL for later use.

## Add configuration in Docusign account {#ariaid-title5}

Add a custom configuration in the Docusign account to send real‐time data updates to the ServiceNow instance.

### Before you begin

Role required: admin

### Procedure

1. Log in to the Docusign account as an admin.
2. Click Admin.
3. Navigate to IntegrationsConnect.
4. Under Configurations, click Add Configuration and select Custom.
5. On the form, fill in the values.  
   {#custom-int-docusign__table_oy2_j4l_b2c__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name to identify the custom configuration record. |
   | URL to Publish | Enter the URL that is generated when you activated the trigger definition in this format: <kbd class="ph userinput">https://&lt;ServiceNow-instance-name&gt;.service-now.com/api/sn_docusign_spoke/docusign_esignature_external_trigger</kbd>. For more information, [Activate the trigger definition on ServiceNow instance](https://www.servicenow.com/docs/jvdam0Hl_vALAveEaY0DQQ#activate-ext-trigger-docusign "Activate the trigger definition to generate the callback URL on your ServiceNow instance."). |
   | Data Format | Ensure that you select REST v2.1. |
   | Event Message Delivery Mode | Select Send Individual Messages (SIM). |
   | Trigger Events | Expand Envelope and Recipients and select these events: * Envelope Sent * Envelope Delivered * Envelope Signed/Completed * Envelope Declined * Envelope Voided * Envelope Deleted * Recipient Sent * Recipient Auto Responded * Recipient Delivered * Recipient Signed/Completed * Recipient Declined {#custom-int-docusign__ul_tnt_htl_b2c} Under Include Data, select the Recipients option. Select other options as per your requirement. |
   [ ]

   {#custom-int-docusign__table_oy2_j4l_b2c}
6. Under Integration and Security Settings, select the Include OAuth (Recommended) check box.
7. Click Add Configuration.  
   The custom configuration record is created.
8. Click Actions for the custom configuration record that you created and select Edit.  
9. Under Integration and Security Settings, click Manage OAuth.  
   The OAuth 2.0 tab is displayed.
10. Enter the values of Client ID and Client Secret.  
    These values are created when you create application registry record in ServiceNow instance. For more information, see [Create an application registry to authenticate the inbound calls](https://www.servicenow.com/docs/jvdam0Hl_vALAveEaY0DQQ#app-reg-inbound-docusign "Create an application registry in the ServiceNow instance to authenticate the inbound calls.").
11. Enter Authorization Server URL in this format: <kbd class="ph userinput">https://&lt;ServiceNow-instance-name&gt;.service-now.com/oauth_token.do</kbd>.
12. Click Save.

### What to do next

Create flows in Workflow Studio using these triggers as per your requirement. For more information, see .

*[\>]: and then