HR · 45 pre-built actions
BambooHR integration with Nexus
Connect BambooHR to the systems that act on people changes. Employee, payroll, performance and time off actions become steps in governed workflows that reach identity, IT and finance.
Pre-built actions
What you can automate
45 pre-built BambooHR actions, grouped by what they work on.
45
PRE-BUILT ACTIONS
- 01Employees actions read and update employee records for downstream systems.
- 02Payroll actions bring pay data into finance checks.
- 03Performance and Time Off actions support review cycles and leave coordination.
Workflow
How it fits into a Nexus workflow
BambooHR steps run as pre-built actions. A run that uses them starts from a webhook, a schedule, a request in Nexus or another system's trigger source.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the BambooHR API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
New hire to identity and equipment
A new BambooHR employee starts Okta provisioning and an equipment request, with approval for privileged access.
Time off to calendar and coverage
Approved time off is reflected in calendars and the team channel so coverage can be planned.
Leaver offboarding
A termination starts deprovisioning across identity and collaboration systems, with each step recorded.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
Industry use cases
Processes that use BambooHR
FAQ
BambooHR connector questions
- Which BambooHR actions are pre-built?
- Nexus includes 45 pre-built BambooHR actions across Payroll (10), Performance (15), Time Off (10) and Employees (10).
- Can BambooHR start a workflow?
- Runs that use BambooHR start from a webhook, a schedule or another trigger source. BambooHR steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the BambooHR API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- Okta connector
Identity changes driven by workforce events.
- Microsoft 365 connector
Teams, email and calendar.
- Workday connector
Employee, payroll and recruitment actions.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how BambooHR fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.