Skip to main content

How to connect BambooHR to Coworker

Connect BambooHR so Coworker knows who works at your company and who reports to whom. BambooHR is an admin-connected, identity-only source — it anchors the roster spine of Coworker's knowledge graph.

BambooHR Data in Coworker

Indexed into the knowledge graph

  • Employee directory, including every hire, update, and termination — builds a verified Person entity for each employee

  • Hire and termination dates per employee

  • Merges each employee's identity with the same human across Slack, Google, Jira, your CRM, and every other connected source

  • Builds your org chart from reporting lines

  • Stamps a standard set of HR properties (e.g. title, department) onto each Person node

Available to users, but kept out of the graph

These are available via live chat tools rather than becoming searchable graph content:

  • Time-off requests and the who's-out calendar, including upcoming approved leave

  • Locations, the custom field catalog, and account users

Never collected

Compensation and salary data, bank details, review and feedback text, private-goal descriptions, identity documents, emergency contacts, birthdays, and home addresses are excluded at the API-scope and code level for every HRIS connector — they never reach the warehouse, the graph, or a prompt.

Before you start

  • You must be a Coworker Network Admin

  • You need a BambooHR API key created by a BambooHR admin

  • You need your BambooHR company subdomain

Connect as an admin

  1. Open Data Sources from the admin settings in Coworker.

  2. Select BambooHR.

  3. Paste your BambooHR API key and enter your company subdomain.

  4. Save. Coworker validates the credential immediately and reports any problem.

Connect as a member

Members cannot connect BambooHR individually. One admin credential covers the whole workspace.

Good to know

  • The API key inherits the permissions of the employee who created it. Use an admin-created key — a non-admin key can authenticate successfully while silently omitting people or fields.

  • The subdomain is part of the credential. A valid key paired with the wrong company subdomain fails just like a bad key.

Did this answer your question?