All Collections
Connecting Salesforce & Juro: Mapping
Connecting Salesforce & Juro: Mapping

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

Jeremy Huitson avatar
Written by Jeremy Huitson
Updated over a week ago

Introduction πŸ‘‹

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

This ensures that the correct data is sent to contracts and in the right format to allow you to synchronise data between the two platforms.

β€‹πŸ’‘ NB: Juro's Negotiation flow cannot be activated for any contracts generated from Salesforce.

Field mapping πŸ“œ

Juro smartfields that have been set up within templates will also show in Salesforce.

To achieve this, you'll need the Salesforce path to:

  • the parent object

  • any relevant child objects, and

  • the Salesforce field.

Mapping basic object fields πŸ₯«

To map fields:

  1. Go to the Juro application and Templates in Salesforce

  2. Select the template you'd like to start mapping by clicking on the template ID in the Name column

  3. Open the Smartfields tab: you will see the title of all smartfields set up for this template, each of which will need to be mapped individually

  4. The fourth column contains Juro's path builder. Clicking on this icon will surface all available parent objects. You will need to click through to relevant child objects and continue selecting to find the field you'd like to map. As you click, the Salesforce path will automatically be built and shown above in blue above with the relevant syntaxes

  5. Click Save.

Required fields πŸ“’

You will notice that some fields are set up as Required in the fifth column. This means that these have been set as required within the Q&A flow on the template in Juro, where fields must be filled out when creating a contract. If any of the fields are left blank, the contract will not be created.

By default, the counterparty legal name (or Signing Side #2) is a required field as it names the contract and also labels the counterparty in Juro. Required fields can be configured in the Juro Q&A editor.

Synchronising field data for a single source of truth πŸ“‘

Data can be synchronised between Salesforce & Juro so that changes to field data in one system are reflected in the other. In the sixth column, these are set on a field-by-field basis within Salesforce.

Each field can be set to synchronise on an Outbound, Inbound or Two-way basis. As a default, all fields will not sync.

➑️ Outbound sync: pushes Salesforce field data to the Juro smartfield on contract creation and post-creation, any time the Salesforce field is updated and saved, the Juro smartfield will update on the event

⬅️ Inbound sync: pushes Juro smartfield data to the Salesforce field post-contract creation, any time the Juro smartfield is updated and saved, the Salesforce field will update on the event

πŸ” Two-way sync: pushes field data between Salesforce and Juro post-contract creation, any time a field is updated and saved in one application, the field will update on the event in the other application


πŸ’‘ NOTE: If a contract has been fully signed, no changes will be pushed from Salesforce to Juro.

Fields that cannot be synchronised β›”

Unfortunately, some field types on Salesforce cannot be synchronised.
Please find an extensive sync matrix near the bottom of this page.

Dynamic table mapping πŸ“Š

Juro tables can contain individual smartfields in each cell and be mapped as above.

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.

In the Juro template, create a table with as many columns as needed and add a header label to these columns. You don't need to create any empty rows as the integration will automatically populate the correct number of rows per line item found in Salesforce.
In Salesforce, click on the Juro application and then Templates:

  1. Open the Tables tab

  2. Click the path builder icon and map the table to the Salesforce objectΒ (not the individual rows/columns yet)

  3. Click Save

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

  5. Use the path builder icon again here to select the Salesforce column to map. Each column in Salesforce will then be mapped to each column in the Juro template table.

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

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 only. Changes can only be pushed from Salesforce to Juro on contract creation; any changes to line items post-creation will not update the existing Juro contract.

Signatory email mapping ✍️

External and internal signatories can be mapped to push the relevant email address from Salesforce-related objects into Juro on contract creation. It's even possible to send the signing request directly from Salesforce (see below).

To map signatories on a template level:

  1. Navigate to the required template in Salesforce and select Signatures

  2. Click into the 'table' icon that shows "Map Signatories" for the external signing side

  3. 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.

  4. 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 no filter is added, Juro will select the first contact email from this object.

The Email SF path column must be completed to direct Juro to the field that contains the email address of this contact, the path builder is available to the right of this field to support mapping: 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 contract object was added e.g. Account/Opportunity

  2. Select Contracts, and then New

  3. Select the Account and Template*

  4. 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 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 have a dedicated article that has guidance on how to troubleshoot 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 πŸš€

Did this answer your question?