On a schedule
Post who's out today to Slack
Every weekday morning your team sees who is on leave, so nobody waits on a reply that won't come.
- Runs
- On a schedule
- Apps
- BambooHR
- AI
- Not needed
- Access
- read (time off)
Send this to your assistant
Create a ClickRuntime automation: every weekday at 9am, get who's out today from BambooHR and post the names and return dates to #team in Slack.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
By 9 am on any given weekday, a few people are out: a vacation day, a doctor's appointment, a sick day. Colleagues find out the hard way. A designer pings a developer for an urgent review and waits an hour before learning the developer is on leave. A customer is told to expect a call back from someone who is away until Monday. In a team of forty, nobody has the whole picture without opening the HR calendar.
Each morning, ClickRuntime fetches the list of who is out today from BambooHR, formats the names with the dates of absence and posts it to a Slack channel. People can see at a glance who is unavailable before they send a message or plan a meeting.
It is useful for companies where teams depend on one another and nobody has time to check a shared calendar. Larger offices can post a different list for each location.
What you get out of it
Questions go to people who can answer
Knowing who is away prevents messages that sit unread and unanswered. Colleagues find the right backup immediately, and work continues without delay. Colleagues find the right backup immediately and work keeps moving.
Meetings are not scheduled around absent people
A glance at the morning post tells the organizer who cannot attend. Meetings can be moved before invitations go out, saving everyone's time. Meetings move before invitations are sent, saving everybody's time.
Customers get accurate expectations
Support and sales staff can promise realistic callbacks when they know who is out. Fewer promises are made that cannot be kept, which protects relationships. Fewer promises are made that cannot be kept, which protects relationships.
Cover is arranged before problems appear
Managers see absences first thing and can ask someone to pick up urgent tasks. It is easier than discovering a gap at 3 pm. That is easier than discovering a gap at three in the afternoon.
Nobody has to open the HR system
Employees do not need BambooHR access to see who is away. Leave information is shared at the level of names and dates, with no reasons or balances exposed. Employees need no HR login to see this.
How it works
What happens, step by step
Every weekday at 9am, ClickRuntime asks BambooHR who is out today.
It lists each person with the date they are back.
The list is posted to your Slack channel, so everyone knows who won't be replying.
Before it runs live
- Connect BambooHR
What you get
Build your own
Need it to work differently?
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 BambooHR steps into one automation
Under the hood
The code that runs this automation
from datetime import date
from clickruntime import on_trigger, credentials, http, notify
COMPANY = "northwind"
def bamboo(path, **params):
resp = http.get(f"https://api.bamboohr.com/api/gateway.php/{COMPANY}/v1/{path}",
auth=(credentials.secret("BAMBOOHR_API_KEY"), "x"),
headers={"Accept": "application/json"}, params=params)
resp.raise_for_status()
return resp.json()
@on_trigger
def run(event):
today = str(date.today())
out = [e for e in bamboo("time_off/whos_out/", start=today, end=today) if e["type"] == "timeOff"]
if not out:
notify.slack("Everyone's in today.", channel="#team")
else:
lines = [f"• {e['name']}, back after {e['end']}" for e in out]
notify.slack("Out today:\n" + "\n".join(lines), channel="#team")
return {"out": len(out)}FAQ
Common questions
Does it show the reason for the absence?
What happens on a day when nobody is out?
Does it include public holidays?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Get this week's work anniversaries by email
Each Monday you know whose anniversary is coming, in time to say something.
See how it worksGet an email for every new time-off request
You hear about each leave request within 15 minutes, so you can approve it or plan cover.
See how it worksAnnounce new starters and flag leavers
New starters get a welcome post in Slack, and you get an email when someone's employment ends.
See how it worksKeep exploring
Set up “Post who's out today to Slack” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
