Integrations / BambooHR

BambooHR

BambooHR HRIS for employee directory, employment status, time off, job info, and lightweight people operations workflows.

Basic auth

Indexes

Actions

Events

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events Yes

Before you connect

Prerequisites

A BambooHR company you can administer.

Permission to create an API key.

Vendor setup

Get the credential

Create an API key

In BambooHR, open Settings → API Keys (under Apps / integrations, wording varies). Create a key.

Paste in Telara

Settings → Integrations → BambooHR. Use the key as the username. The password field can be any non-empty placeholder.

In Telara

Connect in Telara

Basic auth

BambooHR API key over HTTP Basic Auth. Use the API key as username and any non-empty password, commonly x.

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

Fields Telara asks for

API key
Password

Knowledge

What gets indexed

Resource	Coverage
Employee	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Employee	Up to 1 day	Removed 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

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

The key inherits that user’s directory view.

A key created in a sandbox company does not read production.