WorkerKitAI workers for BambooHR
AI workers for BambooHR help your team prepare a team availability brief and answer a people-data question. Connect the intended account, choose a focused job and grant the available tools that job needs.
What is an AI worker for BambooHR?
Answer scoped people-operations questions from BambooHR employees, reports, time off, goals and hiring data, using the connecting user's existing permissions. The available capabilities load after you connect and depend on your vendor permissions and enabled features. Each worker receives the tools its owner grants. Start with a specific set of records and a result your team can verify; this connection does not add vendor-side field or record permissions.
What these workers do
Prepare a team availability brief
Review accessible time-off information for the requested team and period without exposing unrelated employee details.
Answer a people-data question
Use available employee fields and reports to answer a defined HR question, stating permission-related gaps.
Review hiring progress
Summarize accessible hiring records and outstanding steps for the recruiting team, keeping candidate details within the intended audience.
How an AI worker runs in BambooHR
Connect the right account
Start with a concrete workflow
Grant the actions the job needs
Check the outcome
BambooHR questions, answered.
How do I connect BambooHR?
A BambooHR admin enables AI Connectors. Register an app in its developer portal with mcp and the entity scopes needed. An account admin enters your company endpoint and OAuth client; then sign in. The first authorized connection loads the available capabilities. Review those tools and the account identity before granting access to a worker; the app's presence in the directory does not establish a connection.
What can a worker access or change?
Answer scoped people-operations questions from BambooHR employees, reports, time off, goals and hiring data, using the connecting user's existing permissions. The available tools follow the connected user's vendor permissions, and WorkerKit exposes only the tools granted to that worker. Tool-level grants do not create a separate field mask, per-customer boundary or monetary limit inside the vendor.
What is a useful first workflow?
Review accessible time-off information for the requested team and period without exposing unrelated employee details. Start with a bounded period or small set of records, ask for source references and review the result in BambooHR. BambooHR MCP is in beta. Missing fields may reflect permissions, not missing employee data. Confirm the actual available tools before making a kit depend on them.