The moment it happens

Welcome new joiners in Slack

When someone joins in HiBob, the company sees their name, role and team in Slack.

Runs: The moment it happens
Apps: HiBob
AI: Not needed
Access: service user in a group with people read

Send this to your assistant

Create a ClickRuntime automation: when a new employee joins in HiBob, post a welcome to #general in Slack with their name, job title, department and manager.

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 new hire's first week can feel invisible. The laptop arrives, an onboarding doc is shared, and nobody outside the immediate team knows there is a new person. Colleagues in other departments find out by chance, weeks later, when they see an unfamiliar name in a meeting. That makes the person feel less welcome, and in a remote company, where nobody bumps into anyone in the corridor, it can slow integration noticeably.

When HiBob records a new joiner, the person's profile is fetched and a welcome post goes to a Slack channel, with name, role, team and start date, and a photo if one is on the profile. The post appears when the record is created, so the team can say hello before day one.

It is ideal for remote and growing companies that want a warm, consistent way to introduce people.

What you get out of it

New hires feel welcomed
A post full of greetings and emojis on day one is a pleasant first impression. People who feel welcome settle in faster and tend to stay longer. Small gestures like this have a measurable effect on how connected people feel to a company in the first month.
Cross-team introductions happen
Colleagues in other departments learn who has joined and what they do, which makes later collaboration easier and faster to start. Fewer awkward moments of asking who someone is after weeks of working near them.
Managers and buddies are reminded
A visible post prompts the manager and onboarding buddy to schedule that first coffee or call, which is a step that is easy to forget. The announcement acts as a nudge for the manager to schedule one-to-ones and for the buddy to introduce the person.
Consistency across the company
Every joiner gets the same treatment, regardless of which team they are in or how busy the manager is. No hire is skipped because a manager was busy or the team is small and informal, which keeps the experience fair.
Company growth is visible
A feed of new names gives everyone a feel for how the company is growing, and which teams are hiring. That visibility also helps current employees see progress and recognize which areas of the company need support.

How it works

What happens, step by step

When someone joins in HiBob, HiBob tells ClickRuntime straight away.
ClickRuntime looks up their role, team and manager.
A welcome message with those details is posted to your Slack channel.

Before it runs live

Connect HiBob
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Welcome new joiners in Slackjust nowSucceeded

Slack · #general👋 Welcome Ines Duarte! Joining as Data Analyst in Finance, reporting to Mark Ellis.

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

Act only on the items that match your own rules, and skip the rest
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.

new_joiner_announcement.pyexample

from clickruntime import on_event, 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_event
def handle(event):
    payload = event.json or {}
    if payload.get("type") != "employee.joined":
        return {"posted": False}
    p = bob(f"people/{payload['employee']['id']}")
    work = p.get("work", {})
    manager = (work.get("reportsTo") or {}).get("displayName", "")
    notify.slack(f"👋 Welcome {p['displayName']}! Joining as {work.get('title')} in {work.get('department')}"
                 + (f", reporting to {manager}" if manager else "") + ".", channel="#general")
    return {"posted": True}

FAQ

Common questions

What information appears in the post?

The name, role, team and start date taken from the HiBob profile, plus a photo if one exists. You can decide which fields to show, and sensitive details never need to be included. Fewer fields also keep the post short and friendly.

Is it posted before or after the person starts?

When the record is created in HiBob, which is often a week or more before the start date. If you prefer to announce on day one, the post can wait until the start date. Some teams prefer that timing because it feels more personal.

Can I send it to a different channel for each department?

Yes. Routing engineering joiners to one channel and sales joiners to another is a specific change, using the department field. Describe the mapping and approve it before it runs. Only the mapping between department and channel needs to be defined.

What permissions does it need?

service user in a group with people 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 for each event the app sends.

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