This article explains how the Jiminny Salesforce integration works: which Salesforce editions are supported, how Jiminny connects, what it logs, and how it decides which Lead, Contact, Account or Opportunity a call is logged against. It is for Salesforce admins and Jiminny admins setting up or reviewing the integration.
How Jiminny connects to Salesforce
Jiminny uses the Salesforce REST API and the Jiminny Chrome Extension. There are no packages or Apex code to install. It works with Salesforce Lightning and Classic, and has limited support for the Console.
Enterprise and Unlimited editions include REST API access. Professional Edition does not include it by default, so you need the Web API package and API call bundles. To check whether your organisation has the API package, in Salesforce go to Setup > Monitor > System Overview > API usage. If you need to upgrade, contact your Salesforce Account Executive.
Salesforce applies per-organisation and per-user API limits. Jiminny uses caching and a shadow copy of some data to keep its footprint small. Usage spikes on the initial connection, then settles at around 200 API calls per user per day, depending on how much activity goes through Jiminny.
Connecting users
Each user authenticates individually with OAuth 2 when they onboard. To connect users without each of them going through the OAuth flow, see Salesforce Pre-Authorization. If users see connection or sync errors, see Troubleshooting Salesforce.
The integration owner
The integration owner is the Jiminny user whose Salesforce connection is used for metadata and object sync. This must be a Salesforce admin with a Jiminny account, because reading metadata requires permissions that regular users do not have.
To see whether Salesforce is connected and who owns the connection, go to Settings > Integrations. You can change the owner from the same page.
Note: After you change the owner, the new owner has to log in to Jiminny. They are redirected to a page where they connect their Salesforce account. Sync does not resume until they have done this.
What Jiminny logs to Salesforce
Jiminny logs video calls to Salesforce as Task or Event depending on how your integration is configured.
The fields you log are configurable. Typical fields include:
Activity type (for example Discovery Call)
Subject
Stage
Attendee list
Call duration
Link to the call recording
Meeting notes
Call outcome
Users can fill in these fields before, during or after the meeting from the Jiminny sidebar, and the values pre-populate from Salesforce where available. Meetings marked as internal are not logged.
To set up automatic or manual logging, see Setting up CRM Activity Logging. To log a call by hand, see Logging a call.
Logged activities appear under Activity History on the matching Lead, Contact, Account or Opportunity.
How participants are matched to Salesforce records
Jiminny identifies who is on a call and looks them up in Salesforce. How this happens depends on the type of activity.
Scheduled meetings. When a meeting is scheduled in your calendar, Jiminny checks each attendee against Salesforce using the email address in the invite.
Ad-hoc meetings. When a participant joins, Jiminny checks them against Salesforce using the email address or phone number they provided.
Calls and texts from Salesforce (only for customers using Jiminny Voice). The Jiminny Chrome Extension embeds in the Salesforce page and, where possible, passes the record ID to Jiminny so the customer is set automatically.
Where a call is logged
Once Jiminny knows who was on the call, it decides which record to log the activity against. The same matching is used to associate emails with Salesforce records in Jiminny, but only video calls are logged to Salesforce.
Jiminny runs the following checks in order and stops at the first match.
1. Lead or Contact
Jiminny takes the customer participant's email address and looks for a matching Lead or Contact. If it finds a Lead, the call is logged on the Lead and matching stops.
2. Account
If it finds a Contact, Jiminny uses the Account the Contact belongs to. If there is no Contact, Jiminny looks for an Account whose domain matches the participant's email domain and logs the call against that Account.
3. Opportunity through Contact Roles
If the Contact appears in the Contact Roles of one or more Opportunities, Jiminny only considers those Opportunities. The list is filtered and sorted by your Opportunity matching setting first, then Jiminny takes the first Opportunity that fits, in this order:
The Contact is the Primary contact and the Opportunity is owned by the call host
Any Opportunity owned by the call host
Any Opportunity where the Contact is the Primary contact
The first Opportunity in the list
Note: When an Opportunity is matched through Contact Roles, the call is logged against that Opportunity's Account.
4. Opportunity through the Account
If the Contact is not on any Contact Roles, Jiminny looks at the Account's Opportunities instead. As in step 3, the list is filtered and sorted by your Opportunity matching setting first, then Jiminny takes the first Opportunity that fits:
An Opportunity owned by the call host
Any Opportunity on the Account
The Opportunity matching setting
This setting controls which Opportunities Jiminny considers and how they are ordered before the checks above run. You will find it under Settings > CRM Activity Logging > Company-wide.
Most recently updated open (default) – open Opportunities, most recently updated first
Most recently created open – open Opportunities, most recently created first
Most recently updated – open and closed Opportunities, most recently updated first
Oldest created open – open Opportunities, oldest first