home

Composer for Salesforce

Adobe Sign ServicesAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)CPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery Agent for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTest AuthorTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for ExcelX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerRelease NotesGeneralDocs by Release
Adobe Sign ServicesAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)CPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery Agent for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTest AuthorTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for ExcelX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerRelease NotesGeneralDocs by Release

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.

Show Contents

Composer for Salesforce

Conga Composer and DocuSign for Salesforce Integration

Generate a Composer Document with DocuSign for Salesforce Package

This is one approach towards a one-click Composer/DocuSign solution. This can be created using standard Conga Composer functionality along with DocuSign for Salesforce functionality via a Salesforce Flow.
  1. Click a Composer button or Composer Lightning Web Component to launch
  2. Your Composer Solution must include an MFTS parameter with a field to update on the merge. For more information on setting this process up, refer to Using Composer to Update Fields in Salesforce.

  3. Your Composer Solution must also include parameters that save the merged document back to the Salesforce record that was updated. You can use Activity Logging parameters to do so, the following are recommended.
    1. Use SC0 to save a copy of the merged file to the Salesforce Record.
    2. Use SC1 to specify where the merged output file is saved.
  4. Create a Salesforce Flow to take the merged document from the Salesforce record. You can refer to DocuSign's documentation on this process here.
  5. This Flow is set to run anytime the Salesforce field is changed to a specified value. This value is what will be changed in the Composer solution's MFTS parameter, which then calls the DocuSign for Salesforce package directly, sending in an Envelope Template ID along with the Salesforce Record ID you want your signing transaction associated with.

  6. Envelope Templates are part of the DocuSign for Salesforce package, and are a way to setup a repeatable DocuSign e-signature process based on set parameters. In this example, the Envelope Template being used in the Flow is setup to grab the most recent document associated with the Salesforce record and send it to our customer contact listed in Salesforce.

    2. Use the ID found from your envelopes ID found in the browser URL.
    3. Example of the DocuSign Envelope:
  7. Ensure your DocuSign Envelope Template has the Attach documents from Salesforce Record setting set to True, and the Document Selection dropdown set to Latest Document.

  8. Set your Recipients and their Roles in the DocuSign envelope settings.

The process merges your document through Composer, modifies the field specified through MFTS and saves the merged document on the Salesforce record, then triggers a Salesforce Flow to send it via DocuSign for e-signature in a single connected Flow.
Administrator Guide
Salesforce
Composer

August 31, 2026