description: dlt source for notion.com keywords: [notion API, notion.com]

dlt-source-notion

DLT source for notion.

Currently loads the following data:

<shorthash> refers to the hashed id of an entity. The hash is a 4-bit BLAKE2b hash.

Why are you not using the dlt-hub/verified-sources notion source / Differences

The official verified source has a few drawbacks:

• on usage of the verified source, a copy of the current state of the dlt-hub/verified-sources repository is copied into your project; Once you make changes to it, it effectively becomes a fork, making it hard to update after the fact.
• This makes use of a preexisting client implementation
• And Pydantic types for Notion entities, which makes this implementation a lot more stable

Usage

Create a .dlt/secrets.toml with your API key and email:

notion_token = "ntn_abcd12345"

and then run the default source with optional list references:

from dlt_source_notion import source as notion_source

pipeline = dlt.pipeline(
   pipeline_name="notion_pipeline",
   destination="duckdb",
   dev_mode=True,
)
notion_data = notion_source()
pipeline.run(notion_data)

To load a specific database under a clean, explicit table name instead of the default database_<title>_<shorthash>, pass table_name to DatabaseResource:

from dlt_source_notion import source as notion_source, DatabaseResource

events_db = DatabaseResource(
    database_id="1b83e0058e9244e7b1933cce404e2a98",
    table_name="event_database",
)
notion_data = notion_source(database_resources=[events_db])

Development

This project is using devenv.

Commands:

Run the sample

NOTION_TOKEN=[...] \
  sample-pipeline-run

alternatively you can also create a .dlt/secrets.toml (excluded from git) with the following content:

notion_token = "ntn_abcd12345"