HiBob Webhook Setup Guide

When linking your HiBob account in StackOne (or via StackOne Hub), the Native Webhook URL is displayed on the hub form. Copy this URL — you will paste it into HiBob in the next steps.

Log in to your HiBob account. Using the Apps menu (top-left corner), select System Settings. You will be directed to the My Company page.

In the left sidebar, under Integration tools, click Webhooks, then click the + Add webhook button to open the webhook form.

• Enter a Name for the webhook (e.g., StackOne Integration).
• Paste the Native Webhook URL (copied from StackOne) into the Endpoint URL field.
• Under Events, select the events you want to receive. Refer to the Available Webhook Events section below for the full list of supported events.
• Optionally, under Trigger events for specific people, you can scope the webhook to specific employees. When people are selected, HiBob will only send events that occur for those individuals. Choose All employees to receive events for everyone in your organisation.

Click the Add button to save the webhook configuration. HiBob will immediately send a ping test to verify the endpoint is reachable.

• HiBob sends an HTTP POST with either the string "Ping test" or a JSON body {"text":"Ping test"}.
• StackOne responds automatically with a 200 OK status.
• If the ping fails, check that the Native Webhook URL was copied correctly and that the StackOne connection is active.

After saving, you can verify the webhook is working at any time from the Webhooks list.

• Locate your webhook in the list and click the three-dot menu (⋮) on the corresponding row.
• Select Test to send a test event to the endpoint.
• If the connection is healthy, you will see a “Test has been sent” confirmation message.
• The Webhook Status column will show Active, confirming that the endpoint is reachable and responding correctly.

When linking your HiBob account in StackOne (or via StackOne Hub), the Native Webhook URL is displayed on the hub form. Copy this URL — you will need it when configuring the webhook endpoint.

Log in to the HiBob Developer Portal and open your OAuth app. To create a new OAuth app, visit HiBob Connector Profile Guide (OAuth 2.0).

• From the My Apps page, click on the existing OAuth 2.0 app you registered for your StackOne integration.
• In the left sidebar, under the Develop menu, click Webhooks to open the webhook configuration page.
• Toggle Allow event subscription to enable webhook event delivery for your app.
• Paste the Native Webhook URL (copied from StackOne Hub) into the Endpoint URL field.
• Click the + Manage events button to open the event selection modal. Select the events you want to receive. Refer to the Available Webhook Events section below for the full list of supported events.
• Click the Apply button to confirm your selected events. Only events selected here will be delivered to StackOne.

Click the Save button to save the webhook configuration for your OAuth app.

Click the Validate button next to the Endpoint URL field to send a health check request and verify that the endpoint is reachable. You will see the green tick or check within the Endpoint URL field if the validation is successful.

• HiBob sends an HTTP POST with either the string "Ping test" or a JSON body {"text":"Ping test"}.
• StackOne responds automatically with a 200 OK status.
• If validation fails, check that the Native Webhook URL was copied correctly and that the StackOne connection is active.

Events related to employee records, profiles, and table entries.

• Employee created (Employees) — Fired when a new employee is added
• Employee updated (Employees) — Fired when an employee field is modified
• Employee deleted (Employees) — Fired when an employee record is removed
• Employee deactivated (Employees) — Fired when an employee is set on leave or terminated
• Employee activated (Employees) — Fired when an employee’s system access is enabled
• Employee joined (Employees) — Fired when an employee is granted access to the system
• Employee left (Employees) — Fired when an employee is terminated or placed on garden leave
• Employee on leave (Employees) — Fired when an employee is placed on temporary leave
• Table entry created (Employees) — Fired when an entry is added to an employee table
• Table entry updated (Employees) — Fired when an entry in an employee table is modified

Events related to time off requests and balances.

• Request submitted (Time off) — Fired when a time off request is submitted
• Request updated (Time off) — Fired when a time off request is modified
• Request approved (Time off) — Fired when a time off request is approved
• Request declined (Time off) — Fired when a time off request is rejected
• Request canceled (Time off) — Fired when a time off request is cancelled
• Request deleted (Time off) — Fired when a time off request is permanently removed
• Request created from import (Time off) — Fired when a time off request is created via import
• Set end date (Time off) — Fired when the end date is set on an open-ended time off request

Events related to task assignments and document signing.

• Task list triggered (Tasks) — Fired when a task list is triggered for an employee
• Task status changed (Tasks) — Fired when a task is marked complete or incomplete
• eSign document signing completed (Docs) — Fired when all parties have signed an eSign document

Events related to positions, openings, and budgets.

• Position created (Workforce planning) — Fired when a new position is created
• Position updated (Workforce planning) — Fired when a position is modified
• Position opening created (Workforce planning) — Fired when a new position opening is created
• Position opening updated (Workforce planning) — Fired when a position opening is modified
• Position opening deleted (Workforce planning) — Fired when a position opening is removed
• Position budget created (Workforce planning) — Fired when a new position budget is created
• Position budget updated (Workforce planning) — Fired when a position budget is modified