&QMode=Attachments

Attaches the merged output files to the Master Object records

&QMode=Download

This parameter value is available only to Conga Batch. There is no download option available in Conga Trigger.

Recommended: &ContentWorkspaceId=[Workspace ID] to specify the Content Workspace (Library) where Conga Batch will store the merged output file if the Conga Batch solution is configured to run on a schedule. Without this parameter, the merged output file from a scheduled Conga Batch solution configured to download will be stored in the running user’s personal Salesforce Content Workspace (Library).

If either the &DefaultPDF=1 or &FP0=1 parameter is not included in the Conga Batch formula field, the merged output files will be consolidated into a .zip file. However, if one of these PDF output parameters is included in the formula field, the merged output file will be a consolidated PDF.

&QMode=SendEmail

Requires:

&TemplateID unless using only a Conga Email Template (&CongaEmailTemplateID) and no document template.

&EmailTemplateId=[Saleforce Email Template ID] or &CongaEmailTemplateID=[Conga Email Template ID]

&EmailToId=[Salesforce Contact ID] or &ContactId=[Salesforce Contact Id]

If you cannot use the &EmailToId or &ContactId parameters to specify an email recipient by their Contact Id, you can instead specify &EmailAdditionalTo=[email address] and &EmailSubject=[subject text].

&QMode=Chatter

By default, Conga Trigger posts files to the Master Object record feed. To override this behavior and post a file to another record’s feed, a Chatter Group or a specific User’s feed, use &AttachmentParentID.

&QMode=Content

Recommended: &ContentWorkspaceId=[Salesforce Content Workspace ID] to specify an alternate Content Workspace (Library).

Does not permit saving additional attachments outside of the initial document created in your Content Workspace (for example, cannot save a copy to Attachments or Chatter in addition to your Content Workspace).

Use this method if you are scheduling a content deliver.

&QMode=Documents

Requires: &DocFolderId=[Salesforce Documents Folder ID]

Does not permit saving additional attachments outside of the initial document created in your Document folder (i.e. cannot save a copy to Attachments or Chatter in addition to your Document folder).

&QMode=DocuSign

• &DocuSignEndPoint= [See DocuSignEndpoint for relevant values]
• &DocuSignR1ID=[Salesforce Contact, Lead, or User ID]
• &DocuSignR1Role= [See DocuSignR1Role for relevant values]
• &DocuSignR1Type= [See DocuSignR1Type for relevant values]
• DocuSign Credentials on the USER record
• The user's email address on their User record in Salesforce must match the user's email address in DocuSign.

There are many combinations of possible DocuSign parameters. Please see DocuSign Integration Parameters for more information.

&QMode=EchoSign

Sends the merged output files via Adobe eSign (one Adobe eSign Agreement per Master Object record). For more information, see Adobe eSign Integration Parameters.

&QMode=EchoSignCreate

Merges the output files and attaches each to an Adobe eSign Agreement but does not automatically send those Agreements.

&QMode=GoogleDrive

Requires the Google Refresh Token on Conga Batch Setup tab.

Use &OFP to specify in which folder the merged output files are to be saved.

Remove &SC0=1 and &SC1=Google from the Conga Batch formula field to prevent the storage of duplicate copies of the merged output file in Google Drive.

&QMode=GoogleDocs

Requires Google Refresh Token on Conga Trigger Setup tab.

Recommended: &OFP to specify in which folder the merged output files are to be saved.

&QMode=SalesforceFile

The &SC0=1 and &SC1=SalesforceFile parameters are required in the URL for this QMode.

&QMode=Sertifi

Sends the merged output files via Sertifi. The browser page refreshes and lands on the Sertifi EContract. There are many combinations of possible Sertifi parameters. For more information, see Sertifi Integration Parameters.

&QMode=SpringCM

Saves the merged output files in a SpringCM folder, as defined by the SpringCM configuration rules.

&QMode=Box

Sends the output documents to Box.

&QMode=OneDrive

Sends the output documents to the user's OneDrive repository.

&QMode=CongaSign

Sends the output documents to Conga Sign for Salesforce.

&QMode=Contracts

Sends the output documents for negotiation using Conga Contracts for Salesforce's Send for Negotiation email service.

&QMode=AmazonS3

Sends the output documents to AmazonS3

&QMode=EmailLink

Allows you to send the composer-generated link via a unique URL in a Conga Email Template with Trigger or Batch.

Requires:

• Composer File Storage enabled in Composer Setup.
• &CongaEmailTemplateID to designate a specific Conga Email Template
• The {Conga_Doc_Link} merge tag to successfully generate the document link in the email.
• &TemplateID unless using only a Conga Email Template and no document template.
• &EmailToId=[Salesforce Contact ID] or &ContactId=[Salesforce Contact Id]

&QMode=GenerateLink

Allows you to generate a unique URL for the Composer generated document and adds that link to the document history record. For more details, refer to Document History and Document History Detail Objects.

1

(One of the following parameters should be used with QMode=1: LG3=1 OR LG4=1.) (default)

2

LG4=1 is the only Activity Logging parameter needed when using QMode=2.

Analogous to Qmode=Attachments

3

Requires &TemplateId

For an Opportunity with a Primary Contact (Contact Roles), there is no need to set the &EmailToId. Also, if you use &EmailTemplateId, you must specify the &EmailToId.

4

Delivers the output via Adobe eSign. Requires Adobe eSign parameters.

5

QMode=5 saves the output to the specified location only. You cannot attach the document to other locations such as Chatter or Notes and Attachments.

6

QMode=6 saves the output to the specified location only. You cannot attach the document to other locations such as Chatter or Notes and Attachments.

7

Delivers the output via DocuSign. Requires DocuSign parameters.

94

Creates an Adobe eSign Agreement but does not automatically deliver it. Requires Adobe eSign parameters.