Send Open Holidays reports to Google Chat
Load Open Holidays into your data warehouse first, link it to the rest of your data with SQL keys, then post the next public holidays where the team plans campaigns and staffing. The message comes from your source of truth, not from an API call that can break.
Open HolidaysConnectedPublic Holidays
Google ChatDateIdNameDaily 09:00The team that plans campaigns finds out about a regional holiday in Google Chat the day it starts.
Paste this into your AI assistant. It keeps Open Holidays calendars in a Data Mart in your data warehouse and posts the upcoming public holidays to the Google Chat space through a webhook, on a schedule.
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-google-chat.md. The task: post next week's public and regional holidays from Open Holidays for our countries to the planning Google Chat space every Friday, by date and country. 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 go straight to Google Chat
Open Holidays lists public holidays by date, not how a holiday moved your sales. A message built straight from the source puts the source's own numbers in the space and does not tie them to the rest of the business reliably, at scale or business-ready, so the join happens in a warehouse first.
- A holiday has a date, a name and a type, with no orders or visits to read it against
- The data analyst links the tables by SQL keys and controls what a message may say
- The space reads one scheduled message instead of several tabs and an export
Open HolidaysHoliday calendarGoogle Chat
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 seven fields, in one table
- Pick a country ISO code and a language for holiday names
- 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 orders and traffic
In your data warehouse the model joins the holiday calendar to sessions and store traffic by date and country code. Pick an industry to see the shape of its model.
- In the Retail model, Open Holidays fills the is_holiday flag on Store Traffic
- Orders and sessions join by SQL keys, not by eye
- The measures, such as conversion_rate, are defined once
Open HolidaysPublic HolidaysStep 3: Send Open Holidays reports to Google Chat
Add an incoming webhook in the Chat space (Apps & integrations, Add webhooks), paste its URL into a Google Chat destination in OWOX, and attach a report of the Open Holidays Data Mart. The message is a Markdown template.
- The message is a card with the subject, the Data Mart name, your text and a link back to the report
- The table carries date, name, nationwide and type
- Tables arrive as monospace blocks, and a long report is split into numbered parts
Google ChatWeeklyWeekly holiday calendardatenamenationwidetypeStep 4: Add a short analysis under the Open Holidays report in Chat
Write the reading under the table in the template, or let an Insight on the same Data Mart write it. Then add a trigger on the Triggers tab: OWOX runs the Data Mart first and checks the sending condition.
- Send always, or only when the result is not empty, so a quiet week stays quiet
- The reading comes from the report's fields and adds no cause the data does not show
- One space can receive several reports, each with its own trigger
Google ChatWeekly holiday calendardatenamenationwidetypeAnalysisUpcoming holiday by date, name and type.A nationwide holiday affects every region; others affect some.Plan campaigns around the dates marked nationwide first.Step 5: Reuse Open Holidays inside OWOX MCP
The Data Mart behind your Chat message also 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
- Change the Open Holidays report once and the next Chat message reads the change
Google SheetsOpen
ExcelOpen
- 0.41.0Reuse one Google Sheets or Google Chat key across Destinations
- 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
Why OWOX for Open Holidays in Google Chat
Hand-built bots and webhook scripts post numbers into a space. OWOX also keeps the data yours, linked and ready to model.
- You own the data. Open Holidays lands in your own data warehouse, in tables you control.
- Dates in the planning thread. The next holiday is posted where campaigns get planned, so nobody schedules a launch on a closed day.
- The webhook stays simple. Paste the space's webhook URL once; it is stored write-only and several destinations can share it.
- Same numbers everywhere. The Open Holidays Data Mart behind the message also feeds your reports and your AI assistant.
- Maintained for you. No bot code to fix when Open Holidays changes its API.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.