Partner Integrations: DocuSign

The Velocify/Docusign integration allows data from a Velocify lead to be 'pushed' directly to a DocuSign PowerForm via an HTTP Post. This means that a document (like an application, legal agreement or contract) is sent to a lead from DocuSign but is triggered within Velocify and is already filled out with key customer information.


A Velocify user triggers the DocuSign PowerForm - which is emailed to a lead for e-signature via DocuSign -  by taking an action in Velocify. The user never needs to log in to DocuSign.


Management of the document PowerForms, including control of authentications, approvals, and routing order is handled by and defined in DocuSign as part of the standard PowerForm setup process.



What is Required for a DocuSign Integration?

Both DocuSign and Velocify as individual services have their own independent requirements. They also have independent setup steps, as well as required account configurations that are specific to this integration. 



  • DocuSign account with PowerForms enabled
  • Additional account features, training requirements, support levels, and fees as outlined by DocuSign. Please work with DocuSign for details.

Any questions or support regarding enabling PowerForm functionality, creating templates or using other DocuSign features must be directed to DocuSign.



  • Velocify LeadManager Advanced Edition account with the Manage Posts page (also referred to as XML Poster) enabled. 
  • Additional account features, training requirements, support levels, and fees may be required as well. Please work with your Velocify Account Manager for details. 


DocuSign Setup Overview

This overview assumes a certain level of foundation knowledge of the DocuSign system. Please work directly with DocuSign regarding any questions you may have about the DocuSign application.


1. Create a PowerForm


If you haven't done so already, you will need to create a PowerForm in DocuSign from your document (contract, agreement, application, etc.). This should be fully setup and tested. The DocuSign team can provide support on this step, if needed.

2. Edit PowerForm Field Tags


Edit the Field Tag Properties for each DocuSign field that should be pre-populated with Velocify lead data. Place the appropriate Velocify field name in the the Label box. When doing so, it is best practice to use Velocify field names without special characters or spaces as the naming convention.



Example 1: If the DocuSign field should be populated with data from the Velocify field called ‘Last Name’, then use ‘LastName’ for the Label.


Example 2: If the DocuSign field should be populated with data from the Velocify field called ‘Borrower’s Account #’, then use ‘BorrowersAccount’ for the Label.



3. Check PowerForm Settings


  • In the PowerForm Summary section, the Signing Mode should be Email
  • In the Recipients section, note the Role or Name  


4. Get the PowerForm Posting URL


Each PowerForm has a unique posting URL (link). You will need this posting URL when setting up the Velocify Post.




Velocify Setup Overview

An HTTP post from Velocify 'pushes' lead data directly to the DocuSign PowerForm and triggers the sending of the DocuSign envelope email ('envelope' is the term DocuSign uses to describe a container used to send one or more documents for signature).


A basic understanding of the following is strongly recommended for this step:


  • Writing and troubleshooting HTTP posts
  • Adding Actions
  • Creating, triggering and testing Velocify posts (Manage Posts)


1. Write HTTP Post Body


The key-value pairs in the post follow this format:


docusign label = velocify field tag


For example: firstname={First Name}&lastname={First Name}&email1={Email Address}


The post must contain the following elements: 


The name that appears on the DocuSign envelope/email (i.e. the lead's name) is determined by this:


XX_username={First Name} {Last Name}


where XX is the DocuSign ROLE name (for example, this may be something like 'signer' or 'client') - and {First Name} {Last Name} are the Velocify field tags that are associated with the name of the lead.


For example: signer_username={Borrower Full Name}


The email(s) that the DocuSign envelope will be sent to is determined by this:




where XX is the DocuSign role name (for example, this may be something like 'signer', 'agent', or 'cosigner') - and {email} is the Velocify field tag that are associated with the appropriate email address.


For example: signer_email={Borrower Email Address}&agent_email={User.Email}


*Routing order and type are defined in DocuSign


Also include:




Example Post:


Customer_UserName={Borrower First Name} {Borrower Last Name}&CSR_UserName={User.Name.First} {User.Name.Last}&Customer_Email={Email}&CSR_Email={User.Email}&Email={Email}&BorrowerFirstName={Borrower First Name}&BorrowerLastName={Borrower Last Name}&BorrowerMiddleInitial={Borrower Middle Initial}&Address={Address}&City={City}&State={State}&Country={Country}&HomePhone={Home Phone}&WorkPhone={Work Phone}&MobilePhone={Mobile Phone}&Address2={Address 2}&Comments={Comments}&ZipPostalCode={Zip/Postal Code}&activateonly=1&submit=Send


Also see DocuSign's support article on this topic.


2. Create the Velocify Post


New posts are added on the Manage Posts page. Click Add New Post to access the Compose Post form.



Title: Title your post so it is easy to identify what the post does. Typically, the post is the name of the DocuSign PowerForm that it is linked to. 

URL: Copy/paste the DocuSign posting URL here.

Type: Select URL-encoded Post.

Header: Leave blank.

Success Regex Response: Leave blank.

Update Lead From: Select Nothing.

Body: Insert the HTTP post here.


Click Submit to save the post.


3. Set Post Trigger


The use of an Action as the post trigger is the most common and best practice. Details on adding actions and associating posts with action an is here

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk