Resources · Zapier integration

Hibob Zapier integrationAutomate Hibob with Zapier.

The Hibob Zapier integration gives you 8 triggers and 1 action, with no search. Every trigger is instant: Hibob tells Zapier about hires, start dates, leave, departures and profile changes as they happen, on any plan, the free one included.

See the 9 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Hibob Zapier integration is for

The Hibob Zapier integration connects bob, Hibob's HR platform for onboarding, pay, culture and people data, to Zapier, the tool that chains apps together. It is built almost entirely around listening: eight employee events in bob can start an automation the moment they happen.

Three outcomes it is good at. Onboarding that starts on day one: Employee Joined fires when the start date arrives, not when the record is typed, so the welcome steps land at the right time. Clean offboarding: Employee Left fires on the termination date, which is the moment access and equipment should be dealt with. A live roster: New Employee Created, Employee Updated and Employee Temporary Leave let the rest of your tools follow what HR records in bob.

What Zapier does not do here: there is no ready-made action to create or edit an employee, and no search. The only action is API Request (Beta), an advanced step for people comfortable writing a request by hand. In practice, Hibob on Zapier is a source of events, and the work usually happens in other apps after it.

The good news is speed. All eight triggers are instant, so even on the free plan nothing waits for a timer. If you are still deciding whether Zapier is the right tool for HR flows, our Zapier review and the n8n vs Zapier comparison are the two places to start.

Vocabulary

Zapier vocabulary, quickly

The page leans on seven Zapier words. Here is what each one means in practice.

Zap
An automation on Zapier: one trigger, then one or more actions that run every time that trigger's event happens.
Trigger
The event in an app that kicks off the Zap. Once the Zap is on, Zapier sits and waits for that event.
Action
The step that does the work once the Zap has started: it writes, sends or moves something for you.
Task
What Zapier bills: one action your Zap completes successfully. The number on your plan counts exactly those.
Instant vs polling
An instant trigger is reported by the app the moment the event happens. A polling one is checked by Zapier on a timer.
Filter
A step that lets the Zap continue only if what came in meets the condition you set, and stops it otherwise.
Multi-step Zap
Any Zap with more than one trigger and one action. A filter or a second action makes it one, and it needs a paid plan.
Cost

What a Hibob Zap costs you

Hibob is not a premium app, so it runs on Zapier's free plan. And because every trigger is instant, the plan's polling interval does not slow it down.

  • Free plan100 tasks a month, unlimited Zaps
  • Steps on the free plan2: one trigger, one action
  • Hibob triggers8 instant, so no waiting on any plan
  • Hibob on the free planYes, it is not a premium app

Triggers never cost a task. Only actions that succeed count, one task each, and an action that fails is not billed. So a Zap with three actions eats three times what a one-action Zap eats. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger and one action. A filter, or a second action, turns it into a multi-step Zap that needs a paid plan. The interval grid below only matters for polling triggers, and Hibob has none.

Connect

Connect Hibob to Zapier in 3 steps

  1. 01

    Start from Apps

    Open the Apps page of your Zapier account and click + Add connection. A connection is your Hibob account linked once, then reused by every Zap that touches bob.

  2. 02

    Pick Hibob

    Type Hibob in the search box of the dialog that appears, select it, then click Add connection. You need an existing Hibob account; Zapier will not create one for you.

  3. 03

    Sign in and allow access

    Sign in to Hibob in the tab that opens and grant Zapier access to the account. For employee data you do not own, the account also needs read or write access on it.

First Zap

Your first Hibob Zap: welcome a new hire on day one

GoalWhen a new hire's start date arrives in bob, open an onboarding task for the buddy and post a welcome message for the team.

  1. 01

    Build: choose the trigger

    In the editor, under Build, pick Hibob as the trigger app and Employee Joined as the event, then select the Hibob connection you made.

  2. 02

    Test the trigger

    Run the test. Zapier pulls the three most recent items from your account. You then map the next steps on a real employee, not on an empty template.

  3. 03

    Add the onboarding task

    Click the plus icon and pick your task tool as the action app. Map the new hire's name from the trigger into the task title, so the buddy knows who to look after.

  4. 04

    Add the welcome message

    Add a second action in your team chat and write a short welcome that reuses the same name. This second action makes the Zap multi-step, so it needs a paid plan.

  5. 05

    Test, then Publish

    Test each action once and read what came back. Then click Publish. Start dates that passed before that moment are never picked up.

Triggers

The 8 Hibob triggers

8 events start a Zap when something happens in Hibob, and 8 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Employee Activated

Instant trigger

In Zapier“Triggers when employee is activated in bob.”

This trigger reports an employee being activated in bob. It has its own counterpart, Employee Inactivated, which makes the pair handy when access should follow a person's status both ways.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a retail chain that inactivates seasonal staff between peaks and wants to reopen their access the day HR switches them back on.
Watch out
pair it with Employee Inactivated if you automate both directions, so the two Zaps stay mirror images of each other.
2

New Employee Created

Instant trigger

In Zapier“Triggers when a new employee is created.”

As soon as someone adds a new employee record in bob, this one goes off. That usually happens well before the person's first day, at offer stage or during paperwork.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a recruiting team that wants the hiring manager warned early, so laptops and desks get sorted before the start date.
Watch out
creation is not arrival; if your flow should run on day one, Employee Joined is the better choice.
3

Employee Deleted

Instant trigger

In Zapier“Triggers when employee is removed from Bob.”

When an employee is removed from bob, Zapier hears about it here. Removal and inactivation are two separate triggers, and they are worth keeping apart in your head.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an operations lead who wants a record in another tool every time a profile disappears from bob, as a simple audit trail.
Watch out
a record typed by mistake and then removed also fires this trigger, so check what you do with it downstream.
4

Employee Inactivated

Instant trigger

In Zapier“Triggers when employee is inactivated in bob.”

Use this one to catch an employee being switched to inactive in bob. It is a different event from a removal, which has its own trigger, Employee Deleted.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an IT manager who suspends tool access as soon as HR inactivates someone, rather than waiting for a ticket.
Watch out
inactivation and departure are separate events in bob; a Zap built on one will not see the other.
5

Employee Joined

Instant trigger

In Zapier“Triggers when employee start date has occurred.”

Here the signal is the start date itself: the trigger goes off when an employee's start date has occurred, not when the record was created. That makes it the natural first step of day-one onboarding.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a startup that posts a welcome message and assigns a buddy the morning the new hire actually walks in.
Watch out
a Zap published after someone's start date never fires for that person.
6

Employee Left

Instant trigger

In Zapier“Triggers when employee termination date has occurred.”

The mirror of Employee Joined: it fires when an employee's termination date has occurred. What counts is the date itself, so the Zap runs on the actual last day.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a finance team that closes expense cards on the leaver's real last day, not the day the resignation was typed in.
Watch out
a Zap published after someone's termination date has passed never fires for that person.
7

Employee Temporary Leave

Instant trigger

In Zapier“Triggers when a new employee goes on temporary leave.”

Fires when an employee goes on temporary leave. It covers the in-between state where someone is still employed but away for a while.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a consultancy that reassigns an absent consultant's client accounts to a colleague as soon as the leave is recorded.
Watch out
bob gives no separate trigger for the return from leave on this list, so plan how the comeback is handled.
8

Employee Updated

Instant trigger

In Zapier“Triggers when employee is updated in bob.”

The broadest of the eight: any update to an employee in bob sets it off. A new job title, a changed manager or a corrected phone number all count.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keeping a directory in another tool in step with bob, where each change simply overwrites the old value.
Watch out
it fires on every edit, so never use it to create a new record downstream, or each change adds a duplicate.
Actions

The 1 Hibob action

Hibob gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced step that sends a raw request to Hibob, reusing the authentication of your connection, for the cases no ready-made action covers.

When to use it
a technical HR ops person who knows which Hibob address to call and wants Zapier to handle the login part.
Watch out
HTTP Method, URL and Stop on error are all required. Set Stop on error to Yes to halt the step when Hibob returns an error.
When it breaks

When a Hibob Zap breaks

Zapier links no help article to Hibob. The cases below are the general limits that apply to every Zap, seen through HR events.

Most of them do not raise an error: the Zap just misses something or runs more than you meant it to. When a run does fail and the reason is unclear, go to our Zapier troubleshooting page.

  • Past hires are not replayed

    A Zap only reacts to events after it is switched on. Employees who joined or left before that never reach it; moving the backlog is a separate job.

  • A request that wakes its own trigger

    If API Request writes to an employee in bob while Employee Updated is the trigger, the Zap sets itself off again and again and burns tasks fast.

  • A mass import gets held back

    When a trigger suddenly sends a huge batch, after a bulk import or a migration to bob, Zapier's flood protection can hold it back.

  • Stop on error set to No

    With Stop on error on No, the API Request step runs regardless of what Hibob answers, so a failed call can pass unnoticed.
Need help

Need help automating Hibob with Zapier?

A person reads every message.

FAQ

Hibob Zapier integration: common questions

01Is the Hibob Zapier integration free?
Yes. Hibob is not a premium app, so it works on Zapier's free plan, which includes 100 tasks a month and unlimited Zaps. The catch is the step limit: on the free plan a Zap holds one trigger and one action, nothing more. Add a filter or a second action and it becomes a multi-step Zap, which needs a paid plan. The triggers themselves never cost anything, so listening to bob events is free; only actions that succeed are billed.
02How many tasks does a Hibob Zap use?
One task for each action that completes successfully. The trigger is free, whichever of the eight you pick, so a Zap that fires a hundred times but whose action fails every time costs nothing. A Zap with one API Request step uses one task per employee event. Add two more actions and the same event costs three tasks. Keep an eye on Employee Updated, which fires on every edit and can drive the count up quickly.
03Does Hibob send events to Zapier in real time?
Yes. All eight Hibob triggers are instant: bob tells Zapier the moment the event happens, and the Zap starts right away, whatever your plan. The polling interval grid, 15 minutes on the free plan, simply does not apply to them. That type comes from Hibob's own API and cannot be changed in the editor. In the Zap editor, a Zap built on an instant trigger shows a lightning bolt, which is the quickest way to check.
04What does it take to connect Hibob to Zapier?
An existing Hibob account, plus read or write access on the employee data you do not own yourself and want the Zap to touch. The connection is three moves: open the Apps page in Zapier and click + Add connection, search for Hibob and click Add connection, then sign in to Hibob in the new tab and grant access. Once done, every Zap that uses Hibob reuses that same connection, so you only do this once.
05Why does an Employee Updated Zap run so often?
Because it fires on any change to an employee in bob, however small. A corrected phone number counts just as much as a promotion. That is fine for keeping another directory in step, where each run overwrites the old value. It is a problem if the Zap creates something new each time, because every edit then adds a duplicate. If only certain changes matter, a filter after the trigger narrows it down, on a paid plan.
06What if the Hibob operation you need is not there?
Then there are two routes. The first is API Request (Beta), the only Hibob action: it sends a raw request to Hibob with your connection's login, provided the URL sits on a Hibob domain, which covers what no ready-made action does if someone on the team can write the request. The second is accepting that Zapier listens to bob events but does not create or edit employees through a dedicated action today.
07Zapier, Make or n8n for Hibob?
Pick by criteria rather than by brand. On Zapier, Hibob's eight triggers are instant, so speed is not an issue even on the free plan, but the only action is one advanced API Request, with no search. If your HR flows mostly react to bob events and do their work in other apps, that is enough. If you need ready-made steps that create or edit employees in bob, check what the Make or n8n connector for Hibob exposes before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations