Conga CLM

This page records how composerID publishes into Conga CLM: the vendor’s API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it. Conga CLM is an enterprise contract-lifecycle platform of Apttus lineage, shipped in two materially different deployments: CLM for Salesforce (a managed package running inside the customer’s own Salesforce org) and CLM on the Conga Advantage Platform (Conga-hosted REST APIs). composerID publishes into Conga by creating or amending an Agreement record once a decision has been taken, carrying the Intent ID onto that record so the paper reconciles back to the decision. Conga records and progresses the agreement; it is not the system that decided the engagement should happen.

Category: Signature & Contract Management. Coverage status: Carrier mapped. Vendor documentation: public developer portal.

Integration path

How composerID connects to this destination, at a glance.

Step	Detail
Authentication	Deployment-dependent, and the two are not interchangeable.
composerID publishes	Agreement / contract record: Contract / agreement name
Intent ID lands on	`contract` `ExternalId`, written into the destination record
Carrier evidence	Cited: the vendor documents this field on this object. Source: Conga CLM API: Create contract, checked 23 September 2026.
Back-sync	Webhooks and polling: some lifecycle events are pushed, the rest are read on a schedule.

Vendor documentation

Conga Developer Portal - Contracts (CLM REST reference)

Advantage Platform - REST API introduction

Authenticating Agreement Services APIs (CLM for Salesforce)

CLM SOAP API reference (Agreement Web Service)

CLM for Advantage Platform - documentation

API posture

Aspect	Detail
Authentication	Deployment-dependent, and the two are not interchangeable. Advantage Platform: OAuth 2.0 client credentials - a Conga API Connection issues a client ID and secret, exchanged for a bearer token with roughly an hour’s lifetime. CLM for Salesforce: authentication is Salesforce’s own OAuth 2.0 against the customer org (the legacy SOAP surface authenticates via an Apttus login call first).
Style	Advantage Platform: REST/JSON with resource-oriented URLs and HTTP status codes for errors. CLM for Salesforce is Salesforce-platform-based, which changes both auth and object model - the surface is Salesforce REST/SOAP over managed-package objects plus Conga Apex REST services, so a publisher connects to the customer’s Salesforce org rather than a Conga-hosted tenant. A SOAP Agreement Web Service covers activate, select-template and publish operations. Pagination conventions are not publicly documented.
Base URL	Advantage Platform: https://rls.congacloud.com/api/clm/v1/… · CLM for Salesforce: https://{myorg}.force.com/services/apexrest/Apttus/clm/{version}/{API} alongside the org’s standard Salesforce REST endpoints
Webhooks	No CLM-specific webhook or event-subscription API is publicly documented. Webhooks are documented for adjacent Conga products (Conga Sign event notifications, and the separate Novatus-lineage Conga Contracts) - do not assume they cover CLM. Salesforce-hosted deployments can use Salesforce-native Platform Events and Change Data Capture, but that is a Salesforce capability rather than a Conga-documented CLM one, so confirm the event path per deployment.
Events posture	Webhooks and polling
Rate limits	None published for CLM on either deployment. For CLM for Salesforce the binding constraint is the customer’s own Salesforce org limits, including per-transaction governor limits and total org API calls per rolling 24 hours; no limits are documented for the Conga-hosted endpoints.
Objects	Advantage Platform CLM v1: contracts (create-offline, amend, activate, terminate), contract clauses, supporting documents, document generation and preview, reviews. CLM for Salesforce: the managed-package Agreement object and its related clause, template and document records, exposed via Salesforce REST/SOAP plus the Agreement Web Service.

Publish target and field mapping

Each object below pairs the canonical intent fields with the destination’s own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.

Agreement / contract record

Advantage Platform: create against the CLM v1 contracts resource. Salesforce: insert the managed-package Agreement object, then use the Agreement Web Service to select a template and generate.

Mapping	Detail
Canonical to destination	title
Target	Contract / agreement name
Requirement	Required
Notes	The publish target is the agreement record itself; document generation is a second step against the created record rather than part of creation.

Agreement → reference field

Carrier for the Intent ID

Mapping	Detail
Canonical to destination	intent_id
Target	ExternalId on the contract record (Conga Advantage Platform); on CLM for Salesforce, a Salesforce External ID field
Requirement	Tenant required
Notes	ExternalId is a native, writable, queryable contract field on the Advantage Platform; a tenant custom field is the fallback

Agreement → counterparty

Account or party association

Mapping	Detail
Canonical to destination	counterparty
Target	Account / party record referenced by the agreement
Requirement	Required
Notes	Salesforce deployments resolve to a Salesforce Account; Advantage Platform deployments to the platform’s account record. Either way the counterparty must pre-exist or be created first, so agree a look-up-or-create strategy per tenant.

Agreement → commercial terms

Term and value fields on the agreement header

Mapping	Detail
Canonical to destination	start_date, end_date, value
Target	Contract term start and end dates, contract value
Requirement	Tenant
Notes	Field API names differ between the managed package and the Advantage Platform contract model, and are commonly extended per customer - confirm against the tenant’s schema rather than mapping generically.

Supporting document

Attach the decision record alongside the paper

Mapping	Detail
Canonical to destination	defence_file_ref
Target	Supporting document on the contract record (Advantage Platform), or the publish-document operations on the Agreement Web Service (Salesforce)
Requirement	Recommended
Notes	Keeps the rationale travelling with the agreement so an auditor reading the contract can reach the decision behind it.

The first question on any Conga engagement is which Conga CLM this is: the Salesforce managed package or CLM on the Conga Advantage Platform. They differ in authentication, base URL and object model, and a connector built for one does not work against the other. Conga’s estate also contains several similarly named contract products (Conga Contracts and Conga Contracts for Salesforce are a different lineage again), so confirm the product, not just the vendor. Beyond that, the Intent ID carrier field, the agreement record type, the generation template and the approval path are all tenant-configured; on Salesforce deployments the customer’s org API limits and managed-package version also constrain throughput.

Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.

⌘I

Get started

Concepts

Guides

Destinations

Upstream connectors

API reference

Endpoints

Manuscript API (Triage)

Manuscript endpoints

Resources

Integration path

Vendor documentation

Conga Developer Portal - Contracts (CLM REST reference)

Advantage Platform - REST API introduction

Authenticating Agreement Services APIs (CLM for Salesforce)

CLM SOAP API reference (Agreement Web Service)

CLM for Advantage Platform - documentation

API posture

Publish target and field mapping

Next steps

How composerID connects

Publishing

All destinations

​Integration path

​Vendor documentation

Conga Developer Portal - Contracts (CLM REST reference)

Advantage Platform - REST API introduction

Authenticating Agreement Services APIs (CLM for Salesforce)

CLM SOAP API reference (Agreement Web Service)

CLM for Advantage Platform - documentation

​API posture

​Publish target and field mapping

​Next steps

How composerID connects

Publishing

All destinations

Integration path

Vendor documentation

API posture

Publish target and field mapping

Next steps