The following process allows Conga Mix users to integrate with DocuSign.

Create a Consumer key and Consumer Secret in DocuSign

  1. In DocuSign eSignature Settings, select Apps and Keys
  2. Select ADD APP AND INTEGRATION KEY
  3. Enter a name for your app, and select CREATE APP
  4. Select ADD SECRET KEY 

    For more information, see Add Integration Keys on the DocuSign support site. 

  5. After Integration key is created on a developer account, the integration key needs to go live on a Production environment too. 

    For more information, see the DocuSign Go-Live documentation. 

  6. Once the above step is completed, the integration key is now live on Production and secret key needs to be created for Production.

Once all steps are complete, you will have a Developer and Production account integration key. Create an Authentication Provider to Connect to DocuSign

  1. In your Salesforce Org, from Setup, enter Auth Providers in the Quick Find box, then select Providers.
  2. Click New, and select Open ID Connect as the Provider Type.
  3. Name the Auth Provider DocuSign Auth Provider and enter "DocuSign_Auth_Provider" in the URL Suffix field.
  4. In the Consumer Key field, enter your DocuSign App's Integration Key.
  5. For Consumer Secret, enter your DocuSign App's Secret Key.
  6. For Authorize Endpoint URL, enter https://account-d.docusign.com/oauth/auth for UAT and enter https://account.docusign.com/oauth/auth for Production
  7. For Token Endpoint URL, enter https://account-d.docusign.com/oauth/token for UAT and enter https://account.docusign.com/oauth/token for Production
  8. For Default Scopes, enter refresh_token full.
  9. Ensure that the Send access token in header is selected.
  10. Ensure that Include Consumer Secret in API Responses is selected.
  11. Click Save. This saves your Auth provider and generates Salesforce Configuration URLs.
  12. Copy the Callback URL.
  13. Log into your DocuSign developer account.
  14. From your DocuSign account, in the App and Keys section, click Edit for your app.
  15. Paste the Callback URL in the Redirect URIs
  16. Click Save.

OAuth 2.0 Named Credential to Connect to DocuSign (Named Credential 1)

  1. In your Salesforce Org, from Setup, enter Named in the Quick Find box, then select Named Credentials.
  2. In the New dropdown list, select New Legacy.
  3. For Label and Name, enter Mix Named Credentials.
  4. For URL, enter https://account-d.docusign.com for UAT or https://account.docusign.com for Production.
  5. For Identity Type, select Named Principal.
  6. For Authentication Protocol, select OAuth 2.0.
  7. For Authentication Provider, select DocuSign Auth Provider.
  8. Ensure that Start Authentication Flow on Save is selected.
  9. Ensure that Generate Authorization Header is selected.
  10. Click Save.

The DocuSign login window appears. From the DocuSign login window, log in to DocuSign either Developer or Production according to URL provided in Step4. This changes the Named Credential's Authentication Status to Authenticated.

OAuth 2.0 Named Credential to Connect to DocuSign (Named Credential 2)

  1. In your Salesforce org, from Setup, enter Named in the Quick Find box, then select Named Credentials.
  2. In the New dropdown list, select New Legacy.
  3. For Label and Name, enter Mix Named Credentials API.
  4. For URL, enter https://demo.docusign.net for UAT or https://{server}.docusign.net for Production. Here server name you can find on your DocuSign account by following this step Go to Settings > Apps and Keys. In the top right of the screen, you should see the BaseURI which contains the site.
  5. For Identity Type, select Named Principal.
  6. For Authentication Protocol, select OAuth 2.0.
  7. For Authentication Provider, select DocuSign Auth Provider.
  8. Ensure that Start Authentication Flow on Save is selected.
  9. Ensure that Generate Authorization Header is selected.
  10. Click Save.
  11. The DocuSign login window appears. From the DocuSign login window, log in to DocuSign either Developer or Production according to URL provided in Step4. This changes the Named Credential's Authentication Status to Authenticated.

Quik Integration 

  1. Congawill reach out to you to request your Admin user information for new Quik! App account.
  2. Conga will add your Admin users to the your Quik! App.
  3. The new users will receive their Quik! App credentials once the admin user is created in customers' Quik! App.
  4. Users will now be able to use their Quik! App credentials to set up their DocuSign connection.
  5. Add the connection by following the DocuSign - How to Connect to an Admin Account documentation on the Quik support site. Once connection is added, you must remember the connection Name in Mix UI.  Instead of adding the DocuSign username and password you need to add DocuSign username and connection name you have created in Quik as shown in below screenshot.
  6. You need to get a token to use E-Sign. The token value is not displayed on Mix screen. If you created your token in Quik, click the Get Token button. Token retrieved successfully displays on screen to confirm the token was created and saved successfully.