Resources · Make integration

HiBob Make integrationAutomate HiBob with Make.

Can an event in Bob kick off the rest of your HR admin by itself? The HiBob Make integration gives you 7 modules: 1 instant trigger, 3 actions and 3 searches. This guide is for people ops teams who know Bob well, and it walks you from the connection to a first working scenario.

Try the HiBob integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the HiBob Make integration do for your HR team?

The HiBob Make integration links your Bob account to Make, a no-code tool where you chain apps into a scenario, meaning the automation you build block by block. Each block is a module: a trigger that starts the flow, an action, or a search. HiBob brings 7 of them, so an event in Bob can feed your other tools without anyone copying data by hand.

Employee record, sent where it is needed. Watch All Events reacts to the events you enable in Bob, then Get an Employee pulls the full profile of the person concerned so the next module (a sheet, a chat message, an IT ticket) gets names and details instead of a bare ID.

Onboarding tasks closed from another tool. List Tasks finds the open tasks that match your criteria, and Complete a Task marks one as done. When the work really happens outside Bob, say in an IT checklist, the task in Bob can follow without a manual click.

A history pulled for reporting. List Employee's History returns the work, employment, life-cycle or salary history of a person, and List All Employees returns the staff list, each person as one bundle (one item passed to the next module). Good material for a report in Airtable, as shown on the Airtable Make integration page.

Know the limits before you start. List All Employees only returns what the connected user is allowed to see, category by category. Anything the six ready-made modules skip goes through Make an API Call, with the same connection. And HiBob's module documentation on Make is flagged as AI-generated, so check any detail that matters with HiBob.

Weighing Make against n8n for this job? The n8n vs Make comparison lays out the criteria, and the Make training helps you build faster once you pick Make.

Connect

How do you connect your HiBob account to Make?

  1. 01

    Create a service user in Bob

    Make does not sign in with your personal Bob login. In HiBob, open the configuration menu, go to the Service Users section and create a new service user. Bob then shows an API key and an API token: copy both right away.

  2. 02

    Open the connection window in Make

    In your scenario, add any HiBob module and click Create a connection. A connection is your Bob account linked to Make once, then reused by every HiBob module. If you picked Watch All Events, click Create a webhook first.

  3. 03

    Paste the credentials and save

    Give the connection a clear name in the Connection name field (optional, but handy with several Bob accounts). Paste the key and token you copied from the service user, or follow the on-screen instructions, then save.

First scenario

Build your first HiBob scenario in Make

GoalWhen an event you enabled fires in Bob, Make catches it and fetches the full record of the employee it concerns.

  1. 01

    Create the scenario

    On the Scenarios page of Make, create a new scenario. The editor opens on an empty canvas: click the big + to place the first module, the one that starts everything.

  2. 02

    Add Watch All Events

    Search for HiBob, pick Watch All Events, click Create a webhook, then Create a connection with the service user key and token. This trigger is instant: Bob calls Make as soon as an event happens.

  3. 03

    Enable the events in Bob

    Make only hears what Bob sends. In HiBob, open Settings, then Integrations, then Webhooks, and choose the events that should start your scenario.

  4. 04

    Add Get an Employee

    Click the + on the right of the trigger, pick HiBob again and choose Get an Employee. If the event data carries the employee ID or email, map it into the module (check it in the first test run), reusing the same connection.

  5. 05

    Test with Run once

    Click Run once, then trigger a matching event in Bob. Open the bubble above each module to read the bundles it received and check that the employee record came back complete.

  6. 06

    Switch the scenario on

    Once the test looks right, save and switch the scenario on. From then on, each event Bob sends runs it, and every module run counts as one operation on your Make plan.

Triggers

What starts a HiBob scenario

1 module starts a scenario when something happens in HiBob. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by HiBob as soon as it happens.

HiBob1Watch All Events

Watch All Events

Instant trigger

In Make“Triggers when an event occurs. Events are set in HiBob > Settings > Integrations > Webhooks.”

Watch All Events hands your scenario every event you chose in Bob, the moment it happens, so the rest of your tools learn about a change without anyone forwarding it.

How it fires
instant: the app calls Make through a webhook as soon as it happens, so there is no schedule to set and no waiting between checks.
When to use it
whenever a Bob event should set off work elsewhere, for example alerting IT or updating a staff sheet.
Watch out
the events themselves are picked in HiBob under Settings, Integrations, Webhooks; if none are enabled there, the scenario stays silent.
Modules

What the HiBob modules do

HiBob gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

HiBob1

Complete a Task

Action

In Make“Marks task as completed.”

Complete a Task ticks off a task in Bob for you, so the checklist there matches what was actually done in another tool.

When to use it
an onboarding step finishes outside Bob, such as a laptop handed over, and the matching Bob task should close too.
Watch out
the module needs to know which task to close, so place List Tasks before it to find the right one.
HiBob2

Get an Employee

Action

In Make“Retrieves an employee by their ID or email address.”

Get an Employee brings back one person's profile from Bob, found by ID or email address, ready to map into the next module.

When to use it
a trigger or another app hands you only an email, and you need the rest of the record to write a welcome message or fill a form.
Watch out
it returns a single employee; for the whole company, use List All Employees instead.
HiBob3

Make an API Call

Action

In Make“Performs arbitrary authorized API call.”

Make an API Call lets you reach any endpoint of the HiBob API from your scenario, using the connection you already set up, with no second login.

When to use it
the six ready-made modules do not cover what you need, for instance a data point none of them returns.
Watch out
you build the request yourself, so keep HiBob's API reference open while you fill it in.
HiBob4

List All Employees

Search

In Make“Lists employees of the company. The data is filtered based on the access level of the logged-in user. Only viewable categories are returned.”

List All Employees returns your company's staff, one bundle per person, which is the easy way to feed a directory, a sheet or a headcount report.

When to use it
you need to act on everyone at once, like syncing the whole team into another tool.
Watch out
Bob filters the result by the access level of the connected user and returns only the categories that user can view.
HiBob5

List Employee's History

Search

In Make“Lists employee's history of work, employment, life-cycle status or salary.”

List Employee's History gives you the timeline of one person: work history, employment, life-cycle status or salary, whichever you choose.

When to use it
a report or an audit needs past changes, not just the current profile, for example after a promotion.
Watch out
it is a search, so it can send back zero, one or many bundles; plan the next module for each case.
HiBob6

List Tasks

Search

In Make“Lists tasks based on selected criteria.”

List Tasks pulls the Bob tasks that match the criteria you set, so your scenario knows what is still pending before it acts.

When to use it
just before Complete a Task, or to send a reminder listing the open onboarding tasks of a new hire.
Watch out
an empty result is a normal outcome, not an error; the modules after it then simply receive nothing.
Need help

Need help automating HiBob with Make?

A person reads every message.

FAQ

HiBob and Make: common questions

01Is the HiBob Make integration free?
Yes, on the Make side. HiBob is a standard app, available from the Free plan. That plan allows 2 active scenarios, 15 minutes minimum between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run. You still need an active Bob subscription, which HiBob sells separately.
02What do you need to connect HiBob to Make?
An active Bob account and service user credentials. In HiBob, open the configuration menu, go to Service Users, create a new service user and copy the API key and the API token it displays. In Make, add a HiBob module, click Create a connection, optionally name it, and paste both values. For the Watch All Events trigger, click Create a webhook first, then create the connection. One connection then serves every HiBob module in your scenarios.
03Does the HiBob trigger in Make work in real time?
Yes. Watch All Events is an instant trigger: Bob calls Make through a webhook as soon as an event happens, so the scenario does not wait for a schedule. The condition is that the event is enabled in HiBob under Settings, Integrations, Webhooks. The lightning badge on the module in the editor confirms it is instant. The other six HiBob modules are actions and searches, which run when the scenario reaches them.
04What if the HiBob module you need is missing in Make?
Use Make an API Call. It is part of the HiBob app in Make and can call any endpoint of the HiBob API with the connection you already have, so a gap in the six ready-made modules does not block you. You write the request yourself from HiBob's API documentation. Also keep in mind that Make flags its HiBob module documentation as AI-generated, so confirm important details with HiBob directly.
05Should you use Make or n8n for HiBob?
It depends on your criteria rather than on a winner. On Make, HiBob comes with 7 modules, including an instant trigger, and Make an API Call covers the rest of the API. The Free plan is enough to test a first scenario. n8n often has a node for the same app, so check what it offers for HiBob and compare the two on your own use case, your team's habits and your budget before deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations