Integrate the customer card with Make

Updated

Introduction

The information you need to resolve cases is often spread across different systems and tools. Searching, clicking around and hunting for it takes time and slows you down. By integrating your systems with Kundo, you get the relevant information right next to the case, so you can answer the customer quickly and correctly.

This guide describes how to integrate your CRM, order system, invoicing system or other systems to show data on the customer card in Kundo.

Contents

Step 1: Create a connection between Kundo and Make

Step 2: Fetch data from your source system using an email address from Kundo

Step 3: Map the data from your source system to fields in Kundo with Kundo's Make module "Return Customer Data"

Step 4: See the result in Kundo

Step 1: Create a connection between Kundo and Make

  1. Log in to the Kundo dashboard.
  2. Click Settings (the cog) at the bottom of the left menu and select Integrations in the submenu.

    The Integrations page under Settings. Annotation 1 marks the Settings cog in the left menu, annotation 2 marks Integrations in the submenu.

  3. Select Generate API key and give the key a name.
  4. Save and copy the API key. Note: This is the only time you will be able to see and copy the key. Store it somewhere safe, for example in a password manager.
  5. Create an account on Make if you don't already have one, and install the Kundo app in your Make organization.
  6. Select the organization you want to add the Kundo app to, and click Install.
  7. In the Make dashboard, click Create a new scenario.
  8. Click the plus sign. Search for Kundo and select Handle customer Data Request.
  9. Click Create a Webhook and enter a name that describes what it does, for example "Get user data from MyService".
  10. Under Connection, if you don't already have a connection to Kundo, click Add, give the connection a name and paste the key from step 4. Then click Save.
  11. Enter a Label. It is shown in Kundo later to indicate which source the data comes from.
  12. Click OK.

Step 1 is now done, and it's time to start fetching data from the source system you want to connect to the customer card in Kundo.

Step 2: Fetch data from your source system using an email address from Kundo

This step looks different depending on how your source system works. Some source systems have an app in Make (for example Shopify, HubSpot and Salesforce). Otherwise you need to build the request yourself with Make's HTTP module.

That makes it hard for us to write a guide that fits every integration through Make. The steps below describe a simple scenario with the HTTP module.

  1. In the Make dashboard you now have a module called Kundo. To add a connection to your source system, click the plus sign to the right of the module.
  2. If your source system has an app in Make, search for it and follow the steps to fetch data based on the email address you receive from Kundo. If the source system doesn't have an app, the HTTP app is usually used to make a regular API request to a service.

Step 3: Map the data from your source system to fields in Kundo with Kundo's Make module "Return Customer Data"

Now that the data has been fetched from your source system, you need to choose which data to show and map it to fields in Kundo.

  1. Click the plus sign next to the module furthest to the right. Search for Kundo and select the Kundo app Return Customer Data.
  2. There are two options here (you can use both together, or just one of them):
    • Info Module – for simple fields such as name, email address and customer number
    • List Module – for lists of data, for example orders, invoices or comments

Info Module

To add fields to an Info Module, click Add item. Three fields appear:

  1. Label – The name of the field shown in Kundo. Kundo provides preset fields as examples, but you can also add your own field with Custom label if none of them fit. Note: Kundo's preset fields are translated if your users use Kundo in different languages. Custom labels are not.
  2. Value – The data from your source system to show under the label.
  3. URL (optional) – A link to your source system. It can be a value fetched directly from the source system (step 2), or a link you build "manually" by combining values from there with a fixed template ("https://example.com/customer/{customer_id}/user/{user_id}").
  4. Repeat this for every data point you want to show in Kundo.

List Modules

To add a list under List Modules, click Add item. First enter general information about the list:

  1. Label – The heading of the list, shown in Kundo. Kundo provides preset fields as examples, but you can also add your own field with Custom label if none of them fit. Note: Kundo's preset fields are translated if your users use Kundo in different languages. Custom labels are not.
  2. URL (optional) – A link to the list in your source system. It can be a value fetched directly from the source system (step 2), or a link you build "manually" by combining values from there with a fixed template ("https://example.com/customer/{customer_id}/orders").

Under items you find the fields you can set for each element in the list. Mapping to these fields has to be done through an Array aggregator in Make. An example shows this best:

Array aggregator example

  1. HubSpot's Make module Search for CRM Objects fetches a list of Deals. Once fetched, each Deal is represented in Make by a so-called bundle.
  2. To map the list of Deals (bundles) to the item fields in the List Module, there is an Array aggregator.
  3. Last comes the Kundo module Return Customer Data.

To make sure no list is generated when Search for CRM Objects returns no matches, add a filter between it and the Array aggregator (click the wrench icon and select Set up filter), like this:

Filter between Search for CRM Objects and Array aggregator

In the Array aggregator, first set:

  • Source Module: The module that generated the list of bundles, that is "Search for CRM Objects".
  • Target Structure type: "Kundo - Return Customer Data [No.] List modules: items".

Once these are selected, the fields for List Modules: items become visible and values can be mapped:

  • Header: The heading for each element. In this example the name is mapped ("Deal name").
  • Secondary: The subheading for each element. In this example the type of Deal is mapped ("Deal type").
  • More: Values that go into an expandable part of each element in the list. Line breaks are allowed, so you can map longer texts or several fields. In this example the value ("Amount") and stage ("Deal stage") are mapped for each Deal in the list.
  • URL (optional): A URL to each element in the source system. If set, the heading (Header) links there. In this example a text template is used where the values for portalId and ID are replaced for each element (mapped from the HubSpot module).

Once the mapping is done in the Array aggregator, you can connect it to the List module items in the Kundo module Return Customer Data:

Connecting the Array aggregator to Return Customer Data

  1. Next to items, turn on mapping mode by clicking Map (it turns blue).
  2. In the field below, select the Array[] that resulted from the mapping in the previous step.

Step 4: See the result in Kundo

In the customer card tab of the case view, data from your external systems is now synced to the customer card, so you can make sure the information shown is correct.

The result on the customer card in Kundo

warning Warning.