Python Data Loading from `zendesk` to `postgresql` with `dlt`

Need help deploying these pipelines, or figuring out how to run them in your data stack?

Join our Slack community or book a call with our support engineer Adrian.

This guide provides a walkthrough on how to utilize dlt, an open-source Python library, to load data from Zendesk to PostgreSQL. Zendesk is a trusted customer service software used by over 200,000 customers, facilitating customer interaction via various channels like text, mobile, phone, email, live chat, and social media. On the other hand, PostgreSQL is a robust, open-source object-relational database system that extends SQL language, offering a safe environment for storing and scaling complex data workloads. Leveraging dlt, we can bridge these two platforms, effectively transferring data from Zendesk to PostgreSQL. For more details on Zendesk, visit https://www.zendesk.de.

`dlt` Key Features

Pipeline Metadata: dlt pipelines leverage metadata to provide governance capabilities. This metadata includes load IDs, which consist of a timestamp and pipeline name. Load IDs enable incremental transformations and data vaulting by tracking data loads and facilitating data lineage and traceability. Read more about data lineage.
Schema Enforcement and Curation: dlt empowers users to enforce and curate schemas, ensuring data consistency and quality. Schemas define the structure of normalized data and guide the processing and loading of data. By adhering to predefined schemas, pipelines maintain data integrity and facilitate standardized data handling practices. Read more about how to adjust a schema.
Schema Evolution Alerts: dlt enables proactive governance by alerting users to schema changes. When modifications occur in the source data’s schema, such as table or column alterations, dlt notifies stakeholders, allowing them to take necessary actions. Read more about schema evolution.
Scaling and Finetuning: dlt offers several mechanisms and configuration options to scale up and finetune pipelines, including running extraction, normalization, and load in parallel, writing sources and resources that run in parallel via thread pools and async execution, and finetuning the memory buffers, intermediary file sizes, and compression options. Read more about performance.
Community Support: dlt is a constantly growing library that supports many features and use cases needed by the community. You can join the Slack community to find recent releases or discuss what you can build with dlt.

Getting started with your pipeline locally

0. Prerequisites

dlt requires Python 3.8 or higher. Additionally, you need to have the pip package manager installed, and we recommend using a virtual environment to manage your dependencies. You can learn more about preparing your computer for dlt in our installation reference.

1. Install dlt

First you need to install the dlt library with the correct extras for PostgreSQL:

pip install "dlt[postgres]"

The dlt cli has a useful command to get you started with any combination of source and destination. For this example, we want to load data from Zendesk to PostgreSQL. You can run the following commands to create a starting point for loading data from Zendesk to PostgreSQL:

# create a new directory
mkdir my-zendesk-pipeline
cd my-zendesk-pipeline
# initialize a new pipeline with your source and destination
dlt init zendesk postgres
# install the required dependencies
pip install -r requirements.txt

The last command will install the required dependencies for your pipeline. The dependencies are listed in the requirements.txt:

dlt[postgres]>=0.3.8

You now have the following folder structure in your project:

my-zendesk-pipeline/
├── .dlt/
│   ├── config.toml          # configs for your pipeline
│   └── secrets.toml         # secrets for your pipeline
├── zendesk/                   # folder with source specific files
│   └── ...
├── zendesk_pipeline.py        # your main pipeline script
├── requirements.txt         # dependencies for your pipeline
└── .gitignore               # ignore files for git (not required)

2. Configuring your source and destination credentials

The dlt cli will have created a .dlt directory in your project folder. This directory contains a config.toml file and a secrets.toml file that you can use to configure your pipeline:

config.toml

# put your configuration values here

[runtime]
log_level="WARNING"  # the system log level of dlt
# use the dlthub_telemetry setting to enable/disable anonymous usage data reporting, see https://dlthub.com/docs/telemetry
dlthub_telemetry = true

secrets.toml

# put your secret values and credentials here. do not share this file and do not push it to github

[sources.zendesk.credentials]
subdomain = "subdomain" # please set me up!
email = "email" # please set me up!
password = "password" # please set me up!

[destination.postgres.credentials]
database = "database" # please set me up!
password = "password" # please set me up!
username = "username" # please set me up!
host = "host" # please set me up!
port = 5432
connect_timeout = 15

Further help setting up your source and destinations

Please consult the detailed setup instructions for the PostgreSQL destination in the dlt destinations documentation.

Likewise you can find the setup instructions for Zendesk source in the dlt verifed sources documentation.

3. Running your pipeline for the first time

The dlt cli has also created a main pipeline script for you at zendesk_pipeline.py, as well as a folder zendesk that contains additional python files for your source. These files are your local copies which you can modify to fit your needs. In some cases you may find that you only need to do small changes to your pipelines or add some configurations, in other cases these files can serve as a working starting point for your code, but will need to be adjusted to do what you need them to do.

The main pipeline script will look something like this:

import time
from typing import Any

import dlt
from dlt.common.time import timedelta
from zendesk import (
    pendulum,
    zendesk_chat,
    zendesk_talk,
    zendesk_support,
    make_date_ranges,
)


def incremental_load_all_default() -> Any:
    """
    Loads all possible tables for Zendesk Support, Chat, Talk
    """
    # FULL PIPELINE RUN
    pipeline = dlt.pipeline(
        pipeline_name="dlt_zendesk_pipeline",
        destination='postgres',
        full_refresh=False,
        dataset_name="sample_zendesk_data3",
    )

    # zendesk support source function
    data_support = zendesk_support(load_all=True)
    # zendesk chat source function
    data_chat = zendesk_chat()
    # zendesk talk source function
    data_talk = zendesk_talk()
    # run pipeline with all 3 sources
    info = pipeline.run(data=[data_support, data_chat, data_talk])
    return info


def load_support_with_pivoting() -> Any:
    """
    Loads Zendesk Support data with pivoting. Simply done by setting the pivot_ticket_fields to true - default option. Loads only the base tables.
    """
    pipeline = dlt.pipeline(
        pipeline_name="zendesk_support_pivoting",
        destination='postgres',
        full_refresh=False,
    )
    data = zendesk_support(load_all=False, pivot_ticket_fields=True)
    info = pipeline.run(data=data)
    return info


def incremental_load_all_start_date() -> Any:
    """
    Implements incremental load when possible to Support, Chat and Talk Endpoints. The default behaviour gets data since the last load time saved in dlt state or
    1st Jan 2000 if there has been no previous loading of the resource. With this setting, the sources will load data since the given data for all incremental endpoints.
    Last load time will still be updated.
    """

    # Choosing starting point for incremental load - optional, the default is the last load time. If no last load time
    # the start time will be the 1st day of the millennium
    # start time needs to be a pendulum datetime object
    start_date = pendulum.DateTime(year=2023, month=1, day=1).in_timezone("UTC")

    pipeline = dlt.pipeline(
        pipeline_name="dlt_zendesk_pipeline",
        destination='postgres',
        full_refresh=False,
        dataset_name="sample_zendesk_data",
    )
    data = zendesk_support(load_all=True, start_date=start_date)
    data_chat = zendesk_chat(start_date=start_date)
    data_talk = zendesk_talk(start_date=start_date)
    info = pipeline.run(data=[data, data_chat, data_talk])
    return info


def incremental_load_with_backloading() -> Any:
    """Backload historic data in ranges. In this method we load all tickets so far created since Jan 1st 2023 but one week at a time
    and then switch to incrementally loading new tickets.
    This can useful to reduce the potiential failure window when loading large amounts of historic data.
    This approach can be used with all incremental Zendesk sources.
    """
    pipeline = dlt.pipeline(
        pipeline_name="dlt_zendesk_pipeline",
        destination='postgres',
        full_refresh=False,
        dataset_name="sample_zendesk_data",
    )

    # Load ranges of dates to load between January 1st 2023 and today
    min_start_date = pendulum.DateTime(year=2023, month=1, day=1).in_timezone("UTC")
    max_end_date = pendulum.today()
    # Generate tuples of date ranges, each with 1 week in between.
    ranges = make_date_ranges(min_start_date, max_end_date, timedelta(weeks=1))

    # Run the pipeline in a loop for each 1 week range
    for start, end in ranges:
        print(f"Loading tickets between {start} and {end}")
        data = zendesk_support(start_date=start, end_date=end).with_resources("tickets")
        info = pipeline.run(data=data)
        print(info)

    # Backloading is done, now we continue loading with incremental state, starting where the backloading left off
    print(f"Loading with incremental state, starting at {end}")
    data = zendesk_support(start_date=end).with_resources("tickets")
    info = pipeline.run(data)
    print(info)


if __name__ == "__main__":
    # simple run where everything is loaded
    start = time.time()
    load_info = incremental_load_all_default()
    end = time.time()
    print(load_info)
    print(f"Time taken: {end-start}")

Provided you have set up your credentials, you can run your pipeline like a regular python script with the following command:

python zendesk_pipeline.py

4. Inspecting your load result

You can now inspect the state of your pipeline with the dlt cli:

dlt pipeline dlt_zendesk_pipeline info

You can also use streamlit to inspect the contents of your PostgreSQL destination for this:

# install streamlit
pip install streamlit
# run the streamlit app for your pipeline with the dlt cli:
dlt pipeline dlt_zendesk_pipeline show

5. Next steps to get your pipeline running in production

One of the beauties of dlt is, that we are just a plain Python library, so you can run your pipeline in any environment that supports Python >= 3.8. We have a couple of helpers and guides in our docs to get you there:

The Deploy section will show you how to deploy your pipeline to

Deploy with Github Actions: dlt can be easily deployed with Github Actions. This CI/CD runner is essentially free and can be scheduled using a cron schedule expression. More details on how to deploy using Github Actions can be found here.
Deploy with Airflow: dlt can also be deployed using Airflow. This Python platform can be used to programmatically author, schedule and monitor workflows. More details on how to deploy using Airflow can be found here.
Deploy with Google Cloud Functions: dlt can be deployed using Google Cloud Functions. This serverless execution environment runs your code upon events, such as HTTP requests. More details on how to deploy using Google Cloud Functions can be found here.
Other Deployment Options: dlt can also be deployed using other methods. More details on these methods can be found here.

The running in production section will teach you about:

Monitor Your Pipeline: dlt provides robust monitoring capabilities, allowing you to keep track of your pipeline's performance and status. Learn more about how to monitor your pipeline here.
Set Up Alerts: Stay informed about any issues or changes in your pipeline by setting up alerts. dlt makes it easy for you to set up alerts to notify you of any errors or disruptions in your pipeline. Learn how to set up alerts here.
Implement Tracing: dlt supports tracing, allowing you to track the execution of your pipeline and identify any bottlenecks or issues. Find out more about setting up tracing here.

Available Sources and Resources

For this verified source the following sources and resources are available

Source `zendesk_chat`

Zendesk Chat source provides detailed chat session data including user information and messages.

Resource Name	Write Disposition	Description
`chats`	`merge`	This resource includes details about the chats in Zendesk. It includes information such as whether the chat has been deleted, the id, message, details about the session (browser, city, country code, country name, end date, id, ip, platform, region, start date, user agent), timestamp, type of chat, whether it is unread, update timestamp, and details about the visitor (email, id, name, notes, phone).

Source `zendesk_support`

The source 'zendesk_support' provides comprehensive data on customer service interactions, including ticket details, user information, and organizational metrics.

Resource Name	Write Disposition	Description
`activities`	`replace`	Activities in Zendesk are logs of all the changes and updates made to tickets.
`automations`	`replace`	Automations in Zendesk are business rules you define that run in the background of your support operations.
`brands`	`replace`	Brands in Zendesk allow you to manage multiple brands in a single account.
`custom_agent_roles`	`replace`	Custom agent roles in Zendesk allow you to customize the access and permissions of your agents.
`dynamic_content`	`replace`	Dynamic content in Zendesk allows you to write one version of an automated response and then translate it into other languages.
`group_memberships`	`replace`	Group memberships in Zendesk define the groups an agent belongs to.
`groups`	`replace`	Groups in Zendesk are used to route tickets to the right people in your organization.
`job_status`	`replace`	Job statuses in Zendesk provide information about the completion status of a job.
`macros`	`replace`	Macros in Zendesk are predefined responses or sets of actions.
`organization_fields`	`replace`	Organization fields in Zendesk are custom fields you can create for organizations.
`organization_memberships`	`replace`	Organization memberships in Zendesk define the organizations a user belongs to.
`organizations`	`replace`	Organizations in Zendesk are groups of your end-users.
`recipient_addresses`	`replace`	Recipient addresses in Zendesk are the email addresses associated with your support address.
`requests`	`replace`	Requests in Zendesk are the tickets that end-users submit.
`satisfaction_ratings`	`replace`	Satisfaction ratings in Zendesk are the ratings that your end-users can give to your support.
`sharing_agreements`	`replace`	Sharing agreements in Zendesk define how tickets are shared with other Zendesk instances.
`skips`	`replace`	Skips in Zendesk are tickets that were skipped in a play queue.
`sla_policies`	`replace`	SLA policies in Zendesk are the service level agreements you define for your tickets.
`suspended_tickets`	`replace`	Suspended tickets in Zendesk are tickets that have been marked as spam or have been suspended for some other reason.
`tags`	`replace`	Tags in Zendesk are keywords or phrases that you can add to tickets.
`targets`	`replace`	Targets in Zendesk are third-party applications or services that you can send notifications to.
`ticket_events`	`append`	Ticket events in Zendesk are the changes and updates made to a ticket.
`ticket_fields`	`replace`	Ticket fields in Zendesk are the fields that a ticket form is composed of.
`ticket_forms`	`replace`	Ticket forms in Zendesk are the different forms you can create for different types of tickets.
`ticket_metric_events`	`append`	Ticket metric events in Zendesk are the metrics associated with a ticket.
`ticket_metrics`	`replace`	Ticket metrics in Zendesk are the metrics associated with a ticket.
`tickets`	`merge`	Tickets in Zendesk are the means by which your end-users request help from your team.
`triggers`	`replace`	Triggers in Zendesk are business rules you define that automatically perform actions based on certain conditions.
`user_fields`	`replace`	User fields in Zendesk are custom fields you can create for users.
`users`	`replace`	Users in Zendesk are anyone who interacts with the Zendesk product.
`views`	`replace`	Views in Zendesk are collections of tickets based on certain criteria.

Source `zendesk_talk`

Zendesk_talk provides data on call activity, agent activity, settings, greetings, and queue status.

Resource Name	Write Disposition	Description
`addresses`	`replace`	This resource contains the addresses associated with Zendesk Talk.
`agents_activity`	`replace`	This resource contains information about the activity of agents in Zendesk Talk.
`calls`	`replace`	This resource contains information about the calls made in Zendesk Talk.
`calls_incremental`	`merge`	This resource contains incremental information about the calls made in Zendesk Talk.
`current_queue_activity`	`replace`	This resource contains information about the current activity in the queue of Zendesk Talk.
`greeting_categories`	`replace`	This resource contains information about the categories of greetings in Zendesk Talk.
`greetings`	`replace`	This resource contains information about the greetings used in Zendesk Talk.
`ivrs`	`replace`	This resource contains information about the Interactive Voice Response (IVR) systems in Zendesk Talk.
`legs_incremental`	`merge`	This resource contains incremental information about the legs (or parts) of calls in Zendesk Talk.
`lines`	`replace`	This resource contains information about the lines used in Zendesk Talk.
`phone_numbers`	`replace`	This resource contains information about the phone numbers associated with Zendesk Talk.
`settings`	`replace`	This resource contains information about the settings configured in Zendesk Talk.

Python Data Loading from `zendesk` to `postgresql` with `dlt`

`dlt` Key Features

Getting started with your pipeline locally

0. Prerequisites

1. Install dlt

2. Configuring your source and destination credentials

config.toml

secrets.toml

3. Running your pipeline for the first time

4. Inspecting your load result

5. Next steps to get your pipeline running in production

The Deploy section will show you how to deploy your pipeline to

The running in production section will teach you about:

Available Sources and Resources

Source `zendesk_chat`

Source `zendesk_support`

Source `zendesk_talk`

Additional pipeline guides

DHelp

Ask a question

Python Data Loading from zendesk to postgresql with dlt

dlt Key Features​

Getting started with your pipeline locally​

0. Prerequisites​

1. Install dlt​

2. Configuring your source and destination credentials​

config.toml​

secrets.toml​

3. Running your pipeline for the first time​

4. Inspecting your load result​

5. Next steps to get your pipeline running in production​

The Deploy section will show you how to deploy your pipeline to​

The running in production section will teach you about:​

Available Sources and Resources​

Source zendesk_chat​

Source zendesk_support​

Source zendesk_talk​

Additional pipeline guides​

DHelp

Ask a question

Python Data Loading from `zendesk` to `postgresql` with `dlt`

`dlt` Key Features

Getting started with your pipeline locally

0. Prerequisites

1. Install dlt

2. Configuring your source and destination credentials

config.toml

secrets.toml

3. Running your pipeline for the first time

4. Inspecting your load result

5. Next steps to get your pipeline running in production

The Deploy section will show you how to deploy your pipeline to

The running in production section will teach you about:

Available Sources and Resources

Source `zendesk_chat`

Source `zendesk_support`

Source `zendesk_talk`

Additional pipeline guides