Send Open Holidays reports to Slack
Open Holidays by date, name and regional scope, once a week. Open Holidays goes into your data warehouse first, is linked there by SQL keys, and only then reaches Slack. The channel gets the answer, not a copy of the source.
Open HolidaysConnectedPublic Holidays
SlackDateIdNameDaily 09:00The Slack channel worries about a slow Tuesday that a public holiday already explains.
Paste this into your AI assistant. It joins Open Holidays to daily orders and sessions in your data warehouse and sends a weekly Slack message that marks each holiday beside the numbers.
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/open-holidays-insights-to-slack.md. The task: send a Monday Slack message with last week's daily orders and sessions and the coming week's holidays from Open Holidays, with holiday days marked by name and regional scope. 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
Open Holidays Endpoints
1 Open Holidays endpoints you can import. Each lands in its own table in your data warehouse.
Why Open Holidays does not post straight to Slack
Open Holidays lists public and school holidays by country, and a message from it is a calendar. A drop in orders or sessions is explained only when that calendar sits beside your daily numbers, which happens in the data warehouse. A Slack channel reads fast, so a number posted there is quoted quickly. Whoever posts it needs to be sure of its definition. The join belongs in a warehouse first.
- Open Holidays names the date of a holiday, not what it did to your sales
- Slack channels are quoted in meetings, so every figure needs one definition
- The data analyst links the sources by SQL keys and controls what the message says
Open HolidaysHolidays by dateSlack
Data warehouseJoined by idStep 1: Load Open Holidays into your data warehouse first
Create a Data Mart with Open Holidays as the source and choose where the data lands. It works with any popular data warehouse.
- One endpoint, Public Holidays, with the date, name, type and regional scope of each holiday
- Set one country ISO code and a language per Data Mart
- Open the Open Holidays connector for your data warehouse below
Open Holida…Data MartGoogle BigQuery
AWS Athena
Snowflake
AWS Redshift
Databricksopen_holidays.public_holidaysStep 2: Link Open Holidays to sessions and orders
In your data warehouse the model joins holidays to daily orders and sessions by date, so a quiet day has a reason next to it. Pick an industry to see the shape of its model.
- Each holiday joins to the sales of its own date
- Sessions and store traffic join by date
- Measures such as orders_total are defined once
Open HolidaysPublic HolidaysStep 3: Send Open Holidays reports to Slack
Create a Slack destination in OWOX with the email address of the channel that should get the report, then add a report to the published Data Mart. The message is Markdown, and Preview shows how it looks in Slack.
- Slack gives every channel an email address, and OWOX posts to it
- Type / in the message to add the Public Holidays table with date, name, type, regionalScope
- Create & Run sends the first report at once
SlackWeeklyWeekly holidays reportdatenametypenationwideStep 4: Add a short analysis under the Open Holidays report
Write two or three lines under the table in the same Markdown message. Add a trigger on the Triggers tab, for example every Monday morning, and the channel gets a fresh run each week.
- The lines read name and type from the report, with no figure from outside it
- The table is filled from a new run of the Data Mart before every send
- A report with a send condition posts only when the result is not empty
SlackWeekly holidays reportdatenametypenationwideAnalysisname and date tell which days the week may run quietnationwide separates holidays everyone has from local onestype tells public holidays from school onesStep 5: Reuse Open Holidays inside OWOX MCP
The same Data Mart works in OWOX MCP, your assistant for data. Request any report, chat with your data, then get the report in Google Sheets or Excel in one click.
- Ask in plain words; the answer comes from your data warehouse
- Define the numbers once and every report reads them
Google SheetsOpen
ExcelOpen
- 0.39.0Reload a year of history in one backfill, not twelve
- 0.37.0Clearer connector errors, and custom connectors that handle more APIs
- 0.36.0Start a connector run without expanding the Input Source card
- 0.35.0Resume an interrupted manual backfill from the last fully loaded date
- 0.35.0Limit manual backfill to 31 days per run
Why OWOX for Open Holidays in Slack
A Slack bot or a script pulling from the Open Holidays source posts numbers as they are. OWOX posts answers from your data warehouse, in the channel your team already uses.
- The calendar behind a dip. Slack lists the holidays that may explain a quiet day, before anyone asks.
- You own the data. Open Holidays lands in your own data warehouse, in tables you control, before anything reaches Slack.
- Slack stays simple. Paste the channel email address once; no Slack app to build and no token to renew.
- Posts only when it matters. Set a report to send only when the result is not empty, so the channel stays quiet on a quiet week.
- Maintained for you. When the source changes its API, the connector is updated, not your Slack setup.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.