Skip to main content
The common use is onboarding and account changes from the HR system: a scheduled agent asks a client’s BambooHR who was added or changed since its last run, reads each employee’s record, creates or updates their Microsoft 365 account with the values BambooHR holds, and writes the new work email back to BambooHR.
Automatically enabled when you configure BambooHR permissions in your agent workflow. BambooHR is connected per client, so the agent calls the BambooHR company of the company it works on.

What it does

  • Find the employees added, changed or removed since a time, and the table rows that changed
  • Read an employee’s record with the fields the job needs, and their job, employment status and asset history
  • List and filter employees, and read the company directory and BambooHR users
  • Add employees, change their fields, and add or change rows in their tables
  • Read and change time off, time tracking and schedules, hiring, onboarding, training and goals
  • Read and change compensation, benefits, personal details, file names, reports and datasets, custom fields and company settings
  • Read and change webhooks
Neo does not upload or download a file’s content: the agent lists an employee’s or the company’s files, and a person opens or adds the file in BambooHR. Neo asks BambooHR for JSON only, so a report runs as JSON, never as a CSV, Excel or PDF file. Neo does not delete an employee: to end someone’s employment, the agent adds a Terminated row to their employment status. Neo replaces government identity numbers (such as social security, social insurance and national insurance numbers, national ids, employer identification numbers and passport numbers) and webhook signing keys in every BambooHR answer, so the agent never reads one. A report column of an identity-number type is replaced too. A write that sends Neo’s placeholder back is refused, so BambooHR keeps the value it has, and a webhook may not send one of those fields to its address.

Fields and tables

An agent names the fields it reads or writes, and each field needs its permission group: a home address or birth date needs Personal Details, a pay rate needs Compensation & Benefits, and a field the client added in BambooHR needs Custom Fields & Tables. The same holds for the fields a list filters or sorts on, the fields a webhook watches and sends, and the tables an agent reads or writes, such as the compensation or emergency contacts table. A write asks a technician when a group it writes asks.

Permission groups

Access profiles

Read Only, Helpdesk and IT Admin keep Personal Details, Compensation & Benefits, Files and Reports & Datasets off. Turn one on by hand for an agent that needs it.

Safety Controls

Creating or changing a webhook always asks a technician, whatever the access profile: a webhook sends employee data to the address it names, outside BambooHR, on every later change. Naming a compensation planning cycle’s admins, its final approver, or an approval flow’s recommenders and approvers always asks too, because it gives someone authority over pay. Every other BambooHR write follows its group’s approval setting and the agent’s access profile.