With Juro's Salesforce integration, you can create a single source of truth between your CRM and CLM, where changes made in one platform are reflected in the other.
Field mapping 📜
You must be a Salesforce Admin to map template smartfields to your Salesforce fields (you don't need to be an Org Admin in Juro). To get started from Salesforce, you'll need:
the parent object
any relevant child objects
the Salesforce field
Mapping basic object fields 🥫
To map basic object fields:
3. Open the Smartfields tab and click the Path Builder icon in the relevant row. |
|
NB: Required fields 📒
There are two types of Required fields which are fundamental to Juro's contract creation flow and must be mapped to a Salesforce field.
System fields: For example, the Counterparty Legal Name field names both the contracts created from a template and the first external signing side for each one.
Internal Form fields marked as 'Required': these fields are linked to questions that your users answer at the very beginning of the contract creation stage. These answers then populate the linked smartfields on generated contracts.
A required field will show a ✔️ icon in the Required column of your Smartfields mapping page.
Synchronising data between Juro and Salesforce 📡
Juro's Salesforce integration supports inbound, outbound and two-way sync functionality for mapped fields:
➡️ Outbound sync: pushes Salesforce field data to the mapped Juro smartfield at contract creation. Post-creation, saved updates to these fields show in their mapped Juro smartfields.
⬅️ Inbound sync: pushes Juro smartfield data to the mapped Salesforce field post-contract creation. Post-creation, saved updates to these smartfields in Juro show in their mapped fields in Salesforce.
🔁 Two-way sync: pushes Juro smartfield data to the Salesforce field post-contract creation. Post-creation, saved updates in either platform update their counterpart field in both Salesforce and Juro.
🔕 None: pushes Salesforce field data to the Juro smartfield once, on contract creation only.
💡 NOTE: The sync feature is disabled by default and must be enabled following the above steps. Changes do not reflect on fully signed contracts.
You can view which field types cannot be synchronised in our sync matrix.
To set up a field sync:
1. Click the Synchronize column's pencil icon in the relevant row. Next, select your sync direction. |
|
Mapping tables dynamically 📊
You can map smartfields in static table cells using the steps above, as the smartfield data changes rather than the table's broader structure.
If you want to structure a table based on your Object's line items, Juro's dynamic table mapping feature can achieve this.
1. In your Juro template, create a table with a header label for as many columns as you need. |
|
You don't need to add empty or placeholder rows: this feature automatically adds and populates rows per mapped Salesforce line item. |
3. In the Tables tab, click the path builder icon and map the table to the Salesforce object (not the individual rows/columns yet). Click Save. |
|
4. Your table details can be further configured from the Name column. Each row in Salesforce corresponds to your Juro template's table columns. |
|
When users create contracts from this template, Juro will dynamically add and populate the table to match the line items present.
💡 NOTE: As the columns in this flow are mapped dynamically, Juro can't adjust the format of the data being pushed from Salesforce into Juro. As such, this will display as it is set in Salesforce.
Tables support the outbound sync detailed above. Changes can be synced from Salesforce to Juro upon contract creation. Any changes to line items post-creation will update the existing Juro contract's table.
Mapping signatories ✍️
Mapping internal and external signatories in Salesforce ensures the correct email from your object shows on your external signing links.
To map signatories from Salesforce:
1. On your Juro template, add Signature links for the relevant signing sides and republish it. Click here to learn more about adding Signature links. |
|
4. Open the path builder and select the relevant Contacts or Contact Roles objects. Click Save to apply the changes. |
💡 NOTE: Juro can only map signatories to emails within related objects. |
|
Using the SOQL filter, you can filter through roles and select a specific role type as the signatory, e.g. role = 'decision maker'. If no filter is applied, Juro selects the first contact email from this object. |
5. Click the Email Path Builder icon in the relevant row and map this to the field containing the signatory's email address: the path here is typically Email. |
|
Click Save to apply the changes. |
For future contracts, this mapping will:
Read the Salesforce object
Select the relevant contact
Apply their email address to the Signature link.
Creating a contract ✈️
You're now set up to create contracts directly from Salesforce.
To do this:
1. From the relevant page where you've added the Juro Contract Object (e.g. an Opportunity), click the downward-facing arrow and select New. |
|
2. Select the relevant template and click Save (or Save & New for multiple contracts). |
|
When they select a template for the first time, a user may need to type the full template name and press Enter for it to show in the list of options. |
💡 NOTE: A contract will only be sent out for signature if the external signature link is populated and no approval flow is in place.
If you encounter any error messages, we have a dedicated troubleshooting article with suggested next steps for the most common errors.
Using Juro's async negotiation for Salesforce contracts 🎴
Juro contracts created through the Salesforce integration are also compatible with the Async Negotiation flow.
Enabling this on your Juro template makes this option available on contracts you create from Salesforce using that template.
Counterparty redlines accepted by you in Juro will pass back to and be reflected in your Salesforce instance. When data is changed in both Salesforce and the counterparty's version, this is presented to you in summary form upon receiving a new version so you can decide which data to update.
To use this feature, you must update to the latest version of our Salesforce package (v 1.76), which you can do by clicking the button below:
💁♀️ As always, our Support Team is happy to help you with anything further if needed. Start a chat with us right here by clicking the Intercom button in the bottom-right-hand corner of this page.
Alternatively, you can email us at support@juro.com 🚀


















