Skip to main content
Telara

Integrations / HiBob

HiBob logo

HiBob

HiBob HRIS for employee lifecycle, people data, time off, documents, reports, and HR-driven access workflows.

Basic auth
Indexes
Actions
Events

What Telara does

Capability matrix

Before you connect

Prerequisites

A HiBob account you can administer.
Admin who can create a service user under Integrations.

Vendor setup

Get the credential

1
Open service users
In HiBob, go to Settings → Integrations → Service Users (or Automation → Service users).
2
Create a service user
Click New service user. Name it for Telara. Copy the service-user id and token. HiBob uses HTTP Basic with those two values.
3
Paste in Telara
Settings → Integrations → HiBob. Paste the id as username and the token as password, matching the Connect form labels.

In Telara

Connect in Telara

Basic auth

HiBob service-user Basic Auth using service user ID as username and service user token as password.

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for
  • Service User Id
  • Service User Token

Knowledge

What gets indexed

ResourceCoverage
EmployeePartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
EmployeeUp to 1 hourRemoved records disappear when Telara next reconciles that resource

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Employee.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Permission groups on the service user control which people Telara can see. Missing employees are usually a HiBob permission group.
Sandbox and production companies are different service users.