Load DocuSign Data to a Database Using Embulk

Embulk is an open source bulk data loader. When paired with the CData JDBC Driver for DocuSign, Embulk easily loads data from DocuSign to any supported destination. In this article, we explain how to use the CData JDBC Driver for DocuSign in Embulk to load DocuSign data to a MySQL dtabase.

With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live DocuSign data. When you issue complex SQL queries to DocuSign, the driver pushes supported SQL operations, like filters and aggregations, directly to DocuSign and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations).

Configure a JDBC Connection to DocuSign Data

Before creating a bulk load job in Embulk, note the installation location for the JAR file for the JDBC Driver (typically C:\Program Files\CData\CData JDBC Driver for DocuSign\lib).

Embulk supports JDBC connectivity, so you can easily connect to DocuSign and execute SQL queries. Before creating a bulk load job, create a JDBC URL for authenticating with DocuSign.

To connect to DocuSign, set the following connection properties:

• UseSandbox: indicates whether current user account is sandbox or not (FALSE by default)
• AccountId (optional): set it in the connection string if you have access to multiple Account Ids

Authenticating to DocuSign

DocuSign uses the OAuth authentication standard. To authenticate using OAuth, create an app to obtain the OAuthClientId, OAuthClientSecret, and CallbackURL connection properties. See the Help documentation more information.

Built-in Connection String Designer

For assistance in constructing the JDBC URL, use the connection string designer built into the DocuSign JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

java -jar cdata.jdbc.docusign.jar

Fill in the connection properties and copy the connection string to the clipboard.

👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)

Below is a typical JDBC connection string for DocuSign:

jdbc:docusign:OAuthClientId=MyClientId; OAuthClientSecret=MyClientSecret; 
CallbackURL=http://localhost:33333;

Load DocuSign Data in Embulk

After installing the CData JDBC Driver and creating a JDBC connection string, install the required Embulk plugins.

Install Embulk Input & Output Plugins

1. Install the JDBC Input Plugin in Embulk.
   https://github.com/embulk/embulk-input-jdbc/tree/master/embulk-input-jdbc

embulk gem install embulk-input-jdbc

2. In this article, we use MySQL as the destination database. You can also choose SQL Server, PostgreSQL, or Google BigQuery as the destination using the output Plugins.
   https://github.com/embulk/embulk-output-jdbc/tree/master/embulk-output-mysql

   embulk gem install embulk-output-mysql
   

With the input and output plugins installed, we are ready to load DocuSign data into MySQL using Embulk.

Create a Job to Load DocuSign Data

Start by creating a config file in Embulk, using a name like docusign-mysql.yml.

1. For the input plugin options, use the CData JDBC Driver for DocuSign, including the path to the driver JAR file, the driver class (e.g. cdata.jdbc.docusign.DocuSignDriver), and the JDBC URL from above
2. For the output plugin options, use the values and credentials for the MySQL database

Sample Config File (docusign-mysql.yml)

in:
	type: jdbc
	driver_path: C:\Program Files\CData[product_name] 20xx\lib\cdata.jdbc.docusign.jar
	driver_class: cdata.jdbc.docusign.DocuSignDriver
	url: jdbc:docusign:OAuthClientId=MyClientId; OAuthClientSecret=MyClientSecret; 
CallbackURL=http://localhost:33333;

	table: "Documents"
out: 
	type: mysql
	host: localhost
	database: DatabaseName
	user: UserId
	password: UserPassword
	table: "Documents"
	mode: insert

After creating the file, run the Embulk job.

embulk run docusign-mysql.yml

After running the the Embulk job, find the Salesforce data in the MySQL table.

Load Filtered DocuSign Data

In addition to loading data directly from a table, you can use a custom SQL query to have more granular control of the data loaded. You can also perform increment loads by setting a last updated column in a SQL WHERE clause in the query field.

in:
	type: jdbc
	driver_path: C:\Program Files\CData[product_name] 20xx\lib\cdata.jdbc.docusign.jar
	driver_class: cdata.jdbc.docusign.DocuSignDriver
	url: jdbc:docusign:OAuthClientId=MyClientId; OAuthClientSecret=MyClientSecret; 
CallbackURL=http://localhost:33333;

	query: "SELECT DocumentId, DocumentName FROM Documents WHERE [RecordId] = 1"
out: 
	type: mysql
	host: localhost
	database: DatabaseName
	user: UserId
	password: UserPassword
	table: "Documents"
	mode: insert

More Information & Free Trial

By using CData JDBC Driver for DocuSign as a connector, Embulk can integrate DocuSign data into your data load jobs. And with drivers for more than 200+ other enterprise sources, you can integrate any enterprise SaaS, big data, or NoSQL source as well. Download a 30-day free trial and get started today.