Loading Data from pipedrive to motherduck using Python and dlt Library

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 Violetta.

This page provides technical documentation about using the open-source Python library, dlt, to load data from Pipedrive into MotherDuck. Pipedrive is a business-oriented CRM tool that helps manage leads, deals, and sales processes. On the other hand, MotherDuck is an in-process analytical database with a rich SQL dialect and deep client API integrations. The dlt library serves as a bridge between these two platforms, streamlining the data transfer process. For more details about Pipedrive, please visit https://pipedrive.com.

dlt Key Features

• Pipedrive API Integration: dlt provides a verified source for the Pipedrive API, allowing businesses to manage leads, track communication, and automate sales processes. Find out more here.
• MotherDuck Destination: dlt supports MotherDuck as a destination, providing functionalities such as dbt support, data loading, and syncing of dlt state. Learn more here.
• Governance Support: dlt offers robust governance support through pipeline metadata utilization, schema enforcement and curation, and schema change alerts, contributing to better data management practices. Discover more here.
• Detailed Tutorial: A comprehensive tutorial is provided to guide users in building a data pipeline that loads data from the GitHub API into DuckDB, teaching how to use some of the most important features of dlt. Check out the tutorial here.
• DuckDB Destination: dlt supports DuckDB as a destination, offering functionalities like data loading, names normalization, and support for different file formats. Learn more here.

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 MotherDuck:

pip install "dlt[motherduck]"

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 Pipedrive to MotherDuck. You can run the following commands to create a starting point for loading data from Pipedrive to MotherDuck:

# create a new directory
mkdir pipedrive_pipeline
cd pipedrive_pipeline
# initialize a new pipeline with your source and destination
dlt init pipedrive motherduck
# 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[motherduck]>=0.3.5

You now have the following folder structure in your project:

pipedrive_pipeline/
├── .dlt/
│   ├── config.toml          # configs for your pipeline
│   └── secrets.toml         # secrets for your pipeline
├── pipedrive/                   # folder with source specific files
│   └── ...
├── pipedrive_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. The automatically created version of these files look like this:

generated 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

generated secrets.toml

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

[sources.pipedrive]
pipedrive_api_key = "pipedrive_api_key" # please set me up!

[destination.motherduck.credentials]
database = "database" # please set me up!
password = "password" # please set me up!

2.1. Adjust the generated code to your usecase

Further help setting up your source and destinations

• Read more about setting up the Pipedrive source in our docs.
• Read more about setting up the MotherDuck destination in our docs.

3. Running your pipeline for the first time

The dlt cli has also created a main pipeline script for you at pipedrive_pipeline.py, as well as a folder pipedrive 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 dlt
from pipedrive import pipedrive_source


def load_pipedrive() -> None:
    """Constructs a pipeline that will load all pipedrive data"""
    # configure the pipeline with your destination details
    pipeline = dlt.pipeline(
        pipeline_name="pipedrive", destination='motherduck', dataset_name="pipedrive_data"
    )
    load_info = pipeline.run(pipedrive_source())
    print(load_info)


def load_selected_data() -> None:
    """Shows how to load just selected tables using `with_resources`"""
    pipeline = dlt.pipeline(
        pipeline_name="pipedrive", destination='motherduck', dataset_name="pipedrive_data"
    )
    # Use with_resources to select which entities to load
    # Note: `custom_fields_mapping` must be included to translate custom field hashes to corresponding names
    load_info = pipeline.run(
        pipedrive_source().with_resources(
            "products", "deals", "deals_participants", "custom_fields_mapping"
        )
    )
    print(load_info)
    # just to show how to access resources within source
    pipedrive_data = pipedrive_source()
    # print source info
    print(pipedrive_data)
    print()
    # list resource names
    print(pipedrive_data.resources.keys())
    print()
    # print `persons` resource info
    print(pipedrive_data.resources["persons"])
    print()
    # alternatively
    print(pipedrive_data.persons)


def load_from_start_date() -> None:
    """Example to incrementally load activities limited to items updated after a given date"""
    pipeline = dlt.pipeline(
        pipeline_name="pipedrive", destination='motherduck', dataset_name="pipedrive_data"
    )

    # First source configure to load everything except activities from the beginning
    source = pipedrive_source()
    source.resources["activities"].selected = False

    # Another source configured to activities starting at the given date (custom_fields_mapping is included to translate custom field hashes to names)
    activities_source = pipedrive_source(
        since_timestamp="2023-03-01 00:00:00Z"
    ).with_resources("activities", "custom_fields_mapping")

    # Run the pipeline with both sources
    load_info = pipeline.run([source, activities_source])
    print(load_info)


if __name__ == "__main__":
    # run our main example
    # load_pipedrive()
    # load selected tables and display resource info
    # load_selected_data()
    # load activities updated since given date
    load_from_start_date()

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

python pipedrive_pipeline.py

4. Inspecting your load result

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

dlt pipeline pipedrive info

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

# install streamlit
pip install streamlit
# run the streamlit app for your pipeline with the dlt cli:
dlt pipeline pipedrive 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 deployed using Github Actions. This allows you to automate your workflows and deploy your pipeline on a schedule, or manually.
• Deploy with Airflow: You can also deploy dlt using Airflow. This is especially useful if you are using Google Composer, a managed Airflow environment provided by Google.
• Deploy with Google Cloud Functions: dlt can be deployed using Google Cloud Functions. This allows you to run your pipeline in response to events in the cloud.
• Other Deployment Options: There are also other ways to deploy dlt. You can find more information on these in the deployment documentation.

The running in production section will teach you about:

• Monitor your pipeline: dlt provides comprehensive tools for monitoring your data pipeline. From load information to schema updates, you can track all aspects of your pipeline's operation. Learn more from the Monitoring guide.
• Set up alerts: Stay aware of your pipeline's status and any potential issues. dlt allows you to set up alerts that notify you of any changes or problems that may arise during the pipeline's operation. Check out the Alerting guide for more information.
• Enable tracing: Tracing is a powerful feature that enables you to track the execution of your pipeline, providing valuable insights into its performance and operation. Learn how to set it up in the Tracing guide.

Available Sources and Resources

For this verified source the following sources and resources are available

Source pipedrive

Pipedrive source provides comprehensive data on sales activities, customer interactions, deals, and user information.

Resource Name	Write Disposition	Description
activities	merge	Refers to scheduled events or tasks associated with deals, contacts, or organizations
custom_fields_mapping	replace	Mapping for custom fields in Pipedrive
deals	merge	Potential sale or transaction that you can track through various stages
deals_flow	merge	Represents the flow of deals in Pipedrive
deals_participants	merge	Represents the participants of deals in Pipedrive
leads	merge	Prospective customers or individuals that have shown interest in a company's products or services
organizations	merge	Company or entity with which you have potential or existing business dealings
persons	merge	Individual contact or lead with whom sales deals can be associated
products	merge	Goods or services that a company sells, which can be associated with deals
users	merge	Individual with a unique login credential who can access and use the platform

Additional pipeline guides

• Load data from Microsoft SQL Server to Supabase in python with dlt
• Load data from Klaviyo to AWS S3 in python with dlt
• Load data from Box Platform API to Snowflake in python with dlt
• Load data from Spotify to Azure Cosmos DB in python with dlt
• Load data from The Local Filesystem to Neon Serverless Postgres in python with dlt
• Load data from Google Sheets to Snowflake in python with dlt
• Load data from Qualtrics to Neon Serverless Postgres in python with dlt
• Load data from Star Trek to PostgreSQL in python with dlt
• Load data from Apple App-Store Connect to Azure Cosmos DB in python with dlt
• Load data from Box Platform API to Snowflake in python with dlt