Skip to content
Docusign eSignature Spoke › Integration Hub spokes › Build integrations › Integration Hub › Workflow Data Fabric
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Set up triggers for the Docusign eSignature spoke

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.

Enable system property for client credentials grant type

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.

Procedure

  1. Navigate to All > System Properties > All Properties.

  2. Search for the glide.oauth.inbound.client.credential.grant_type.enabled system property.

  3. Open the record.

  4. For Value, enter true.

  5. Right-click the form header and click Save.

Create an application registry to authenticate the inbound calls

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

Before you begin

Role required: admin

Procedure

  1. Navigate to All > System OAuth > Application Registry.

  2. Click New.

  3. Select Create an OAuth API endpoint for external clients.

  4. On the form, fill in the fields.

FieldDescription
NameName to identify the application registry record. For example, `Docusign External Trigger`.
OAuth Application UserUser 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 .

  1. 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

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 All > Process Automation > Workflow Studio.

  2. Select the Integrations tab.

  3. Toggle and enable the Inbound tab.

  4. Locate the Docusign eSignature Spoke card and select View Details.

Image omitted: inbound-docusign.png
Locate the Docusign eSignature Spoke card.
  1. Select Configure.
Image omitted: comf-ext-trigger-docusign.png
Configure the endpoint.

  1. On the form, fill these values.

    FieldDescription
    Required rolesRoles using which the flow will be triggered. For example, select admin.
    Application RegistrySelect the application registry you had created to authenticate inbound calls. For example, select Docusign External Trigger.
Image omitted: conf-endpt-docusign.png
Activate the endpoint.

  1. Click Activate.

    The endpoint is activated and the value of URL is generated.

    Copy and record the value of URL for later use.

Image omitted: copy-url-docusign.png
Copy the URL for later use.

Add configuration in Docusign account

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 Integrations > Connect.

  4. Under Configurations, click Add Configuration and select Custom.

  5. On the form, fill in the values.

FieldDescription
NameName to identify the custom configuration record.
URL to PublishEnter the URL that is generated when you activated the trigger definition in this format: `https://.service-now.com/api/sn_docusign_spoke/docusign_esignature_external_trigger`.For more information, Activate the trigger definition on ServiceNow instance.
Data FormatEnsure that you select REST v2.1.
Event Message Delivery ModeSelect 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

Image omitted: trigger-events-docusign.png
Triggers events to be selected.</p>

Under Include Data, select the Recipients option. Select other options as per your requirement.

Image omitted: include-data.png
Select the Recipients option.</p></td></tr></tbody>

  1. Under Integration and Security Settings, select the Include OAuth (Recommended) check box.

  2. Click Add Configuration.

    The custom configuration record is created.

  3. Click Actions for the custom configuration record that you created and select Edit.

Image omitted: edit-conf-docusign.png
Edit the custom configuration.

  1. Under Integration and Security Settings, click Manage OAuth.

    The OAuth 2.0 tab is displayed.

  2. 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.

  3. Enter Authorization Server URL in this format: https://<ServiceNow-instance-name>.service-now.com/oauth_token.do.

  4. Click Save.

What to do next

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

sndocs is an independent community mirror and is not affiliated with or endorsed by ServiceNow.

ServiceNow, the ServiceNow logo, Now, and other ServiceNow marks are trademarks and/or registered trademarks of ServiceNow, Inc., in the United States and/or other countries. Other company and product names may be trademarks of the respective companies with which they are associated.

© 2026 ServiceNow, Inc. All rights reserved.

Documentation content is redistributed under the Apache License 2.0 from the ServiceNowDocs repository.