Skip to main content

Load Data from Notion to Supabase with dlt in Python

tip

We will be using the dlt PostgreSQL destination to connect to Supabase. You can get the connection string for your Supabase database as described in the Supabase Docs.

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.

Notion is a versatile tool where you can think, write, and plan. It allows you to capture thoughts, manage projects, or even run an entire company, tailored to your preferences. Supabase is an open-source Firebase alternative, offering a Postgres database, Authentication, instant APIs, Edge Functions, Realtime subscriptions, Storage, and Vector embeddings. This documentation will guide you on how to load data from Notion to Supabase using the open-source Python library dlt. For more details about Notion, visit this link.

dlt Key Features

  • Pipeline Metadata: dlt pipelines leverage metadata to provide governance capabilities, including load IDs that enable incremental transformations and data vaulting. Read more
  • Schema Enforcement and Curation: dlt empowers users to enforce and curate schemas, ensuring data consistency and quality by defining the structure of normalized data. Read more
  • Schema Evolution: dlt alerts users to schema changes, allowing them to review and validate modifications, update downstream processes, or perform impact analysis. Read more
  • Scaling and Finetuning: dlt offers mechanisms and configuration options to scale up and finetune pipelines, including running extraction, normalization, and load in parallel. Read more
  • Automated Maintenance: With schema inference, evolution, and alerts, dlt simplifies maintenance, making it easy to handle data pipelines with short declarative code. Read more

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

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

# create a new directory
mkdir notion_pipeline
cd notion_pipeline
# initialize a new pipeline with your source and destination
dlt init notion 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.5

You now have the following folder structure in your project:

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

[destination.postgres]
dataset_name = "dataset_name" # 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

2.1. Adjust the generated code to your usecase

Further help setting up your source and destinations
  • Read more about setting up the Notion source in our docs.
  • Read more about setting up the Supabase 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 notion_pipeline.py, as well as a folder notion 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 notion import notion_databases


def load_databases() -> None:
"""Loads all databases from a Notion workspace which have been shared with
an integration.
"""
pipeline = dlt.pipeline(
pipeline_name="notion",
destination='postgres',
dataset_name="notion_data",
)

data = notion_databases()

info = pipeline.run(data)
print(info)


if __name__ == "__main__":
load_databases()

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

python notion_pipeline.py

4. Inspecting your load result

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

dlt pipeline notion info

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

# install streamlit
pip install streamlit
# run the streamlit app for your pipeline with the dlt cli:
dlt pipeline notion 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 set up and deploy your dlt pipeline using GitHub Actions. This guide provides step-by-step instructions to automate your deployment process. Read more
  • Deploy with Airflow and Google Composer: Follow this guide to deploy your dlt pipeline using Airflow and Google Composer. It includes instructions on setting up your environment and running your pipeline. Read more
  • Deploy with Google Cloud Functions: This walkthrough explains how to deploy your dlt pipeline using Google Cloud Functions. It covers the necessary steps to get your pipeline running serverlessly. Read more
  • Explore Other Deployment Options: Discover various other methods to deploy your dlt pipeline, including different cloud services and CI/CD tools. Read more

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 efficient operations. How to Monitor your pipeline
  • Set up alerts: Set up alerts to get notified about any issues or anomalies in your dlt pipeline, ensuring timely intervention and resolution. Set up alerts
  • Set up tracing: Implement tracing in your dlt pipeline to gain insights into the data flow and performance, helping you pinpoint and troubleshoot issues. 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.