Salesforce Integration with Conga CLM
Integrate Conga CLM for Advantage Platform directly into the Salesforce Lightning interface to enable contract management without leaving your CRM environment.
| Layer | Role |
|---|---|
| Salesforce Org | Host environment; provides the UI shell, security settings, custom settings, Lightning record pages, and the Visualforce page that embeds Conga CLM. |
| Workato | Middleware integration platform that hosts recipes for data synchronization of Accounts and Opportunities between Salesforce and Conga CLM. |
| Conga Advantage Platform | Exposes API connections (API-to-API and UI-to-API) and stores contract data. The embedded Conga CLM pages are surfaced inside Salesforce via a Lightning Web Component (LWC) and a Visualforce page. |
API Collection and Connections
- SF_Connection_DEV: Salesforce org connection (authenticated with Admin credentials)
- Conga_Connection_DEV: Conga Advantage Platform connection (requires Platform User ID, Client ID, Client Secret, token, and base URI from the API-to-API connection)
Workato Recipes and Endpoints
| Recipe Name | Endpoint | Purpose |
|---|---|---|
| [CLM] REC | SF_Create/FetchAccount | CLM_SF_CreateFetchAccount |
|
| [CLM] REC | CLM_SF_CreateFetchOpportunities | CLM_SF_CreateFetchOpportunities |
|
To make new custom fields appear in a Workato recipe after adding them in Salesforce, you must refresh the connection or reauthorize the Salesforce org.Workato caches the object structure, so new fields will not appear until reconnection.
- If a picklist field value sent from Salesforce does not exist in the Conga Advantage Platform picklist field values, that field update is skipped (other fields still update normally). If the value does exist, it is updated. Currently the Account Type field has this skip logic applied. You must add skip logic for any additional picklist fields.
- Currently, contact synchronization is not supported. Salesforce does not have a Primary Contact field on Account, so there is no reliable way to determine which contact to synchronize. No contact records are synchronized between Salesforce and Conga CLM.
Integration Architecture
All contract-related data resides exclusively on the Advantage Platform. No contract objects are created in Salesforce, eliminating data duplication. The embedded Advantage Platform UI is the single interface for all contract operations, and all documents are stored and accessed through the Advantage Platform.
This architecture supports data residency requirements, ensures compliance with data localization policies, and removes dependency on Salesforce storage.
Before You Begin
- Conga Contract Lifecycle Management version 17.819 or later is installed.
- Conga For Salesforce version 3.16 or later is installed.
- A Workato workspace is available.
- The recipe package zip file, containing connections, recipes, and endpoints is available for import. This zip is needed for the CLM Salesforce API collection, two recipes, and both connections.
- Admin credentials are required for both the Salesforce org and the Conga Advantage Platform to create connections.
- The Salesforce org is onboarded in the Conga Advantage Platform using the Salesforce Org ID.
- The Visualforce base domain for your Salesforce org is available (for example, https://<orgdomain>--c.develop.vf.force.com). Obtain it by previewing any Visualforce page and copying the domain, excluding the /apex/... path.
- The two Conga Advantage Platform URLs for your tenant are available:
- Login URL (for example, https://login-rls.congacloud.com)
- Instance URL (for example, https://prod-rls10.congacloud.com).
- The Salesforce org's base URL is available (for example, https://platformemea.my.salesforce.com). This is required for CORS Origins in the Conga UI-to-API connection and for Session Settings in Salesforce.
