Salesforce Integration Overview (Legacy)

This article provides a brief overview of Ironclad's Salesforce integration.

Ironclad’s Salesforce Integration Legacy Features

Ironclad's Salesforce Integration consists of three features:
1. Workflow Launch allows an Ironclad user to create a contract by filling Ironclad launch forms with data pulled from Salesforce, either to launch a workflow or update it if information in Salesforce changes. Workflow Launch can also be leveraged by building a button in Salesforce to redirect users to Ironclad with the launch form pre-filled. Workflow Launch can pull from standard or custom objects.
2. Workflow Sync provides visibility into the progress of a workflow in Ironclad directly in Salesforce using the Ironclad Workflow object. Workflow Sync requires the installation of the Ironclad Managed Package.
3. Record Sync pushes completed contracts from Ironclad (including the associated metadata and, if desired, the signed PDF) to a Contract object in Salesforce. If applicable, Record Sync can also update existing Salesforce objects, such as fields on an Opportunity, or create new Salesforce objects, such as a new Contact with the signer's name, title, and email.

The Salesforce integration is compatible with both Salesforce Classic and Salesforce Lightning.

To access the Salesforce configuration in Ironclad, click on your profile icon located in the top right corner. Navigate to Company Settings > Integrations > Salesforce. This page shows all of your currently configured integrations.

Requirements

To integrate your Salesforce instance with Ironclad, you need the following:

• Administrator privileges in Ironclad. If you don't see Company Settings, you may not be an administrator. For admin privileges, contact a member of your legal team who is responsible for your Ironclad deployment.
• One of the following Salesforce editions:
  • Professional
  • Enterprise
  • Unlimited
  • Force.com
  • Developer
  • Performance
• A Salesforce account to link to Ironclad

Salesforce Integration Components

Salesforce authentication and data transfer consist of three main components:

• Service Account: Your service account is are responsible for Workflow Sync to create/write updates to the Ironclad Workflow object and Record Sync object creates/writes/reads/edits. We highly recommend using a generic service account, instead of an individual named user license.
• Individual Accounts: Individuals must connect their Salesforce accounts in order to use Workflow Launch. This is used to read information from mapped Salesforce fields and fill in launch form information. It also respects any permissions the user has in Salesforce, which can result in errors, such as Pull from Salesforce failing.
• Managed Package: You can install Ironclad’s Managed Package to your Salesforce instance, which consists of five Custom objects. These objects are used to receive structured information about the contracting workflow in Ironclad as it progresses through the steps. We highly recommend that you Install for All Users to make sure that there are no permissions issues.

After you've installed Ironclad's Managed Package, you also need to create the following field in your Salesforce instance:

• Custom Lookup Relationship field type on Salesforce object, such as Account or Opportunity, to Ironclad Workflow.

If you want to provide a link directly in Salesforce to track your Ironclad workflows, add the Ironclad Workflow field to your page layout to enable Workflow Sync.

Authentication Method

Ironclad uses OAuth authentication when integrating with Salesforce. The service account is used to connect the two instances and create/write/read/edit objects in Salesforce. An individual’s account is used to read from the objects they have access to in Salesforce. Because Ironclad authenticates with OAuth, you can revoke access from Ironclad whenever necessary.

Service Account Requirements

The service account does not need system admin privileges in Salesforce, but needs create/read/write/create permissions on objects, depending on your integration setup, such as Account, Opportunity, Quote, Ironclad Contract, etc.
It is required to have the following:

1. API enabled
2. Field Level Security read/write on the Lookup Relationship fields to the custom Ironclad Workflow object on Account, Opportunity, etc.
3. Field Level Security read/write and on any field mapped in Workflow Launch configuration, such as Counterparty Name Counterparty Signer Name, Counterparty Signer Email
4. Record sharing to any and all qualifying Salesforce records used in the integration

Data Transfer Methodology

Ironclad sends data directly between servers via the Salesforce API, rather than having the browsers communicate across domains. The only data that is transferred across domains in the browser are Salesforce Object IDs. When you have an Ironclad launch button in Salesforce, it is a URL that contains the Salesforce Object ID (the launch target). Ironclad takes that Object ID and asks Salesforce for the relevant fields via the API using server-to-server communication.