> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# HiBob Webhook Setup Guide

> Configure HiBob to deliver events to StackOne.

## Prerequisites

Before continuing, you should have already completed the following for this connector:

<Steps>
  <Step title="Configure the Connector">
    Enable the connector and set up its connector profile in your project. See <a href="/guides/explore-connectors">Managing Connectors</a>.

    <Columns cols={2}>
      <Card title="Connector Profile" href="/connectors/hibob/guides/connector-profile/service-user" icon="https://stackone-logos.com/api/hibob/filled/png" horizontal>
        HiBob - Service User
      </Card>

      <Card title="Connector Profile" href="/connectors/hibob/guides/connector-profile/oauth-2-0" icon="https://stackone-logos.com/api/hibob/filled/png" horizontal>
        HiBob - OAuth 2.0
      </Card>
    </Columns>
  </Step>

  <Step title="Link an Account">
    Connect an account using <a href="/guides/embedding-stackone-hub">StackOne Hub</a> or <a href="/guides/auth-link">Auth Link</a>.

    <Columns cols={2}>
      <Card title="Link Account" href="/connectors/hibob/guides/link-account/service-user" icon="https://stackone-logos.com/api/hibob/filled/png" horizontal>
        HiBob - Service User
      </Card>

      <Card title="Link Account" href="/connectors/hibob/guides/link-account/oauth-2-0" icon="https://stackone-logos.com/api/hibob/filled/png" horizontal>
        HiBob - OAuth 2.0
      </Card>
    </Columns>
  </Step>
</Steps>

<section data-guide-section data-guide-scopes="">
  <h2>Webhook Setup for Service User Authentication</h2>

  <p>If you connected HiBob using a <strong>Service User</strong>, follow these steps to configure webhooks via HiBob System Settings.</p>

  <Steps>
    <Step title="Copy the Native Webhook URL">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>When linking your HiBob account in StackOne (or via StackOne Hub), the <strong>Native Webhook URL</strong> is displayed on the hub form. Copy this URL — you will paste it into HiBob in the next steps.</p>
      </div>
    </Step>

    <Step title="Navigate to System Settings">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Log in to your <a href="https://app.hibob.com/" target="_blank" rel="noopener noreferrer">HiBob account</a>. Using the <strong>Apps menu</strong> (top-left corner), select <strong>System Settings</strong>. You will be directed to the <strong>My Company</strong> page.</p>
      </div>
    </Step>

    <Step title="Add Webhook">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>In the left sidebar, under <strong>Integration tools</strong>, click <strong>Webhooks</strong>, then click the <strong>+ Add webhook</strong> button to open the webhook form.</p>

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

    <Step title="Save the webhook">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Click the <strong>Add</strong> button to save the webhook configuration. HiBob will immediately send a ping test to verify the endpoint is reachable.</p>

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

    <Step title="Verify the webhook connection (optional)">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>After saving, you can verify the webhook is working at any time from the Webhooks list.</p>

        <ul>
          <li>Locate your webhook in the list and click the <strong>three-dot menu</strong> (⋮) on the corresponding row.</li>
          <li>Select <strong>Test</strong> to send a test event to the endpoint.</li>
          <li>If the connection is healthy, you will see a <strong>"Test has been sent"</strong> confirmation message.</li>
          <li>The <strong>Webhook Status</strong> column will show <strong>Active</strong>, confirming that the endpoint is reachable and responding correctly.</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Webhook Setup for OAuth 2.0 Authentication</h2>

  <p>If you connected HiBob using <strong>OAuth 2.0</strong>, webhooks are configured via the HiBob Developer Portal on your registered OAuth app.</p>

  <Steps>
    <Step title="Copy the Native Webhook URL">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>When linking your HiBob account in StackOne (or via StackOne Hub), the <strong>Native Webhook URL</strong> is displayed on the hub form. Copy this URL — you will need it when configuring the webhook endpoint.</p>
      </div>
    </Step>

    <Step title="Configure Webhooks in the Developer Portal">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Log in to the <a href="https://developers.hibob.com/" target="_blank" rel="noopener noreferrer">HiBob Developer Portal</a> and open your OAuth app. To create a new OAuth app, visit <a href="https://docs.stackone.com/connectors/hibob/guides/connector-profile/oauth-2-0" target="_blank" rel="noopener noreferrer">HiBob Connector Profile Guide (OAuth 2.0)</a>.</p>

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

    <Step title="Save webhook configuration">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Click the <strong>Save</strong> button to save the webhook configuration for your OAuth app.</p>
      </div>
    </Step>

    <Step title="Verify the webhook connection (optional)">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Click the <strong>Validate</strong> button next to the <strong>Endpoint URL</strong> 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.</p>

        <ul>
          <li>HiBob sends an HTTP POST with either the string `"Ping test"` or a JSON body `{"text":"Ping test"}`.</li>
          <li>StackOne responds automatically with a `200 OK` status.</li>
          <li>If validation fails, check that the Native Webhook URL was copied correctly and that the StackOne connection is active.</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Available Webhook Events</h2>

  <p>The following events can be selected when configuring webhooks in HiBob. Only events selected in HiBob will be delivered — if an event is enabled in StackOne's Connector Profile but not selected in HiBob, or vice versa, no notification will be delivered for that event.</p>

  <Steps>
    <Step title="Employee events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Events related to employee records, profiles, and table entries.</p>

        <ul>
          <li><strong>Employee created</strong> (Employees) — Fired when a new employee is added</li>
          <li><strong>Employee updated</strong> (Employees) — Fired when an employee field is modified</li>
          <li><strong>Employee deleted</strong> (Employees) — Fired when an employee record is removed</li>
          <li><strong>Employee deactivated</strong> (Employees) — Fired when an employee is set on leave or terminated</li>
          <li><strong>Employee activated</strong> (Employees) — Fired when an employee's system access is enabled</li>
          <li><strong>Employee joined</strong> (Employees) — Fired when an employee is granted access to the system</li>
          <li><strong>Employee left</strong> (Employees) — Fired when an employee is terminated or placed on garden leave</li>
          <li><strong>Employee on leave</strong> (Employees) — Fired when an employee is placed on temporary leave</li>
          <li><strong>Table entry created</strong> (Employees) — Fired when an entry is added to an employee table</li>
          <li><strong>Table entry updated</strong> (Employees) — Fired when an entry in an employee table is modified</li>
        </ul>
      </div>
    </Step>

    <Step title="Time off events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Events related to time off requests and balances.</p>

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

    <Step title="Tasks and documents events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Events related to task assignments and document signing.</p>

        <ul>
          <li><strong>Task list triggered</strong> (Tasks) — Fired when a task list is triggered for an employee</li>
          <li><strong>Task status changed</strong> (Tasks) — Fired when a task is marked complete or incomplete</li>
          <li><strong>eSign document signing completed</strong> (Docs) — Fired when all parties have signed an eSign document</li>
        </ul>
      </div>
    </Step>

    <Step title="Workforce planning events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Events related to positions, openings, and budgets.</p>

        <ul>
          <li><strong>Position created</strong> (Workforce planning) — Fired when a new position is created</li>
          <li><strong>Position updated</strong> (Workforce planning) — Fired when a position is modified</li>
          <li><strong>Position opening created</strong> (Workforce planning) — Fired when a new position opening is created</li>
          <li><strong>Position opening updated</strong> (Workforce planning) — Fired when a position opening is modified</li>
          <li><strong>Position opening deleted</strong> (Workforce planning) — Fired when a position opening is removed</li>
          <li><strong>Position budget created</strong> (Workforce planning) — Fired when a new position budget is created</li>
          <li><strong>Position budget updated</strong> (Workforce planning) — Fired when a position budget is modified</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.