On a schedule

Post who's out today to Slack

Each weekday morning the team sees who is on leave, so nobody waits on someone who's away.

Runs: On a schedule
Apps: HiBob
AI: Not needed
Access: time off read

Send this to your assistant

Create a ClickRuntime automation: every weekday at 9am, post who's out today from HiBob to #team in Slack, with each person's name and type of leave.

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

Every team lead has had the experience of booking a meeting, sending a request or waiting for a reply from someone who is on holiday. In a company of 50 or 200 people, nobody knows who is out on a given day unless they open HiBob's calendar. Customers get a quiet response, handoffs are missed, and people ping a colleague for an hour before somebody mentions they are on leave until Thursday. Even a short pause costs time.

Each morning, the list of people who are out today (holiday, sick leave, parental leave and other absences recorded in HiBob) is fetched and posted to Slack. Everyone sees it at the start of the day.

It helps teams of every size, and particularly support, operations and project teams that need cover.

What you get out of it

Fewer wasted requests
People know who is away before they send a question, so they go to the right person straight away instead of waiting. A question sent to the right person at the start saves a day of waiting for a reply that cannot come.
Cover is arranged in time
Team leads see the day's absences at a glance, which makes it easy to check that support, on-call and customer coverage is intact. If three people from support are away, the lead can rebalance the queue before customers feel it.
Meetings are scheduled sensibly
Seeing who is out stops people from booking reviews or workshops on days when key people are away. A glance before sending an invite avoids a reschedule and the awkward email chain that follows.
Fewer awkward pings
Colleagues are not messaged on days off, which respects people's time away and avoids an awkward response. People on leave are left alone, which supports a healthy culture about time off and rest.
Everyone shares the same picture
A single daily post replaces a dozen private conversations and keeps a distributed team informed about availability. That is especially valuable for remote teams spread across time zones, where nobody sees who is actually at a desk.

How it works

What happens, step by step

Every weekday at 9am, ClickRuntime asks HiBob who is out today.
It lists each person with the type of leave and when they are back.
The list is posted to your Slack channel.

Before it runs live

Connect HiBob

What you get

RunsOn a schedule

Post who's out today to Slacktoday, 9:00Succeeded

Slack · #teamOut today: • Ines Duarte: Holiday (until 2026-10-22) • Mark Ellis: Sick (until 2026-10-19)

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 Slack
Combine it with other HiBob 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.

who_s_out_today_hibob.pyexample

from clickruntime import on_trigger, credentials, http, notify

def bob(path):
    resp = http.get(f"https://api.hibob.com/v1/{path}", headers={"Accept": "application/json"},
                    auth=(credentials.secret("HIBOB_SERVICE_USER_ID"), credentials.secret("HIBOB_SERVICE_USER_TOKEN")))
    resp.raise_for_status()
    return resp.json()

@on_trigger
def run(event):
    outs = bob("timeoff/outtoday").get("outs", [])
    lines = [f"• {o['employeeDisplayName']}: {o['policyTypeDisplayName']} (until {o['endDate']})" for o in outs]
    notify.slack("Out today:\n" + "\n".join(lines) if lines else "Everyone's in today.", channel="#team")
    return {"out": len(lines)}

FAQ

Common questions

Does it share why someone is out?

By default only names appear. The type of leave can be included for holiday or sick days if your culture allows it, but personal reasons are best left out. Keep the post to availability. That keeps private matters private.

Does it include half days?

Yes, partial days recorded in HiBob can be listed with the time they are away. Whether to show them is a choice you can make when setting it up, and many teams do. Showing partial days helps colleagues time their requests.

Can it skip weekends?

Yes. Running only on weekdays is a simple setting. For teams that work Sunday to Thursday or other patterns, the days can be set to match. Weekend posts are never sent, which also keeps the channel quiet for people who are off.

What permissions does it need?

time off read. 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 (on a schedule). 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.

The moment it happens