Composer Document Templates are able to add static text, images, repeating table data and more.  

Composer Document Templates cannot be stored in the Composer Web App. Templates must be stored in our supported cloud storage integration partners to merge with Composer API. 

Create a New Template

  1. Open your document on your local machine. The examples below are using Microsoft Word as the template. 

  2. Input any static text, tables, or images. 
  3. In the the Conga Platform menu, navigate to Email Templates and click Merge Field Lookup. This tool provides you with Composer merge fields to copy and past to build Word, PowerPoint and HTML templates. The merge fields are determined by your JSON data. 
  4. Click the Add JSON Data to open the JSON Text Box. Your data set that provides these fields must be imported from your own JSON File. An example JSON structure can be found here
  5. Copy and paste your JSON code into the box and click Populate Merge Data to make your list of merge fields available. 

    JSON data is only cached for as long as you are interacting with the template builder. No company data is stored in the Merge Field Lookup interface. 

  6. Use the two Radials to choose between displaying your merge fields as text only, or as their merge field syntax. Text only removes the merge field syntax to help you identify fields easier. 
  7. Use the Merge Field Types dropdown menu to choose between Single Merge Fields or Table Data. Use the search bar to find a specific merge field or value. Click the "" to copy the field and paste it into the template.

  8. Merge fields syntax between single merge fields and table merge fields are indicated by their JSON key. Every JSON merge field, whether singular or table data, must be wrapped within the TableStart:MAIN and TableEnd:MAIN JSON data tags. The Main table (TableStart/TableEnd) will contain everything passed into the jsonData tag, and arrays included inside the jsonData tag will be kept in a new table (TableStart/TableEnd) named after the key used in the JSON. In this example, PRODUCTS is the JSON key. 
  9. Once you have completed adding your merge fields, Save the document to your local machine.
  10. Determine your Document Delivery Integration preference. See Configuring Composer Platform Integrations for more details