Data Merging: It's a Two-Way Street

By: Partner

One of our favorite and most recommended solutions for mail merging and document generation is Conga Composer by Conga. Today’s post by Robert Boyd, adapted with permission from Conga, explains how to utilize the power of eSignature apps to capture data from fillable forms into Salesforce.

Conga Composer is a perfect app for merging data and content from Salesforce into customized documents, presentations and reports. That said, I often describe Composer as a “one-way street” in the sense that it’s not built to capture data from outside Salesforce (like in a fillable document) and subsequently populate fields in Salesforce.

Fortunately, a few of Conga’s trusted eSignature partners handle this requirement perfectly. Integrating Conga Composer with an eSignature application has a ton of benefits, but in this post, I want to highlight two specific features of DocuSign for Salesforce and Adobe EchoSign that give you the ability to capture information from a document that’s been sent for eSignature and update fields in Salesforce.

Document tagging with DocuSign

One of the key features of DocuSign is the ability to add tags to a document that will define where a recipient will input information like their signature, initials, name, etc. However, DocuSign also offers the ability to use custom tags to capture other types of information from signers. Custom tags can be related to Salesforce, which gives you the ability to push the data from a DocuSign Envelope back into specific fields in your Salesforce environment.

Data mapping with Adobe EchoSign

Adobe EchoSign offers extremely flexible text tags that give administrators a great deal of control over what kind of information can be collected from recipients in the process of electronically signing a document. EchoSign text tags allow you to do things like set specific locations for customers to sign and initial documents, but also capture data from signers that can be pushed back into specific fields in Salesforce. In order to accomplish the latter option, EchoSign offers the Data Mappings feature. EchoSign Data Mappings are defined in Salesforce and essentially link specific text tags to defined Salesforce fields.

There are many ways to use both DocuSign custom tags and EchoSign data mappings for a variety of business purposes, but I hope this gives you an idea of what’s possible with these particular features when designing an integrated eSignature solution with Conga Composer.

For more information, check out these data sheets that highlight the features and benefits of each integration:

Conga Composer & DocuSign Data Sheet
Conga Composer & EchoSign Data Sheet

For the full post with more examples and details, visit the Conga Blog.