BambooHR New Hire Onboarding Agent
Spots real new hires in BambooHR, builds your onboarding checklist in Asana with dates counted back from the start date, and sends the manager one Slack brief with who is out that week.
A first day goes wrong in the same three ways at every company: no laptop, no accounts, and a manager who forgot somebody was starting. This agent watches BambooHR for people who are actually joining, builds your checklist in Asana with real dates counted back from the start date, and gives the manager one Slack message with the start date and who is on leave that week. It writes nothing back to BambooHR, and the personal fields on the record never leave it.
## What people use it for
- **Nothing depends on remembering** - The checklist is created the moment the hire is confirmed rather than the week somebody thinks of it. New joiners in a busy month get the same setup as the one everybody was excited about.
- **Dates counted back from day one** - Order the laptop five days before means five days before their start date, written on the task as a real date. A start date that lands inside your lead time gets said out loud instead of silently becoming an overdue task.
- **Managers hear it once, clearly** - One Slack message with the name, the role, the start date, their own tasks, and who is on leave that week. Knowing the buddy is away before day one is the difference between a good first week and a quiet one.
- **Personal data stays in BambooHR** - Salary, address, date of birth and visa status never make it into an Asana task or a Slack channel, because the agent is limited to name, role, department, manager and start date. Onboarding automation is where HR data leaks, so the line is drawn in the instructions.
## Before you fork
**What do I need connected before it runs?**
A BambooHR credential that can read the directory and time off, an Asana connection with the onboarding project already created, and the Slack channel or manager DM you want the brief in. Then you write the checklist: each task, its owner, and its timing relative to the start date. If your checklist already exists as an Asana template, copying the task names across is most of the work.
**Does anything private end up in Slack or Asana?**
No. It is restricted to name, job title, department, manager and start date, and instructed to keep pay, home address, personal contact details, date of birth, national ID, visa status, emergency contacts and anything medical out of every task and message. If your checklist mentions a task like enrol in payroll, the task says exactly that and carries no numbers. Anything needing a private field goes to the owner as a task to look it up themselves.
**What happens on status changes that are not new hires, and what does it cost?**
Promotions, returns from leave, record corrections and departures all fire the same BambooHR event. The agent confirms the change is a genuine start before it does anything, so those runs end in one step with no tasks and no Slack message. That means the cost tracks your status changes rather than your hires, and most companies see a handful a month.
