Automate HiBob

Share the people updates from HiBob that your company needs to know. Slack welcomes new joiners on their first day, you get an email when someone leaves, and each morning the team sees who's out. Describe what you want to your AI assistant, check what it will do, and it keeps running.

Add to ChatGPT Add to Claude

Works inChatGPT Claude Claude Code Cursor Codex VS Code Gemini CLI Zed opencode Any MCP client

Try asking

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.

Ideas

What you can automate in HiBob

A welcome for each joiner, a heads-up when someone leaves, and a morning post with who's away today. These are ready-made starting points. Anything else you can describe works too.

The moment it happens

Welcome new joiners in Slack

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

See how it works

The moment it happens

Get an email when someone leaves

You hear as soon as an employee is marked as leaving in HiBob, so access and equipment can be sorted.

See how it works

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.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with HiBob, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any HiBob automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what HiBob should do in your own words, with your conditions, other apps or an AI step, and 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.

For example, ask your assistant

Every Monday, list HiBob employees with work anniversaries and birthdays this week and draft a short message for each with AI.

Every morning, post new joiners and people out of office today from HiBob to our Slack channel.

When someone leaves according to HiBob, create an offboarding checklist in Asana, add their last day to Google Calendar, and email IT through Gmail.

Beyond chat

Have HiBob work when you're not in the chat

Connecting HiBob to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Instant
Welcome new joiners in Slack
The moment it happens
On a schedule
Post who's out today to Slack
On a schedule
Instant
Get an email when someone leaves
The moment it happens

Setup

Connect HiBob

HiBob connects through a service user that an admin creates in your HiBob account. A service user has no access until you add it to a permission group, so you decide exactly what it can read.

HiBob

HR / HRIS

Sign in to HiBob as an admin and open Settings, then Integrations, then Service Users.
Add a service user and copy its ID and token straight away; HiBob only shows the token once.
Add the service user to a dedicated permission group that can read the data the automation needs, such as people and time off.
In the ClickRuntime dashboard, open Connections & secrets and save the service user ID and token as secrets for HiBob.

Good to know

HiBob limits that affect automations

A new service user can't see anything. If it isn't in a permission group with the right access, automations get empty results rather than an error.
The service user token is shown only once, so store it before closing the dialog. If you lose it, create a new one.
Joiner and leaver alerts rely on HiBob webhooks, which you set up in HiBob's settings.

FAQ

Questions about automating HiBob

What can ClickRuntime see in HiBob?

Only what the service user's permission group allows. If the group can read people and time off, that's all the automations can use. They don't change any HiBob data.

Why does my HiBob automation return nothing?

Most often the service user isn't in a permission group yet, or the group lacks the right fields. Add it to a group with read access and run it again.

Can I use an older HiBob API token?

No. HiBob retired its legacy API tokens, so create a service user instead.

Are joiners and leavers announced straight away?

Yes, once you add a webhook in HiBob's settings with the link ClickRuntime gives you. The who's-out post runs on a schedule, such as 9am on weekdays.

Do I need AI for HiBob automations?

No. These run without AI. If you want something like a written welcome message, it uses the AI that comes with every ClickRuntime plan, with no AI key of your own.

Is this a HiBob connector for ChatGPT or Claude?

Not for chatting with HiBob data. A chat connector lets your assistant read and change HiBob while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each HiBob event.

Keep exploring