Zendesk Chat is a real-time online chat application that businesses can use to engage with customers. It was originally marketed as Zopim. Zendesk acquired the company that developed it in 2014, integrated it with Zendesk, and renamed it Zendesk Chat in 2016.

Apache Superset is a cloud-native data exploration and visualization platform that businesses can use to create business intelligence reports and dashboards. It includes a state-of-the-art SQL IDE, and it's open source software, free of cost. The platform was originally developed at Airbnb and donated to the Apache Software Foundation.

Zendesk Chat provides a REST API that lets you get information about accounts, agents, roles, and other elements, all of which have different syntax and return JSON objects with different attributes. If, for example, you wanted to retrieve a list of agents, you would call GET /api/v2/agents. This call has a couple of optional parameters that let you specify a range of agent IDs.

The Zendesk Chat API returns data in JSON format. For example, the result of a call to retrieve agents might look like this:

[
  {
    "id" : 5,
    "first_name" : "John",
    "last_name" : "Doe",
    "display_name" : "Johnny",
    "create_date" : "2017-09-30T08:25:09Z",
    "email" : "johndoe@gmail.com",
    "roles" : {
      "owner": false,
      "administrator": false
    },
    "role_id": 3,
    "enabled" : 1,
    "departments" : []
  },
  {
    "id" : 8,
    "first_name" : "Kevin",
    "last_name" : "Doe",
    ...
  }
]

If you don't already have a data structure in which to store the data you retrieve, you'll have to create a schema for your data tables. Then, for each value in the response, you'll need to identify a predefined datatype (INTEGER, DATETIME, etc.) and build a table that can receive them. Zendesk Chat documentation should tell you what fields are provided by each endpoint, along with their corresponding datatypes.

Complicating things is the fact that the records retrieved from the source may not always be "flat" – some of the objects may actually be lists. This means you'll likely have to create additional tables to capture the unpredictable cardinality in each record.

You must replicate data from your SaaS applications to a data warehouse before you can report on it using Superset. Superset can connect to almost 30 databases and data warehouses. Once you choose a data source you want to connect to, you must specify a host name and port, database name, and username and password to get access to the data. You then specify the database schema or tables you want to work with.

At this point you've coded up a script or written a program to get the data you want and successfully moved it into your data warehouse. But how will you load new or updated data? It's not a good idea to replicate all of your data each time you have updated records. That process would be painfully slow and resource-intensive.

Instead, identify key fields that your script can use to bookmark its progression through the data and use to pick up where it left off as it looks for updated data. Auto-incrementing fields such as updated_at or created_at work best for this. When you've built in this functionality, you can set up your script as a cron job or continuous loop to get new data as it appears in Zendesk Chat.

And remember, as with any code, once you write it, you have to maintain it. If Zendesk modifies its API, or the API sends a field with a datatype your code doesn't recognize, you may have to modify the script. If your users want slightly different information, you definitely will have to.