Skip to main content

Python Guide: Loading Slack Data to AWS S3 with 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.

Welcome to our technical documentation on how to utilize the open-source Python library, dlt, for loading data from Slack to AWS S3. Slack is a business-oriented messaging app that provides users with easy access to necessary information. With dlt, you can efficiently extract this data and store it on AWS S3, a filesystem destination that facilitates the creation of datalakes. AWS S3 supports various data formats, including JSONL, Parquet, and CSV. For additional information on Slack, please visit https://slack.com. This guide will provide you with step-by-step instructions on how to leverage dlt for your data migration needs.

dlt Key Features​

  • Initialise the dlt project: The dlt project can be easily initialised with a command such as dlt init chess filesystem. This command will initialise your pipeline with chess as the source and the AWS S3 filesystem as the destination. More information can be found here.

  • Filesystem and bucket storage: Filesystem destination stores data in remote file systems and bucket storages like S3, Google Storage or Azure Blob Storage. It uses fsspec to abstract file operations. More details can be found here.

  • Governance support: dlt pipelines offer robust governance support through three key mechanisms: pipeline metadata utilization, schema enforcement and curation, and schema change alerts. More details can be found here.

  • Advanced usage: dlt provides advanced options such as deploying from a branch of a repo, or deploying from another repo. More information can be found here.

  • Setup bucket storage and credentials: dlt provides detailed guides to set up bucket storage and credentials for different platforms such as AWS S3. More information can be found 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 AWS S3:

pip install "dlt[filesystem]"

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

# create a new directory
mkdir slack_pipeline
cd slack_pipeline
# initialize a new pipeline with your source and destination
dlt init slack filesystem
# 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[filesystem]>=0.3.12

You now have the following folder structure in your project:

slack_pipeline/
├── .dlt/
│   ├── config.toml          # configs for your pipeline
│   └── secrets.toml         # secrets for your pipeline
├── slack/                   # folder with source specific files
│   └── ...
├── slack_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.slack]
access_token = "access_token" # please set me up!

[destination.filesystem]
dataset_name = "dataset_name" # please set me up!
bucket_url = "bucket_url" # please set me up!

[destination.filesystem.credentials]
aws_access_key_id = "aws_access_key_id" # please set me up!
aws_secret_access_key = "aws_secret_access_key" # 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 Slack source in our docs.
  • Read more about setting up the AWS S3 destination in our docs.

By default, the filesystem destination will store your files as JSONL. You can tell your pipeline to choose a different format with the loader_file_format property that you can set directly on the pipeline or via your config.toml. Available values are jsonl, parquet and csv:

[pipeline] # in ./dlt/config.toml
loader_file_format="parquet"

3. Running your pipeline for the first time​

The dlt cli has also created a main pipeline script for you at slack_pipeline.py, as well as a folder slack 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:


"""Pipeline to load slack into duckdb."""

from typing import List

import dlt
from pendulum import datetime
from slack import slack_source


def load_all_resources(replies: bool = False) -> None:
    """Load all resources from slack without any selection of channels."""

    pipeline = dlt.pipeline(
        pipeline_name="slack", destination='filesystem', dataset_name="slack_data"
    )

    source = slack_source(
        page_size=1000,
        start_date=datetime(2023, 9, 1),
        end_date=datetime(2023, 9, 8),
        replies=replies,
    )

    # Uncomment the following line to load only the access_logs resource. It is not selected
    # by default because it is a resource just available on paid accounts.
    # source.access_logs.selected = True

    load_info = pipeline.run(
        source,
    )
    print(load_info)


def select_resource(selected_channels: List[str]) -> None:
    """Execute a pipeline that will load the given Slack list of channels with the selected
    channels incrementally beginning at the given start date."""

    pipeline = dlt.pipeline(
        pipeline_name="slack", destination='filesystem', dataset_name="slack_data"
    )

    source = slack_source(
        page_size=20,
        selected_channels=selected_channels,
        start_date=datetime(2023, 9, 1),
        end_date=datetime(2023, 9, 8),
    ).with_resources("channels", "1-announcements", "dlt-github-ci")

    load_info = pipeline.run(
        source,
    )
    print(load_info)


def get_users() -> None:
    """Execute a pipeline that will load Slack users list."""

    pipeline = dlt.pipeline(
        pipeline_name="slack", destination='filesystem', dataset_name="slack_data"
    )

    source = slack_source(
        page_size=20,
    ).with_resources("users")

    load_info = pipeline.run(
        source,
    )
    print(load_info)


if __name__ == "__main__":
    # Add your desired resources to the list...
    # resources = ["access_logs", "conversations", "conversations_history"]

    # load_all_resources()

    # load all resources with replies
    # load_all_resources(replies=True)

    # select_resource(selected_channels=["dlt-github-ci"])
    # select_resource(selected_channels=["1-announcements", "dlt-github-ci"])

    get_users()

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

python slack_pipeline.py

4. Inspecting your load result​

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

dlt pipeline slack info

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

# install streamlit
pip install streamlit
# run the streamlit app for your pipeline with the dlt cli:
dlt pipeline slack 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: Learn how to automate your pipeline deployments using GitHub Actions.
  • Deploy with Airflow and Google Composer: Follow this guide to deploy your pipeline with Airflow and Google Composer.
  • Deploy with Google Cloud Functions: Find out how to use Google Cloud Functions for deploying your pipeline.
  • Explore other deployment options: Check out additional methods and detailed guides for deploying your pipeline here.

The running in production section will teach you about:​

  • How to Monitor your pipeline: Learn how to effectively monitor your dlt pipeline in production to ensure smooth and reliable data processing. How to Monitor your pipeline
  • Set up alerts: Set up alerts to stay informed about the status and health of your dlt pipeline in production. Set up alerts
  • Set up tracing: Implement tracing to track the execution and performance of your dlt pipeline, enabling easier debugging and optimization. And set up tracing

Additional pipeline guides​

This demo works on codespaces. Codespaces is a development environment available for free to anyone with a Github account. You'll be asked to fork the demo repository and from there the README guides you with further steps.
The demo uses the Continue VSCode extension.

Off to codespaces!

DHelp

Ask a question

Welcome to "Codex Central", your next-gen help center, driven by OpenAI's GPT-4 model. It's more than just a forum or a FAQ hub – it's a dynamic knowledge base where coders can find AI-assisted solutions to their pressing problems. With GPT-4's powerful comprehension and predictive abilities, Codex Central provides instantaneous issue resolution, insightful debugging, and personalized guidance. Get your code running smoothly with the unparalleled support at Codex Central - coding help reimagined with AI prowess.