Contract Logix provides an integration with Salesforce and will use the integration of your Contract Logix and Salesforce platforms to empower your Sales organization to request, generate, negotiate, and execute customer agreements faster and more conveniently than ever. The integration of Contract Logix and Salesforce features bi-directional sync of Account, Contact, and Opportunity information, including real-time updates of contract details.
NOTE: You must have an existing Salesforce account to integrate with Contract Logix.
To configure an integration of Contract Logix with Salesforce, it is important to recognize the high-level steps involved. The steps are as follows:
Establish the API Connection through the Client ID and Client Secret protocol.
Select which packaged integrations apply for your Salesforce integration use cases.
Create Application connections for bi-directional communication for each application.
Select the Recipe(s) and Connectors(s) (explained below) you will utilize.
Define the Recipe trigger (when to integrate).
Create Data Mapping (what data and where it goes) in any Update or Create step of the Recipe.
Finally, click Start Recipe to enable the integration.
Integrations are configured by clicking Integrations on the left-side menu of Application Settings as seen below:
NOTE: If you don't see Integrations in the Application Settings menu, contact your Client Success Manager (CSM) for information on activating Integrations for your account.
API Integration
The API Integration tab provides developers a way to enter their authentication keys which will be used to authenticate all API calls to Contract Logix. Additional API keys can be added and labeled as seen in the graphic below. The API keys consist of two fields:
Client ID
Client Secret
The Client ID is unique to your organization's Contract Logix account and is provided for you in the Client ID field. NOTE: Do not delete or alter the auto-generated Client ID number. The Client Secret can be generated by first entering a Client ID and by clicking the Generate Key button. The Client Secret generated is a series of letters and numbers unique to the Client ID. NOTE: It is recommended that you click the Generate Key button once and document your Client ID and Client Secret. This is especially important should you need to re-enter the Client Secret into Contract Logix again.
Connector Recipes
The Connector Recipes tab is where you select the bi-direction communication method and the selection of data points transferred during communication.
Connector - A connector is an app available in the system that enables a connection to external software.
Recipe - A Recipe is a set of step-by-step instructions that uses the Connector to push or pull information and files between connected software. They are similar to Contract Logix's own Workflows and may act in real-time or on a set timed interval.
Salesforce Integration Recipe Packages:
Here's an explanation of what's in the packages:
Salesforce Bi-directional Synchronization - This package contains four recipes:
Sync: Contract Logix to Salesforce (Organizations)
Sync: Salesforce to Contract Logix (Organizations)
Sync: Contract Logix to Salesforce (Contacts)
Sync: Salesforce to Contract Logix (Contacts)
Each recipe activates when a new Contact or Organization record is created or an existing one is updated in Contract Logix and vice versa. It facilitates synchronization between Contract Logix and Salesforce by using custom ID fields.
Salesforce ClosedWon Update - This recipe activates when an Opportunity in the system reaches the 'ClosedWon' stage. Upon this trigger, it automatically creates a new request, incorporating relevant associated data from the Opportunity.
Connector Console
The Connector Console tab contains the Integration Projects. For your organization, there may be multiple Projects. A Project contains Assets, which are the list of Recipes and Connectors.
Connections
Connections can be established to one or more Salesforce accounts. When creating the connection, the Salesforce credentials for accessing the account will be entered.
Connections from Salesforce to Contract Logix can also be established by entering the necessary information, as seen in the graphic below:
Recipes
Recipes consist of operational steps to transfer data back and forth. There's the Trigger Event and the customization of Data Mapping, as described below:
Trigger Event - The Recipe trigger (start) can be based on any information entered within Salesforce and what information causes the trigger can be customized.
Data Mapping - The data information passed to and from the systems need a reference for where the information will be saved when transferred. This process involves choosing the Recipe step and mapping the Data pill to the appropriate field.
Enable the Integration
Once the Recipe has been configured with a Trigger Event and Data mapping, you enable the Integration by clicking Start Recipe.
NOTE: Configuration of the Data Mapping to the appropriate fields needs to be in the correct Object type when the Recipe runs, otherwise an error may occur or the data may end up in the wrong field of the records.