Skip to main content
All CollectionsIntegrationsSalesforce
Connecting Salesforce & Juro: Mapping
Connecting Salesforce & Juro: Mapping

Map Salesforce fields to Juro smartfields to synchronise data between the two platforms.

Jimmy Mooring avatar
Written by Jimmy Mooring
Updated over a month ago

Contents 🚀

  1. Introduction

  2. Field mapping

    1. Mapping basic object fields

    2. NB: Required fields

  3. Synchronizing field data between Juro and Salesforce

  4. Mapping dynamic tables

  5. Mapping signatories

  6. Creating a contract from Salesforce

Introduction 👋

Now we will start mapping Salesforce data within objects to the smartfields, tables and signatories in your Juro templates.

💡 NOTE: The Negotiation flow can now be activated for any contracts generated from Salesforce! For more information, please click here.

Field mapping 📜

The smartfields on your Juro templates will also show in Salesforce. Salesforce Admins can map templates even if they are not an Admin in Juro. To map your fields for contract creation, you'll need:

  • the parent object

  • any relevant child objects, and

  • the Salesforce field.

Mapping basic object fields 🥫

To map basic object fields:

1. Open the Juro app in Salesforce and click Templates.

2. Go to the Name column and click the ID of the template you'd want to map.

3. Open the Smartfields tab. Here you will see all of the smartfields from your template. Now, it's time to start mapping.

4. Click the Path Builder icon in the row of the relevant smartfield. This will show all available parent objects, which when clicked through, will show child objects for you to choose from. When you've found the object you're looking for, click Save to apply the mapping.

Repeat this step for all smartfields on your template.

NB: Required fields 📒

Some fields are Required (see the fifth column). Some of these are by default, like Counterparty Legal Name which names both the contract and the counterparty signing side. Others have been assigned as required in the INTERNAL FORMS flow of the template in Juro.

All required fields must be mapped for the contract to be generated.

Required fields can be configured in the INTERNAL FORMS tab of the relevant template.

You can learn more about the Forms feature here.

Synchronising field data between Juro and Salesforce📡

Creating a single source of truth between Juro and Salesforce whereby changes in one platform are reflected in the other can be achieved by applying a sync (inbound, outbound or two-way) to your fields. The syncs will behave as follows:

➡️ Outbound sync: pushes Salesforce field data to the Juro smartfield on contract creation. Post-creation when a Salesforce field is updated and saved, the Juro smartfield will also update with this information.

⬅️ Inbound sync: pushes Juro smartfield data to the Salesforce field post-contract creation. Post-creation when a Juro field is updated and saved, the Salesforce field will also update with this information.

🔁 Two-way sync: pushes Juro smartfield data to the Salesforce field post-contract creation. Post-creation when a field in either platform is updated and saved, the field in the other platform will also update with this information.

🔕 None: pushes Salesforce field data to the Juro smartfield once upon contract creation only.

To set up a field sync:

1. In the Synchronize column, click the pencil item in the row of the relevant smartfield.

2. Click Choose Sync Direction and select the sync type you want to apply to the field.

3. Click Save.

💡 NOTE: The sync feature is turned off for fields by default and must be enabled following the above steps. If a contract has been fully signed, no changes will be pushed from Salesforce to Juro.

Unfortunately, some field types on Salesforce cannot be synchronised.
​
Please find an extensive sync matrix here.

Dynamic table mapping 📊

Juro tables that contain individual smartfields in each cell can be mapped as above (the reason for this is that the table is static and it is the smartfields that are changing rather than the structure of the table.

Alternatively, if you'd like a table in Juro to be populated dynamically based on line items within an object, Juro can do this via our Tables mapping tab:

1. In your Juro template, create a table with as many columns as you need. Add a header label to each of these columns.

You don't need to create empty rows as the mapping will automatically add and populate rows per line item from Salesforce.
​

2. Open the Templates tab of the Juro app in Salesforce. Click Sync template.

3. Open the Tables tab and click the path builder icon and map the table to the Salesforce object (not the individual rows/columns yet). Click Save.

4. Click into each table via the Name column. Each row in Salesforce corresponds to the columns set in the Juro table.

Upon contract creation, the table in Juro will now populate rows dynamically based on how many and which line items there are in this object and adjust the contract length automatically.

💡 NOTE: As the columns are mapped dynamically, Juro is not able to manipulate the formatting of the data pushed from Salesforce to Juro. The formatting and content will show in Juro as it is set in Salesforce.

Tables allow an outbound sync. Changes can be pushed from Salesforce to Juro on contract creation; any changes to line items post-creation will update the existing Juro contract.

Mapping signatories ✍️

You can map internal and external signatories in Salesforce so that the correct email from your object is populated on contract creation.

To map your signatories:

1. Add Signature links for the relevant signing sides in your Juro template and republish it. To learn more about how to add Signature links, click here.
​

2. Open the Templates tab of the Juro app in Salesforce. Click Sync Templates.

3. Open the Signatures tab and click the icon in the Map signatories column for the relevant party.
​

4. Click on the path builder and select the relevant Contacts or Contact Roles objects. Note: Juro can only map signatories to emails within related objects.
​

The SOQL filter here will allow you to filter through e.g. Contact Roles and select a specific role type as the signatory e.g. role = 'decision maker'. If there is no filter, Juro will select the first contact email from this object.

5. Click the Path Builder icon in the Email Path Builder column and map this to the field containing the signatory's email address: the path here is typically Email.

Once saved, this mapping will read the object, select the relevant contact and pre-populate the email address into the signature block for each contract created.

Creating a contract ✈️

Now that the above steps have been completed, you're ready to create a contract right from Salesforce.

To do this:

1. Go to the relevant page where the Juro contract object was added (on an Opportunity, in this example). Click the downward-facing arrow and select New.

2. Select the relevant template.

3. Finally, click Save.

Your contract has been created! With a hard refresh, the Juro contract URL will populate and clicking through will show all the mapped Salesforce data in the Juro contract.

💡 NOTE: This contract will only be sent out for signature if the external signatory is populated and if there is no approval flow in place.

If you encounter any error messages, we also have a dedicated article with guidance on troubleshooting these.

💁‍♀️ 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 your query to support@juro.com 🚀

Did this answer your question?