Integrating ServiceNow with DocuSign
Our goal is to push data elements from ServiceNow to a DocuSign template that will produce a properly formatted NDA, send it out for signature and then attach the signed document to the vendor record at the end of the process. Make sense? Let me show you how you would build this with each of the integration options.
Option 1: Build your integration from scratch
Building this from scratch will look something like this:
What you will build/configure:
| Component | Description | Notes |
| Business Rule or UI Action | To call your script to create the envelope | Just a few lines of code that call the JavaScript function below |
| “Send envelope” JavaScript function | Calling the DocuSign REST API using either sn_ws.RESTMessageV2() or the “Outbound REST message” capability | Maybe 100 lines of JavaScript if you write it well and include some comments ? |
| DocuSign NDA template | A DocuSign template with boilerplate NDA language and DocuSign fields for vendor specific information | These are easy to create using the DocuSign web application |
| DocuSign Connect | Configure DocuSign Connect to call your ServiceNow instance for events on your envelopes | Quickly configured in the DocuSign web application. You will provide a ServiceNow service account with basic authentication to give DocuSign access to your instance |
| “Receive updates” JavaScript function | A function that will be called for each update received from DocuSign culminating with the receipt of the signed document which will be attached to the ServiceNow record | Maybe another 100 lines of JavaScript code |
The short version
This is probably less than a week’s worth of work to build assuming you already know the DocuSign API and are familiar with ServiceNow scripting and other elements.
Option 2: DocuSign Spoke
Using ServiceNow’s IntegrationHub DocuSign Spoke, you will build a process that looks something like this:
What you will build/configure:
| Component | Description | Notes |
| DocuSign Spoke | Install and configure the spoke including the connection to DocuSign | This takes a few hours but it’s well documented |
| Business Rule or UI Action | To call your flow to create the envelope | Just a few lines of script – very simple |
| Envelope creation Flow Designer Subflow | DocuSign Spoke actions to create the envelope, map the data fields and download the signed document when the signing is complete | About 20 flow steps |
| DocuSign NDA template | A DocuSign template with boilerplate NDA language and DocuSign fields for vendor specific information | These are easy to create using the DocuSign web application |
The short version
This is a few hour’s work if you are familiar with DocuSign Spoke and already have it installed and configured. The DocuSign Spoke actions allow you to avoid learning the DocuSign API for all common features (and a few uncommon features too).
Option 3: eSignifi
Use eSignifi, your process will look something like this:
What you will build/configure:
| Component | Description | Notes |
| eSignifi | Install and configure the eSignifi including the connection to DocuSign | This takes a couple hours with your team guiding you through every step |
| Business Rule or UI Action | To call your flow to create the envelope | This will be automatically generated by eSignifi |
| eSignifi NDA Map | The map defines the data flow between ServiceNow and DocuSign without the need for any scripting | 1 map – maybe 25 mouse clicks to create |
| DocuSign NDA template | A DocuSign template with boilerplate NDA language and DocuSign fields for vendor specific information | These are easy to create using the DocuSign web application |
The short version
This takes minutes if you already have eSignifi installed. eSignifi maps provide a 100% declarative connection between ServiceNow and DocuSign.
Ok, great so how do I decide?
My general advice is:
- Avoid the “build from scratch” option. We have worked with several clients who took this approach and though it works, extending and maintaining it requires time and may be difficult.
- If you own Integration Hub at the enterprise level, use DocuSign Spoke period. There just are no good reasons to take another approach for DocuSign integration if you’ve made a commitment to using IntegrationHub as your general integration approach. Being consistent means that your tech folks learn a common set of tools that apply across many integrations.
- If you don’t own IntegrationHub and it doesn’t look like the right option for your organization, choose eSignifi. It’s very easy and super-fast to get deployed.
How General Networks can help (a blatant plug ?)
No matter which option you choose, we are here to help! We have deep experience with all 3 options. Here is a summary of how we can help:
| DocuSign Spoke | eSignifi | Build from Scratch |
| We offer an API launch package where we’ll guide your technical team through the process of installing, configuring and building your first use case. | Free with your first-year subscription is our QuickStart package where we assist getting you live in production in as little as 2 weeks. | We can assist your developers on training and planning resources along with technical advice on an ad-hoc basis. |
