DocuSign Integration for Rev.io

he Rev.io DocuSign integration is designed to support the synchronization of the two platforms to ease the digital transaction process. 

The platform allows users to send, sign, and manage legally binding documents securely in the cloud. The integration leverages our integration cloud platform.

To enable this integration, please contact Client Success.

Customizations 

The table below lists all the potential variables created in both platforms. This integration leverages no custom variables within DocuSign itself. Note that not all clients will require all variables to meet their business requirements.

Item	Description
DocuSign
None
Rev.io
Contact Type	The new Contact Type DocuSign Approver identifies the contact that will flow to DocuSign (Email, Name etc.)
Request Status	The Send DocuSign status functions like a signal in Rev.io to send data to DocuSign.
Request Status	The Pending DocuSign status indicates Rev.io is awaiting customer authorization or signature data from DocuSign.

Supported Workflows 

 

Rev.io to DocuSign

New customer/company synchronization flows from Rev.io to DocuSign whenever Quotes are created for customers. An eSignature process is automatically triggered with the generation of a Rev.io Quote. 

Specific client implementations will differ depending on the integration type purchased and business processes identified during onboarding. Use cases supported include: 

Use Case	Action
Rev.io to DocuSign
1. A new company is saved, and a request is created with Request Status set to "Send Docusign"	A new request is created in Rev.io.
2. A new contact or existing contact is updated with email address and other relevant details. The contact type must be in “DocuSign Approver” status after saving.	A new contact is created in Rev.io.
DocuSign
The authentication for DocuSign the account is complete. A notification will be sent to contact email address for the approval requests.  .	Configuration in DocuSign must be set with Signatures
Rev.io
When the notification is received by Rev.io, the respective Request will be updated to “Pending DocuSign”	Update the Request Status. Note: Status must not be manually changed in Rev.io, as the DocuSign integration does it automatically

The steps below illustrate how the Rev.io to DocuSign Sync is performed. Create and save a new request in Rev.io. Then, create a new contact for the customer with all the details:
 

Update contact details are with the Contact Type set to "DocuSign Approver". 

The basic setup In DocuSign must be completed by the customer. 

A DocuSign Notification will be received by the customer. Upon reviewing the document, it will ask for the necessary signature to confirm the document.

Once the notification is sent to Rev.io for reviewing by the candidate, the status will automatically be changed in Rev.io to “Pending DocuSign”. 

DocuSign to Rev.io

File synchronization can flow from DocuSign to Rev.io at the time a candidate signs or approves a document. 

Specific client implementations will vary depending on the integration type purchased and business processes addressed during onboarding. Use cases supported include: 

Use Case	Action
DocuSign
1.The User/Customer will submit the document in DocuSign.  2. DocuSign checks whether or not submission is completed.  3. All relevant signed attachments are transferred to Rev.io from DocuSign.	Once the request type status to “Send DocuSign” Process only once the candidate submits. Note: It process only Rev specific Quote PDF only

The steps below illustrate how DocuSign syncs with Rev.io. Once a notification is sent to DocuSign from Rev.io, a candidate can review the document and sign or approve it. Every 5 minutes, a process will run and check DocuSign for any approvals that are completed. Upon detection of completed of documents, it captures all the relevant documents and flows it back to Rev.io for that specific customer.

Data Mapping 

There are no fields mapped between Rev.io and DocuSign.