SFDC Integration

The Kronologic Active Scheduling platform requires contact information and optional timing events to deliver the value of meeting automation. Salesforce is common source of this contact & timing event data, and with Salesforce APIs Kronologic is able to import contact information and action on any field associated with a SDFC lead object within an average of 2.5 minutes of the associated timing event. Because the modern sales-stack requires a more powerful integration than simple record import. Kronologic maintains a 6 function integration.

6 ways Kronologic Integrates with Salesforce

Import contact information from a SFDC lead object.
Activate Kronologic contacts from timing events represented as a field changes in SFDC.
Update a Salesforce record when an instance status change occurs to a related Kronologic contact.
Update lead owners in SFDC when Kronologic completes lead routing. (Beta)
Salesforce can tell Kronologic to deactivate a contact on a field change associated with that lead in SFDC.
Update a lead record with email & invite attempts using a BCC address associated a SFDCinstance or SFDC user. (Beta)

Using Channels

4 of the 6 Integrations listed above are managed though Channels. There are 3 types of channels that work with Salesforce. Import, Intercept, & Update. Check out our documentation on Channels.

Authentication

Authentication Oauth2 Endpoint

https://login.salesforce.com/services/oauth2/authorize

Access Scopes

full

refresh_token

API Calls

Type	Method	Details
info	user_info	Retrieves users email and name
query	query: SELECT Id FROM User WHERE email =	Retrieves identifier for a user
query	query: SELECT Id FROM Lead WHERE email =	Retrieves identifier for a lead
update	update: 'Lead', data	Updates owner identifier where data: data = { Id: lead.Id, OwnerId: owner.id, <lead defined fields>}
query	query: SELECT <fields> FROM Lead WHERE LastModifiedDate >=	Retrieves lead data where the fields are either all or a subset of: Id Email OwnerId LastModifiedDate <lead defined fields>
info	describe: "Lead"	Retrieves all lead defined

Configuring an Integration User

In order to integrate Kronologic with your Salesforce environment, and to do so in line with the principle of least privilege, Salesforce admin should create an integration user and only grant read/write access to that integration user for the fields and objects to be used in your specific use case(s).

At a minimum, Kronologic requires read access to the following fields in order to ingest the contact information of a person you wish to schedule a meeting with:

-Id
-Email
-OwnerID
-LastModifiedDate
-Company
-FirstName
-LastName
-Phone
-State
-PostalCode
-Owner.Email

Note: The fields for which read access is required are the same no matter the object in question (lead, contact, opportunity, campaign member)

In addition to the above, Salesforce admin will need to grant read access to any fields you wish to use to configure a Kronologic Channel. For example, if you want all Leads that belong to Mary with a Score greater than 85 and a Status of New to go to Kronologic for scheduling, the Salesforce admin would need to ensure the integration user has read access to the “Score” and “Status” fields on the lead object in addition to the ones listed above.

Important Note Regarding Lookup Fields: If you plan to use a lookup field as a criteria in your filter logic, the integration user will need read access to the referenced object as well.

If you want Kronologic to be able to “report back” to Salesforce, i.e. update the lead/contact/opportunity contact/campaign member when Kronologic receives a response or schedules a meeting, the Salesforce admin will need to grant the integration user write access to the fields to be updated.

Acknowledging that the following won’t work for all environments, it is somewhat common for Salesforce administrators to create the integration user with a permission set mirroring that of a Sales Development Representative or an Inside Sales Representative as those user profiles tend to have read/write access to the vast majority of fields required for actioning and reporting while simultaneously denying access to more sensitive information.

API Call Volume

Kronologic Checks Salesforce for record changes every 5 minutes.

API Name vs Value

Kronologic depends on the API Name with utilizing custom field in Channel logic, because of this be sure to set any filter to respect what is defined in SFDC.

If the object isn' released or managed, you can change the Objects API name by clicking Edit (Setup->Create->Objects) next to the Object: Then, simply type in a new name and hit save: It will probably warn you about making changes to names for existing integrations, assuming you're ok with that just ignore.

Security & Privacy

Please visit www.kronologic.ai/trust to see how we work hard to earn and maintain your trust. And read more about to our privacy policy and ter ms & conditions.