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.

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.

The Salesforce integration with Conga CLM connects Conga CLM for Advantage Platform directly into the Salesforce Lightning interface. Once configured, Salesforce users can access the full range of CLM capabilities — contract creation, approvals, obligation fulfillment, contract search, and dashboards — without leaving Salesforce. As an administrator, you configure three layers that work together to enable this integration: the Salesforce org, Workato as the middleware integration platform, and the Conga Advantage Platform.
LayerRole
Salesforce OrgHost environment; provides the UI shell, security settings, custom settings, Lightning record pages, and the Visualforce page that embeds Conga CLM.
WorkatoMiddleware integration platform that hosts recipes for data synchronization of Accounts and Opportunities between Salesforce and Conga CLM.
Conga Advantage PlatformExposes 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.
Note: Data synchronization of Accounts and Opportunities is unidirectional from Salesforce to Conga Advantage Platform. The data synchronization for related contracts is bidirectional.

API Collection and Connections

All recipes belong to the CLM Salesforce API collection in Workato. The following two connections are required:
  • 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)
Note: Connection names shown above are for the development environment. Connection names must be updated to match the target environment (QA, Production) before activating recipes. For QA testing, clone recipes and switch connections to the QA environment on the cloned copies.

Workato Recipes and Endpoints

The following Workato recipes handle all data synchronization. Each recipe is triggered by Salesforce via an API callout and returns the Conga Advantage Platform record ID.
Recipe NameEndpointPurpose
[CLM] REC | SF_Create/FetchAccountCLM_SF_CreateFetchAccount
  • Synchronizes account data from Salesforce to Conga Advantage Platform.

  • Triggered by the Salesforce through an API callout with AccountId as input parameter.

  • Fetches the account from Salesforce based on AccountId, and searches if same account is present in the Conga or not.

  • Creates the account in Conga Advantage Platform if not available; updates an existing account if available.

  • Returns Conga Advantage Platform ID of the account record.

[CLM] REC | CLM_SF_CreateFetchOpportunitiesCLM_SF_CreateFetchOpportunities
  • Synchronizes Opportunity data from Salesforce to Conga Advantage Platform..

  • Triggered by the Salesforce through an API callout with OpportunityId as input parameter.

  • Fetches the opportunity and its related account data. Creates or updates both the account and the opportunity in Conga Advantage Platform.

  • Returns Conga Advantage Platform ID of the opportunity record.

Note:
  • 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

Ensure all of the following prerequisites are satisfied before starting any configuration tasks. Missing prerequisites will cause steps to fail.
  • 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).
    These must be replaced with actual tenant URLs in all configuration steps. Obtain correct values from the Customer Admin or implementation team.
  • 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.
Note: For new development environments, recipes and connections can also be created directly in Workato without importing the zip package. If you import a package for QA testing, clone the recipes and switch connections to the QA environment on the cloned copies; do not modify the original imported recipes.