Map customers, appointments and events
Updated
by Tara
Once a connection is created, the admin can set up mapping between JRNI customer, appointments and events, and Salesforce objects and fields as required to define where data needs to be saved.
The platform provides a standard template which supports a basic setup for syncing customer data to the contact object and appointment/event data to the event object in Salesforce. Changes can be made in following cases:
- Require sync to another object (lead) or custom object
- Require more JRNI data to be synced to Salesforce (custom) fields
- Map to different fields
- Log in to Studio at parent company level and go to Settings > Integrations > Salesforce, and click Edit.
- The user will arrive on the following screen. Following Mapping options are there:
-Client template configurations: Mapping between Customers and Contact/Lead (or other Custom Object)
-Booking template configurations: Mapping between Appointment and Event (or other Custom Object)
-Event template configurations: Mapping between JRNI Events and SF Event (coming soon...)
Part 1: Mapping of Customer information
Field | Description | Example |
Client object name | Defines which Object we need to send our data too. | Contact |
Client mapping of fields (1) | The actually mapping finds place here. The first field is the field name in Salesforce, the second part is the liquid JRNI field. Create/update if source is JRNI. | "Email__c": "{{client.email}}" |
Client mapping of fields (2) | Create/update if source is both JRNI and Salesforce. | "booking__ClientId__c": "{{client.id}}" |
Client unique field | Unique identifier for a record created as a contact. | booking__ClientId__c |
Client relationship key | The key/field that can be used to link Objects with the contact record. | WhoId |
See more custom mapping options here
Part 2: Mapping of Appointment Booking information
Field | Description | Example |
Booking object name | Defines which Object we need to send our data too. | Event |
Booking mapping of fields | The actually mapping finds place here. The first field is the field name in Salesforce, the second part is the liquid JRNI field. Create/update if source is JRNI. | "booking__BookingId__c": "{{booking.id}}" |
Booking unique field | Unique identifier for a record created as a contact. | booking__BookingId__c |
Booking relationship key | The key/field that can be used to link Objects with the contact record. | WhoId |
Booking owner id | The Salesforce user that owns this record. | OwnerId |
See more custom mapping options here
Part 3: Mapping of Event Booking information
Events are not available yet, but keep an eye out.. they'll be along soon!
