BambooHR

Employment status, start and last-day dates, manager, department and worker type from BambooHR, as triage context. Read-only; no personal or compensation data is stored.

• Connector id: bamboohr
• Category: hr

Configuration

Field	Label	Type	Required	Default	Notes
subdomain	Company subdomain	string	yes	—	The first label of your BambooHR URL: acme.bamboohr.com -> acme.
api_key	API key	secret	yes	—	encrypted at rest · Generated from your BambooHR profile under API Keys. Needs directory and employee read access.
max_employees	Maximum employees per sync	number	no	5000	A ceiling on the per-employee reads one sync will make.

Credential handling

api_key is encrypted at rest by the credential vault before the row is written, and decrypted only at poll time. The value is never logged and never returned by the API — a read of the saved connector shows the field as set, not its contents. See credential vault.

Capabilities

• pull_workforce

Setup

1. In the console, go to Connectors → Add connector and pick BambooHR.
2. Fill in the fields above and run Test connection. The test is read-only and does not save anything.
3. Save. Polling starts on a jittered schedule within about a minute; the connector row shows last_sync once the first poll completes.

If last_sync stays empty

The first poll is the honest signal that the credential works. A connector that saves cleanly and never syncs usually means the credential lacks a scope the vendor requires for reads — check the connectors service log for the vendor's own error, which is passed through verbatim rather than summarised.

Vendor-specific setup notes go here: which console page issues the credential, which scopes to grant, rate limits, and anything the schema cannot express. This section is preserved when the page is regenerated.