dltHub notifies Slack and email. But my org runs on Teams 😩
dltHub ships Slack and email alerts out of the box. My org runs on Teams, so I built the third one myself and wired it into all ~70 pipelines with one decorator shadow.
dltHub ships Slack and email alerts out of the box. My org runs on Teams, so I built the third one myself and wired it into all ~70 pipelines with one decorator shadow.
Re-using shared patterns in a dlt workspace
LinkedIn's Marketing API needs a browser to authorize. Scheduled pipelines don't have browsers. I store the refresh token in Snowflake.
One hour, five manual inputs, and $0.65 of tokens... enough to replace a daily Fivetran sync with a tested dltHub job
A public contact list sounds easy... until 2,110 websites, four languages, changing staff, and source evidence get involved. 😅
Microsoft Planner has no native backup export, so I built a declarative dlt job that writes complete Graph snapshots to Azure Blob. 😎
I gave an agent a dependency graph to make it write notes on my GTM containers
Every opencode session leaves a trail in a local SQLite file. dlt turns it into analytics you actually read.
Exit code 137 is dlt's way of saying "your RAM and I need to talk"
Same migration, opposite bets: rebuild as Streamlit code you own, or as Sigma workbooks behind a parity gate.
Three Iceberg GAs in one week advancing the old tradeoff: open format without babysitting a bucket.
MotherDuck shipped agent-native Python pipelines. The obvious thing to run inside one is dlt.