Enable business reporting from your Databricks data
Turn your data warehouse into a real reporting library. Connected Data Marts, ready for Slack.
DatabricksConnected
SlackDaily 09:00Someone screenshots a Databricks query into Slack every week, and nobody can check how the number was made.
Paste this into your AI assistant. It sets up a Data Mart on your Databricks tables and schedules it to a Slack channel daily, weekly or on a condition, with every number calculated in SQL before it is explained.
The prompt
Read https://www.owox.com/ai-agent-setup.md and follow it to set up OWOX Data Marts for me, starting from /connectors/databricks-insights-to-slack.md. The task: post a Slack message to our revenue channel whenever yesterday's revenue in our Databricks tables falls more than 10% below the 7-day average, with the report and a short explanation. Tag the links you give me with utm_campaign=ai-task and utm_term=data-foundation. Use what you know about my context and goals
Start from your Databricks data
Pick the Databricks catalog and schema that hold the data your Slack reports are built on.
- Nothing to move or copy: your Delta tables stay in Databricks.
DatabricksYour data warehouseCatalogmainSchemaBuild a reporting library in Databricks
Each Data Mart is a ready report over your Databricks tables, described by AI, and joins to other Data Marts through the model.
- Business users browse reports, not tables.
Send Databricks reports to Slack
Schedule a Data Mart to a Slack channel daily, weekly or on a condition. The message carries the report and a short analysis under it.
- Reports reach the channel where decisions happen.
SlackScheduledWeekly paid media reportcostInUsdclicksimpressionsAnalysisWhat stands out: cost per acquisition differs by platform.Look at ROAS next to spend before moving budget.Check the platform with the weakest ROAS first.Keep Slack connected to the same data
Ask in Claude, export to a sheet, share with the boss.
- One source, every tool.
ClaudeAsk in chat
Google SheetsExport to a sheet
- 0.43.0Compare LinkedIn Ads results across markets: spend by country, region, and county
- 0.43.0The Sheet link of a Google Sheets source opens the imported tab, not the first one
- 0.43.0Connect a Google Sheets plan with one Google sign-in
- 0.41.0Rotating a warehouse key is one change: Storages share reusable Credentials
- 0.41.0Dates from Google Sheets arrive as dates, not text
Why OWOX for Databricks and Slack
Slack gets reports built on governed Data Marts on Databricks, with the numbers calculated in SQL first.
- You own the data. Your data lives in your own Databricks lakehouse; each message is built from a governed Data Mart on it.
- Defined once in SQL. Analysts define metrics on your Delta tables once; every Data Mart and every destination reuses them.
- Decisions happen in Slack. Insights arrive in the channel where the team already decides, not in a dashboard nobody opens.
- SQL first, AI second. Every insight starts with a number calculated in SQL, then narrated in plain language.
- On your schedule. Daily, weekly or conditional delivery to a Slack channel.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.