Post Open Holidays reports to Microsoft Teams
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 Microsoft Teams. Colleagues read the answer in Teams, not an export of the source.
Open HolidaysConnectedPublic Holidays
Microsoft TeamsDateIdNameDaily 09:00A quiet sales day gets discussed in Microsoft Teams for an hour before anyone notices it was a public holiday.
Paste this into your AI assistant. It joins Open Holidays to daily orders and sessions in your data warehouse and posts a weekly report to the Microsoft Teams channel with the holiday next to each quiet day.
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-microsoft-teams.md. The task: post last week's daily orders and sessions to our Microsoft Teams channel every Monday, with the Open Holidays holiday name next to any day that fell on one. 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 Microsoft Teams
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 Teams channel is read by people outside the team that built the report, so every number needs to explain itself. The join belongs in a warehouse first.
- Open Holidays names the date of a holiday, not what it did to your sales
- A Teams channel reaches colleagues who never saw the source, so definitions must travel with the figures
- The data analyst links the sources by SQL keys and controls what the message says
Open HolidaysHolidays by dateMicrosoft Tea…
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: Post Open Holidays reports to a Teams channel
Create a Microsoft Teams destination in OWOX with the email address of the channel, taken from the channel menu in Teams, then add a report to the published Data Mart. Write the message in Markdown and check it in Preview.
- Every Teams channel can receive email, and OWOX sends the report to that address
- Type / to place the Public Holidays table: date, name, type, regionalScope and the number of rows you pick
- Create & Run posts the first report straight away
Microsoft TeamsWeeklyUpcoming holidays digestdateregionalScopetemporalScopenameStep 4: Put a short analysis under the Open Holidays table in Teams
Add two or three lines beneath the table in the same message. Pick a send condition on the report, and open the Triggers tab to set the day and time of the run.
- The lines rest on name and type from the table above them
- Figures come from a fresh run of the Data Mart before each message
- Send always, only when empty or only when not empty: chosen per report
Microsoft TeamsUpcoming holidays digestdateregionalScopetemporalScopenameAnalysisCheck regionalScope before assuming a holiday applies to alltemporalScope tells how long a holiday lastsCompare date with last week to spot a quiet day earlyStep 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 it 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 Microsoft Teams
Hand-built flows that read Open Holidays and post to Teams carry the source's numbers only. OWOX posts the answers your data warehouse calculated, to the channel of your choice.
- Plan the week around real dates. Teams shows the holidays of the coming days, by country, in the channel that plans the week.
- You own the data. Open Holidays lands in your own data warehouse, in tables you control, before anything reaches Teams.
- Nothing to build in Teams. The channel email address is all it needs: no custom connector, no flow to maintain on the Microsoft side.
- A message with a condition. Each report has its own send condition, so a Teams channel hears only when there is something to say.
- Maintained for you. When the source changes, the connector is updated; your Teams channel keeps getting the report.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.