Skip to content

Latest commit

 

History

History
38 lines (25 loc) · 2.63 KB

README.md

File metadata and controls

38 lines (25 loc) · 2.63 KB

DocuSign Custom UI App

A sample app showcasing DocuSign integration using Pipedrive Custom UI. You can follow the Codelabs guide for this app to get started.

Custom UI Panel

DocuSign Custom UI Panel

Custom UI Modal

Custom UI Modal

Custom UI App Settings

DocuSign Custom UI App Settings

Steps to run the app:

  • Create a DocuSign developer account and Pipedrive Sandbox Account with Marketplace Manager enabled.
  • Create a new app in Pipedrive with Basic scope and Deals (read-only) scope.
  • Rename .env.example to .env. Fill in the .env file with CLIENT_ID and CLIENT_SECRET details of the newly created app.
  • Make sure you name the Custom UI modal as Template Editor. The same will be used in the panel.js file to invoke the modal (action_id param).
  • Install ngrok using npm i ngrok -g. Once installed, run the following command to make the app reachable over the internet - ngrok http 3000.
  • Copy the ngrok domain and add it to the APP_DOMAIN environment variable in .env file.
  • Run the app by using npm start command. In the console you will notice the callback, Custom UI modal, settings and panel URL. Open the created app in Marketplace Manager and add them in the respective places.
  • To install the app in your account, click on the Preview link near the app name shown in the Marketplace manager.
  • Fill in the app settings page after the authorization in the Custom UI App settings page.
  • In your DocuSign demo account, create templates for usage. This will appear in the Deal Details section.
  • Click on the Preview button to preview and edit the template from within Pipedrive.
  • You can also Send the document to the deal contact if a valid email is provided.

For advanced troubleshooting, you can start the app using the following command - DEBUG=app* npm start

⚠️ Disclaimer

This repository contains non-production code.
Sensitive information, such as tokens or credentials, should always be securely encrypted and stored according to best practices. Do not use hardcoded or plaintext tokens in production.