dlt-source-airtable
Currently loads the following data:
| Table | Contains |
|---|---|
users |
Items of the users model that are users |
service_accounts |
Items of the users model that are service accounts |
Why are you not using the dlt-hub/verified-sources airtable 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-sourcesrepository 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 which uses Pydantic models
Usage
Create a .dlt/secrets.toml with your API token:
airtable_token = "pat..."
You can create this token here or as a Service Admin Account (preferred).
The scopes needed are as follows:
enterprise.user:readenterprise.account:read
and then run the default source with optional list references:
from dlt_source_airtable import source as airtable_source
pipeline = dlt.pipeline(
pipeline_name="airtable_pipeline",
destination="duckdb",
dev_mode=True,
)
enterprise_id = "ent..."
airtable_data = airtable_source(enterprise_id)
pipeline.run(airtable_data)
How to get your enterprise ID
Navigate to your admin view and you will see
Account ID: ent...
in the sidebar and/or URL bar of your browser.
Development
This project is using devenv.
Commands:
| Command | What does it do? |
|---|---|
format |
Formats & lints all code |
sample-pipeline-run |
Runs the sample pipeline. |
sample-pipeline-show |
Starts the streamlit-based dlt hub |
Run the sample
AIRTABLE_TOKEN=[pat...] \
sample-pipeline-run
alternatively you can also create a .dlt/secrets.toml
(excluded from git) with the following content:
airtable_token = "pat..."
Metadata
Release files for dlt-source-airtable 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dlt_source_airtable-0.0.1.tar.gz | 64.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dlt_source_airtable-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 70.0 kB
Release files / dlt_source_airtable-0.0.1.tar.gz
| Download URL | dlt_source_airtable-0.0.1.tar.gz |
|---|---|
| Size | 64.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
15ec895ace137719cf7d6c74464af3ef026b8bbece56959c98661728cfafc0d3
|
|
BLAKE2b-256 checksum How to use checksums |
d0012effe5737945a52674c98a958b48dd2b9122f22fcf82149992822f046bb3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2025.
Transparency logRelease files / dlt_source_airtable-0.0.1-py3-none-any.whl
| Download URL | dlt_source_airtable-0.0.1-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dd720c1c7a9aa81fe3f831b7592011b3414b3d576699976d05628a8897037fd6
|
|
BLAKE2b-256 checksum How to use checksums |
b9ff6d8d6c8158ec26d7e86f63042c83256a951c87bb893fca4a26f5207a3180
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2025.
Transparency log