Weekly

Know when teammates have public holidays

Each week your team sees which colleagues have a public holiday coming up, based on the countries in your Notion team directory.

Runs: Weekly
Apps: Notion, Slack
AI: Not needed
Access: Notion read; Slack chat:write

Send this to your assistant

Create a ClickRuntime automation: every Monday, check the countries in my Team database in Notion and post any public holidays in the next two weeks to #team, with who's affected.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A team in London, Lisbon and Bangalore has different public holidays, and nobody keeps track of all of them. A deadline gets set for the day half the team is off, a customer demo lands on a Portuguese national holiday, or a deploy is scheduled when the one engineer who knows the system is away. Checking each country's calendar by hand every week is the kind of task that is always skipped.

Each week ClickRuntime reads your Notion team database to find each teammate's country, fetches the coming public holidays for those countries from the Nager.Date service, and posts a list to Slack of who is off in the next week and why. No holiday calendar needs to be maintained by hand.

Distributed teams, agencies with clients in several countries and project managers who plan across regions use it most.

What you get out of it

Planning accounts for who is away
A manager sees on Monday that two engineers are off on Thursday. The release is moved, instead of being discovered at the last minute. The release is moved on Monday, not discovered on Wednesday by an empty chat room and a missing engineer.
Customer commitments avoid local holidays
When a demo or delivery lands on a holiday in the customer's or the team's country, it is flagged beforehand. Dates can be adjusted before they are promised. Dates can then be adjusted before they are promised to anyone outside the team in writing.
Colleagues understand each other's calendars
A short note that a teammate is off for a national holiday builds awareness across countries. People stop sending requests that will sit untouched for a day. People stop sending requests that will sit untouched for a day because the recipient is off.
No manual calendar maintenance
The list is generated from your team database and a public holiday source. When someone joins from a new country, adding one property is enough. When someone joins from a new country, adding one property to their row is all that is needed.
Fewer scheduling mistakes in meetings
Recurring meetings and on-call rotations can be planned around known days off. Coverage gaps are filled before the holiday, not on it. Coverage gaps are filled before the holiday starts instead of in the middle of it.

How it works

What happens, step by step

Every week, ClickRuntime reads your Notion team directory to see which country each colleague is in.
It looks up the public holidays in each of those countries for the next two weeks.
A list appears in your #team Slack channel showing each holiday, its date and which colleagues it affects.

Before it runs live

Connect Notion and share the database you want it to use
Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)

What you get

RunsWeekly

Know when teammates have public holidaystoday, 9:00Succeeded

Slack · #team🏖 Public holidays in the next two weeks • 2026-10-26 October Bank Holiday (IE): Aoife, Ciarán

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Google Sheets
Combine it with other Notion and Slack steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

team_holiday_alerts_from_notion.pyexample

from collections import defaultdict
from datetime import date, timedelta
from clickruntime import on_trigger, credentials, http, notify

DATABASE_ID = "your-team-database-id"

@on_trigger
def run(event):
    team = http.post(f"https://api.notion.com/v1/databases/{DATABASE_ID}/query", json={},
                     headers={"Authorization": f"Bearer {credentials.secret('NOTION_TOKEN')}",
                              "Notion-Version": "2022-06-28"}).json()["results"]
    people = defaultdict(list)  # country code -> names
    for p in team:
        name = "".join(t["plain_text"] for t in p["properties"]["Name"]["title"])
        country = (p["properties"]["Country"]["select"] or {}).get("name")
        if country:
            people[country].append(name)
    today, end = date.today(), date.today() + timedelta(days=14)
    lines = []
    for code, names in people.items():
        for year in {today.year, end.year}:
            for h in http.get(f"https://date.nager.at/api/v3/PublicHolidays/{year}/{code}").json():
                if today.isoformat() <= h["date"] <= end.isoformat() and h.get("global", True):
                    lines.append(f"• {h['date']} {h['localName']} ({code}): {', '.join(names)}")
    if lines:
        notify.slack("🏖 Public holidays in the next two weeks\n" + "\n".join(sorted(lines)), channel="#team")
    return {"holidays": len(lines)}

FAQ

Common questions

Where do the holiday dates come from?

From the Nager.Date public holiday API, which covers more than 100 countries. The dates are fetched fresh each week, so they stay correct without anyone updating a spreadsheet. Results are cached for the week so that the run is fast and reliable.

How does it know where each person is?

From a Country property in your Notion team database, for example using ISO country codes such as GB or PT. Add or update the property when a person moves or joins. Without a country, a person is skipped.

Does it include regional holidays?

It reports national public holidays. Regional or state holidays vary within countries and are not part of the data source, so you can add them to the Notion database as extra entries if they matter to you.

What permissions does it need?

Notion read; Slack chat:write. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (weekly). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Weekdays at 9:00