The Kustomer integration enables seamless data exchange between Experiences by Jebbit and Kustomer, allowing for real-time synchronization of customer interactions and profile information. This integration facilitates personalized customer experiences by ensuring that data collected in Experiences by Jebbit is readily available in Kustomer, and vice versa.
Before you begin
Confirm access to both Experiences by Jebbit and Kustomer with the necessary permissions to create and manage integrations.
API credentials from Kustomer to authenticate the connection.
A clear understanding of the data fields you plan to synchronize between the two platforms.
Request the integration with our team.
Create a Kustomer integration
Follow these steps to securely provide Experiences by Jebbit with access for the integration.
Create a new API key
All requests to the Kustomer API must be authenticated using an API token included in the Authorization header. To generate this token:
In Kustomer, go to Settings > Security > API Keys.
Select Create API Key.
Choose an appropriate API Role based on the required permissions.
Add a descriptive Label to identify the key.
Save the key securely.
Create custom klasses
Use custom Klasses to model business objects or map to specialized processes.
To create a custom Klass:
Go to Settings and select Platform > Klasses.
Select Add Klass.
Enter a name. Optionally, select an icon and the icon's color.
Select Create.
Add custom attributes to a Klass
You can add attributes to both standard and custom Klasses.
To add an attribute:
From that object's page, select Create Attribute.
Enter a display name for the attribute. Note the following:
When you create the new attribute, Kustomer will automatically generate the attribute's name based on the Display Name and data Type. For example, an attribute added to a custom Klass for an order that has "Assigned User" as the Display Name will have "assignedUserId" as the Name.
An attribute's Display Name and Value properties can be changed after creation, but Name and data Type cannot.
Select a data type from the Type drop-down menu. The following options are available:
Single line text - for example, product name or item color.
Paragraph - for example, notes on a transaction.
Number - for example, price, quantity, or numeric tracking number.
Date - for example, 01/01/2020.
URL - for example, www.kustomer.com
True/False
Multi level list - for example, Level 1 > Item 1.
Id - for example, a kObject.
User Picker - for example, John Doe. Only active users within your org can be selected.
Customer Picker - for example, Jane Doe.
Select the field value for the attribute type. Available options are:
Single Value are fields that accept any value that matches the data type.
Option List will only accept pre-defined values.
Select Create. Continue adding the necessary attributes for that Klass.
Tip: You can require fields to be filled out before marking a conversation done on the standard Conversation Klass.
Copy API integration information to a .txt file
Collect the API Token and KObjects/atrributes Jebbit will pass attributes collected from Jebbit as kobject, specifically passing the kobject field ID.
Copy the values from the previous steps into your .txt file.
Submit your .txt file via Dropbox file request
Transfer the information from your .txt file via the provided URL.
Next steps
The integrations Team will be notified once this information is submitted, and will be in contact with you regarding timelines and testing.