Conga for Salesforce: Composer, CLM, CPQ and Sign Explained
Conga turns Salesforce data into quotes, contracts, invoices and signed agreements without copy and paste. This guide explains what each Conga product does in 2026, how Conga Composer actually works, how to automate it, and how to choose the right Conga product (or none at all) for your process.
Key Takeaways
- Conga is a separate software company, not part of Salesforce. Its Salesforce products install as managed packages from the AppExchange and work on your Salesforce data.
- Conga Composer is the document generation engine: one button on a record merges Salesforce data into Word, Excel, PowerPoint, PDF or HTML email templates.
- Conga CLM manages the full contract lifecycle, Conga CPQ handles configure-price-quote, and Conga Sign handles eSignature. Composer and Sign together are what Conga now calls Document Automation.
- Conga Batch and Conga Trigger (which works with Salesforce Flow) make documents run in bulk or on their own, with no button click.
- Older guides list products that are gone or renamed, such as Conga Courier, Mail Merge and Composer 7. Check Conga's retirement schedule before you plan around a legacy name.
Conga for Salesforce is a family of applications that turn the data already in your Salesforce org into documents, contracts, quotes and signed agreements. Instead of exporting a record, retyping it into Word, attaching a PDF to an email and chasing a signature, a user clicks one button, or a Flow does it for them.
This guide is for sales operations, legal operations, finance and Salesforce admin leaders at growing and mid-market companies that run on Salesforce. It replaces our earlier overview of Conga with what has changed since: the current product lineup, the products that have been retired, how Composer works under the hood, and a practical way to decide which Conga product your process actually needs.
What Is Conga for Salesforce Used For?
Conga automates the paperwork around revenue: proposals, quotes, contracts, invoices, statements and the signatures that close them. It reads standard and custom Salesforce objects, merges them into branded templates, and sends, stores or routes the result for signature. Conga sells separate products for document generation, contract management, quoting and eSignature, so most companies start with one.

| Conga product | What it does | Start here when |
|---|---|---|
| Conga Composer | Generates documents and reports from Salesforce data | People copy CRM data into Word or Excel to make quotes, letters, invoices or statements |
| Conga Sign | eSignature built for Salesforce, from any object | Signed documents need to land back on the Salesforce record automatically |
| Conga CLM | Contract lifecycle management: request, drafting, redlining, approval, signature, renewal | Legal negotiates contracts and needs clause control, versions and an audit trail |
| Conga CPQ | Configure-price-quote: bundles, constraint rules, price lists, discounts, renewals | Reps build complex quotes and pricing errors cost real money |
| Orchestrate, Grid, X-Author | Process orchestration, spreadsheet-style record editing, Excel authoring | You already use Conga and need to streamline the processes around it |
One point confuses many buyers: Conga is not part of Salesforce. It is an independent vendor whose products for Salesforce are installed from the AppExchange as managed packages, licensed separately from your Salesforce subscription. Conga also offers integrations beyond Salesforce, but Salesforce remains its deepest one.
What Is in Conga's Product Lineup in 2026?
Conga now groups its products into four families: Document Automation, Contract Lifecycle Management, Revenue and Commerce, and Price Optimization and Management. They run on what Conga calls the Conga Advantage Platform, with an AI layer named AiMe. Several product names from older articles have been retired, so check the lineup before you plan around one.
How the company got here
- 2020: Apttus, known for CPQ and contract management, and Conga, known for document generation, combined under the Conga name. That is why CPQ and CLM sit alongside Composer today.
- February 2026: Conga completed its acquisition of the B2B business of PROS, adding AI-driven pricing. That work is now sold as Conga Price Optimization and Management, and Conga says Composer can populate templates with account-specific pricing from it.
- October 2026: Conga launched the Conga MCP Server, which connects AI assistants to the Conga platform, and expanded AiMe with contract redlining, search and compliance screening for CLM, plus an AI template generator for Composer.
Which Conga product names are current, and which are retired?
| Name you may see | Status in 2026 | What to do |
|---|---|---|
| Conga Composer | Current | The document generation product; release 8.7 and later include Solution Manager |
| Conga Sign | Current | Paired with Composer as Document Automation |
| Conga CLM | Current | The contract lifecycle product for Salesforce |
| Conga CPQ (marketed as Advantage CPQ) | Current | The quoting product |
| Conga Orchestrate, Conga Grid | Current | Still documented and marketed as Salesforce automation tools |
| Conga Collaborate | De-emphasized | Still documented, but its product page now leads to Document Automation (Composer and Sign) |
| Conga Contracts | End of sale Nov 2025 | Listed on Conga's retirement schedule; plan new contract work on Conga CLM |
| Conga Courier, Mail Merge, Composer 7, Quick Merge | Retired | End of life between 2021 and 2022; replace with current Composer, Batch and Trigger |
Source: Conga's product retirement schedule, the Document Automation page and the Conga for Salesforce page. Conga Mobile, listed in our earlier post, no longer appears in Conga's product documentation, so we have left it out.
How Does Conga Composer Work in Salesforce?
An admin builds a "Composer Solution": a button on a Salesforce record that knows which templates to use, which data to pull and where to send the result. A user clicks it, or automation runs it in the background, and Composer merges data from that record and its related records into a finished document, then delivers it.
Per Conga's Composer documentation, every solution has the same five parts:
The record the button lives on
An Opportunity, Account, Quote, Case, Contract or any custom object, such as a Matter or an Invoice. Its fields are available to every template in the solution.
SOQL queries and Salesforce reports
Queries or reports, filtered by the master record's ID, pull line items, contacts, payments and other related lists. A solution can draw on as many as 50 other objects or lists.
Word, Excel, PowerPoint, PDF or HTML email
Merge fields such as {{ACCOUNT_NAME}} or Word-style <<ACCOUNT_NAME>> mark where data goes. An admin adds templates through the Conga Template Builder or the Document Automation Wizard.
Instructions on the button URL
Parameters preselect up to 10 templates, log activity, save the output, connect partner tools such as eSignature, and switch on background mode, so users never see a dialog.
Download, email, save, sign or post
Download in the browser, email it, save it to Salesforce or to Box, Google Drive or OneDrive, send it for eSignature, or post it to Chatter. Output can be one merged file or separate files.
Admins can build solutions with the Document Automation Wizard, with Composer Solution Manager (included from release 8.7, alongside ready-made Solution Packs), or by hand in Salesforce Setup. The full list of button options is in the Composer Parameter Guide. Conga's newest addition is the AiMe Template Generator, an AI skill that turns an existing Word document, or a quick-start quote, invoice or service agreement, into a template with its merge fields created for you.
How Do You Automate Conga Composer Without a Button Click?
Use Conga Trigger to run a solution when a record changes, Conga Batch to run it across many records on a schedule, and background mode so nothing waits on a user. Both Trigger and Batch are add-ons to Composer. Trigger works with Salesforce Flow, so the business rule lives where your admins already maintain automation.
| Option | How it runs | Typical use |
|---|---|---|
| Button or link | A user clicks on the record | Proposals, engagement letters, one-off quotes |
| Background mode | Preselected parameters, no dialog | One-click "generate, save and email" actions |
| Conga Trigger | Fires from Salesforce automation such as Flow | Send a credit note when its status changes; create a contract when a deal closes |
| Conga Batch | Runs a solution across a set of records, on a schedule | Monthly invoices and statements, renewal notices, account reports |
| Composer REST API | Called from Apex or another system | Generation inside custom code or an integration; access is enabled through Conga |
Composer's documentation also covers event notifications and webhooks, which let another system react once a document is ready. One caution for API work: Conga's product page describes the Composer API as included, while its developer documentation describes it as an early-adopter program. Confirm access with your Conga account team before you design around it.
Does Conga Work With DocuSign, Adobe Sign or Conga Sign?
Yes, all three. Composer can hand a generated document to Conga Sign, to DocuSign for Salesforce or to Adobe Sign. Conga Sign is the most direct route; DocuSign or Adobe Sign makes sense when your company has already standardized on one of them. In every case the signed file should come back to the Salesforce record.
Conga Sign
Built for Salesforce: sends from any object to up to 10 recipients in a signing order, tracks activity in Salesforce and uploads the signed file back. Recipients don't need a Salesforce license.
DocuSign via Flow
Conga documents a one-click pattern: Composer saves the merged file to the record and updates a field, and a Salesforce Flow sends it with a DocuSign envelope template.
Adobe Sign
The Parameter Guide includes Adobe Sign integration parameters, so a Composer button can send its output straight into an Adobe Sign agreement.
With Conga Sign, templates carry text tags such as {{esl:Signer1:Signature}} that place signature fields automatically, and the button parameters set the recipients. That removes the most error-prone manual step: dragging signature boxes onto every document.
What Are the Most Common Conga Use Cases by Team?
Any document that is assembled from CRM data, follows a standard layout and is produced more than a few times a week is a candidate. These are the most common patterns, from sales and legal to finance.
Sales: proposals and quotes
Opportunity, products and pricing merged into a branded proposal or quote, with the right terms for the region, saved to the deal and emailed in one click.
Legal: letters and agreements
Engagement letters, retainers and fee statements generated from client and matter records, or full contract negotiation in Conga CLM with clause libraries and redlines.
Finance: invoices and statements
Invoices, credit notes, remittances and account statements produced by Conga Batch on a schedule, with branding and sender details per legal entity.
Customer success: renewals
Renewal notices and renewal quotes built from the agreed terms and assets, so nothing is retyped from last year's contract.
Leadership: board and account reports
Excel or PowerPoint reports built from Salesforce reports, refreshed with live data instead of screenshots pasted into slides.
Operations: licenses and leases
Agreements generated from Salesforce, routed for signature in order, and followed by scheduled updates to the records the agreement controls.
Conga Composer vs Conga CLM vs CPQ: Which Do You Need?
Choose by the job, not by the brand: Composer for producing documents, CLM for negotiating and governing contracts, CPQ for building accurate quotes, Sign for signatures. Many companies need only Composer and Sign. Add CLM or CPQ when the process itself (negotiation or pricing) is the bottleneck, not the paperwork.
Conga fits when documents pull from many related objects, vary by region, entity or product, run in volume or on a schedule, and must be stored, sent and signed without leaving Salesforce.
Look elsewhere when you produce a handful of simple documents a month, have no Salesforce admin to own templates, or need contract or pricing logic that a dedicated CLM or CPQ evaluation should decide first.
What are the alternatives to Conga Composer?
Salesforce has its own Document Generation, which creates documents on the platform without a managed package, from Word and PowerPoint templates, with PDF conversion and batch generation. It needs a separate permission set license. On the AppExchange, Nintex DocGen, S-Docs and Formstack Documents compete with Composer. Our document automation comparison sets them side by side, and our document generation services start from one question: whether Salesforce alone is enough.
How Do You Implement Conga Composer in Salesforce?
Inventory the documents first, design the data second, and build templates last. Installation takes minutes; the real work is deciding which records feed each document, cleaning the data they depend on, and testing every variation in a sandbox before users see it.
- 1
Inventory every document. List each quote, letter, invoice and report, who produces it, how often, and what triggers it. Merge near-duplicates now, before they become separate templates.
- 2
Install in a sandbox. Use "Try It" on the AppExchange for a sandbox and "Get It Now" for production, with System Administrator credentials, and install for all users as Conga recommends. Paid subscribers then email Conga onboarding to provision licenses.
- 3
Configure Composer Setup. Connected apps, remote sites, the Composer service user and the user licenses all need to be in place before the first solution runs.
- 4
Design the data. Write the SOQL queries or reports for each related list, with filters such as "active matters only" or "open invoices only", so the document never shows a stale row.
- 5
Build templates and solutions. Add merge fields, set button parameters for templates, save location, email and background mode, and place the buttons on the right page layouts.
- 6
Automate what should not need a click. Add Conga Trigger with Flow for event-driven documents and Conga Batch for scheduled runs. Then connect eSignature.
- 7
Test, migrate and assign an owner. Test every template variation with real records, migrate solutions to production, and name the person who owns template changes after go-live.
Conga also offers an Upgrade Program, an automated tool that keeps Conga managed packages in your org on the latest versions.
What Goes Wrong in Conga Implementations?
Most problems are not Conga bugs; they are data, ownership and maintenance problems that show up in the documents. Plan for these five from the start, or check for them in an existing Conga setup.
What Does Conga Automation Look Like in Practice?
The best results come from narrow, well-defined document flows, each tied to the record that drives it. Three published Twopir Consulting projects show the pattern across legal, manufacturing and real estate.
Legal document automation
US family law firm · 2024Built with: Conga Composer, Sales Cloud, SOQL filters, Conga email templates, Salesforce Files
Staff spent 20 to 30 minutes per document on fee statements, retainers, payment summaries, engagement letters and matter reports. We built five Conga templates with filtered queries across contacts, matters, invoices and payments, and one-click buttons that generate, attach and email the PDF. Each document now takes under 60 seconds, a 90% time saving, and closed or inactive matters no longer appear in billing documents. Read the legal document automation case study.
Multi-entity invoice automation
Manufacturer · NZ and Australia · 2025Built with: Conga Composer, Conga Batch, Conga Trigger, Salesforce Flow, outbound messages
A three-entity industrial equipment manufacturer maintained branding and templates by hand for each company and saw duplicated invoice lines. We built one document framework for all three entities, rebuilt the queries with a composite grouping key, and used Flow with Conga Trigger to send credit notes and statements automatically. Manual document processing effort fell by more than 80%, with zero duplicate invoice lines after the rebuild. Read the invoice automation case study.
Conga and DocuSign in one workflow
US real estate firm · 2026Built with: Salesforce, Conga, DocuSign, Apex
License agreements were drafted by hand and signed over email, and the rent roll was updated manually. We connected Salesforce, Conga and DocuSign into one automated path from generation to signature, with a scheduled Apex job that updates the rent roll, so there is no manual re-entry. Twopir Consulting remains the support partner. Read the Salesforce, Conga and DocuSign case study.
Our Conga Salesforce consulting covers Composer, CLM, CPQ and Conga Sign as one system, with dedicated Conga CLM, Conga CPQ and Conga Sign implementations. For an existing setup, our Conga support and managed services handle release regression testing and template governance, including deployments we did not build.
The Bottom Line
Conga for Salesforce earns its place when documents are frequent, data-heavy and tied to revenue. Start with the document that costs your team the most time, prove it with Composer, then automate and add signatures. Bring in CLM or CPQ only when negotiation or pricing, not paperwork, is the real bottleneck.
- 1
Treat Conga as a separate vendor with its own licenses, packages and release cycle.
- 2
Use Composer for documents, Sign for signatures, CLM for contracts and CPQ for pricing.
- 3
Design queries and filters before templates, and keep templates few.
- 4
Automate with Conga Trigger and Flow, or Conga Batch, wherever a click adds nothing.
- 5
Retire legacy product names from your plans, and regression-test documents after every release.
Turn Your Slowest Document Into One Click
On a 30-minute discovery call, a Twopir Conga consultant will review how your quotes, contracts and invoices are produced today, and recommend whether Composer, CLM, CPQ, Sign or Salesforce's own tools fit best.
Schedule a Discovery CallFrequently Asked Questions
No. Conga is an independent software company. Its Salesforce products, such as Conga Composer, Conga Sign, Conga CLM and Conga CPQ, install as managed packages from the Salesforce AppExchange and are licensed separately from Salesforce. They store and read data in your Salesforce org, so users work without leaving Salesforce.
Conga Composer generates documents and reports from Salesforce data. It merges fields from a record and its related records into Word, Excel, PowerPoint, PDF or HTML email templates, then downloads, emails, saves or sends the result for signature. Common uses are proposals, quotes, engagement letters, invoices, statements and account reports.
Composer produces documents; CLM manages contracts across their whole life. Composer fills templates with Salesforce data. Conga CLM handles the contract request, drafting, redlining, approvals, signature, storage and renewal, with clause control and an audit trail. Choose Composer when the problem is producing documents, and CLM when legal negotiation and governance are the problem.
Yes. Conga Trigger runs a Composer solution when Salesforce automation such as a Flow fires, and Conga Batch runs it across many records on a schedule. Both are add-ons to Composer. Background mode parameters let a solution run with no dialog, so documents can be generated, saved and emailed without anyone clicking a button.
Yes. Conga documents a one-click pattern where Composer saves the merged document to the Salesforce record and updates a field, and a Salesforce Flow then sends it through DocuSign for Salesforce with an envelope template. Composer also integrates with Conga Sign and with Adobe Sign through its button parameters.
Conga does not publish list prices. Its pricing page is a request form, and cost depends on the products, add-ons such as Conga Batch and Conga Trigger, and the number of users. Budget for implementation and template maintenance as well as licenses, and compare against Salesforce's own Document Generation for simpler needs.
Conga's retirement schedule lists Conga Courier, Conga Mail Merge, Composer 7 and Quick Merge, and Conga AI Analyze as end of life, and Conga Contracts as end of sale from November 2025. Conga Orchestrate and Conga Grid are still current, and Conga Collaborate is still documented but no longer promoted as a separate product.
Twopir Consulting
Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Conga document, contract and quoting automation on Salesforce.