Generate and Conga Sign documents

High Volume Document Generation can be integrated with Conga Sign to send out documents for signature.

Prerequisites

A valid and active Conga Advantage Platform organization.
A valid and active Conga Sign for Advantage Platform
ClientID and Secret generated and implemented. See Authorizing High Volume Document Generation.

Use Case

In this use case, we use an HMTL template to merge with data from JSON data, convert it to PDF format, and then email it via Conga Sign for Conga Advantage Platform.

Step 1: Create an HTML Template

Create an email template on using the HTML Editor. Once done, copy the template's file ID. For more information on how to create a template and get the File ID, see the following topics:

Step 2: Connect to Conga Sign

In order to send off transactions through Conga Sign, you must configure Conga Sign for Platform for your platform environment. Refer to the following topic:

Setting Up Conga Sign

Step 3: Create the Merge Request

Create a merge request to generate the document. The merge request contains several parameters that determine which features are included in the generated document. An example of the parameters as they appear in JSON is as follows:{ "dataFileId": "3fa85f64-5717-4562-b3fc-2c963f66afa6", "templateIds": [ "3fa85f64-5717-4562-b3fc-2c963f66afa6" ], "emailTemplateId": "3fa85f64-5717-4562-b3fc-2c963f66afa6", "format": "Json", "useCongaSign": true }

Call the following High Volume Doc Gen API method to create the document:


Method	POST
Endpoint	`https://rls-dev.congacloud.io/api/highvolumemerge/v1/merge`
Request Body	{ "dataFileId": "3fa85f64-5717-4562-b3fc-2c963f66afa6", "templateIds": [ "3fa85f64-5717-4562-b3fc-2c963f66afa6" ], "emailTemplateId": "3fa85f64-5717-4562-b3fc-2c963f66afa6", "format": "Json", "useCongaSign": true }
Example JSON File data	[ { "Id": "a24c9f37-0456-4623-a2de-459b8f5e1221", "DocumentOptions": { "OutputName": "contract.pdf" }, "Data": { "CONTACT_FIRSTNAME": "Oliver", "OPPORTUNITY_NAME": "Cloud Solution Partnership", "ACCOUNT_NAME": "Acme Inc", "Conga_Doc_Link": "https://example.com/doc1", "USER_FIRSTNAME": "Daniel", "USER_NAME": "Daniel Smith", "USER_TITLE": "Senior Manager", "USER_CUSTOM_ORG_NAME": "Smith Consulting", "USER_PHONE": "555-123-4567", "USER_EMAIL": "daniel.smith@example.com", }, "ESignOptions": { "Name": "Sign Transaction created by HVM API", "Sender": { "Email": "JJameson@example.com" }, "Recipients": [ { "FirstName": "John", "LastName": "Smith", "Email": "JohnSmith@example.com", "Role": "Signer", "RoutingOrder": 1 }, { "FirstName": "Emma", "LastName": "Brown", "Email": "EmmaBrown@example.com", "Role": "Signer", "RoutingOrder": 2 }, { "FirstName": "Sophia", "LastName": "Green", "Email": "SophiaGreen@example.com" } ] } } ]

Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.