BambooHR, asked instead of searched.
Ask who is out next week, what a colleague's balance is and who reports to whom, and Cedric proposes the time-off approval or the record update before saving it.
100K credits ($50) on sign up. No card needed.
- The questions people ask HR are small and constant: who is out, who is new, what is my balance, and BambooHR has every answer.
- Ask in plain words: who is out of the office over a date range, a colleague's profile and remaining time off, the employees in one department.
- Cedric can create, approve or decline a time-off request and record used leave, each proposed before it is saved.
- New employees are added and fields like job title, department, compensation and contact info updated from the thread, with the change shown first.
- Changing pay, terminating an employee or approving leave is confirmed by a person every time, and BambooHR's rate limits apply.
What can a BambooHR AI agent do?
A BambooHR AI agent answers the everyday questions from the conversation. Cedric searches the employee directory and pulls up an individual's profile details, lists who is out of the office over a given date range, and checks remaining time-off balances. He retrieves saved company reports and custom lists of employee data, so a headcount by department or a list of start dates this quarter is one ask rather than a report export. He also tracks employment history changes such as promotions, transfers and terminations, which is how "when did she move to sales" gets answered.
Time off is the write people want most. Cedric creates, approves or declines time-off requests and records used leave, proposing each one before it is saved, and the who-is-out list means a request can be checked against the rest of the team before approving it. That is a chunk of the routine an operations assistant carries for a small company, handled in the channel where the question was asked.
The record itself can change too. Cedric adds new employees and updates fields like job title, department, compensation or contact info, and uploads and downloads documents attached to an employee's file, such as a signed contract. On the hiring side he reviews job openings, applicants and each candidate's status in the pipeline. Requests are rate limited, and changing pay, terminating an employee or approving leave always waits for a person's yes.
Monday morning
Two requests, one clash, one approval proposed.
Elena Marchetti9:14 AM
@Cedric who's out the week of 21 September, and are there time-off requests waiting for me? Approve any that don't leave support with fewer than two people.
CedricAPP9:15 AM
Out 21 to 25 September: Noah Vance (support, all week, approved) and Aline Dubois (design, Thursday and Friday). Two requests waiting: Karim Haddad (support, 22 to 24 September, balance 11 days) and Mei Tanaka (finance, 25 September, balance 6 days). Karim's request would leave support with one person on those days, so I have not proposed it. Proposed: approve Mei's request for 25 September. Karim's stays pending for you.
Looked up
A colleague's profile, who is out over a date range, remaining balances, and saved reports or custom lists of employee data.
Handled
A time-off request created, approved or declined and used leave recorded, proposed before it is saved.
Updated
A new employee added, a job title, department, compensation or contact field changed, a document filed, on your yes.
Connect BambooHR with your own key
No setup project, no workflow builder, no field mapping. The flow is the same for every tool Cedric connects to.
- 01
Install Cedric where your team talks
One click. He joins your Slack like any other member, and everyone shares the same Cedric.
- 02
Connect BambooHR from the dashboard
Open the Integrations page, pick BambooHR and paste your company's BambooHR subdomain and an API key from your account. You can revoke the connection in one click at any time.
Pick Read-only when you connect if you only want him reading. You can switch it later.
- 03
Ask in plain words
Back in the channel, try it: "who is out of the office next week?" You describe the outcome; Cedric picks the BambooHR actions the ask needs. There is nothing to configure.
Connect for the whole workspace so the team shares it, or keep the connection personal. Two accounts are fine too; each gets a short name.
- 04
Let it become routine
Schedule the recurring version of the ask, and let Cedric fold BambooHR into bigger jobs that cross your other tools. Anything that would leave your workspace still comes back as a preview to approve first.
Better in company
Who is out in BambooHR and what is booked in Google Calendar are the same question asked twice. Ask Cedric whether a meeting in the week of the 21st works and he reads both, then proposes the slot through Gmail to the people who are in.
A new hire's first week is a checklist in Notion and a record in BambooHR. Ask Cedric to add the employee with the start date and department, and he can open the onboarding page from the same reply, which is the start of client onboarding turned inward.
Worth knowing
BambooHR comes from Cedric's catalog of 3,200+ apps. He works from what the BambooHR connection can read and do, the same list its card shows in your dashboard.
Pay, terminations and leave approvals are confirmed by a person. Cedric drafts the change and shows the employee, the field and the new value, and nothing is saved until someone says yes.
BambooHR's rate limits apply. A large report or a directory-wide listing is paged rather than pulled in one go, so a company-wide question takes longer than one about a person.
The BambooHR connection sets the scope. Cedric sees what it grants. Access is logged, and you can revoke it from the dashboard at any time.
Nothing sends itself. An email, a post, a change to a record: anything with consequences comes back as a preview for a person to approve.
FAQ
Yes. BambooHR is one of the 3,200+ apps in Cedric's catalog. Connect it once from the dashboard, with your company's BambooHR subdomain and an API key from your account, and ask in plain words. Cedric picks the actions an ask needs from what the connection can read and do, with no fields to map.
He sees what the connected account can see in BambooHR, no more. Compensation is one of the fields he can read and update when that account has access, and any change to it is proposed and confirmed by a person before it is saved.
No. He can prepare the approval or the decline, check the request against who else is out and the remaining balance, and he waits for your yes before saving it in BambooHR.
Connect it for the whole workspace and everyone shares it, with one person authorising once. A connection you would rather not share, a personal inbox for instance, can stay personal to you.
Yes, and it starts that way: a key connection is read-only until you turn writes on. Even with writes on, anything that changes or sends waits for an approval.
Every workspace starts with 100,000 free credits (worth $50) on sign-up, no card. Plans start at $19 a month for the whole team, no seats. Each task uses credits in proportion to the work. See pricing.
Works well with BambooHR
GreenhouseCandidates, stages and scorecards read from the thread; every stage change on your yes.
GustoEmployees, pay schedules and payroll runs read from the thread; any pay change on your yes.
CalendlyMeeting types, bookings and invitees looked up, links created, cancellations on your yes.
Google SheetsForms and leads land in the right row, columns stay clean, and the numbers get read back.
AirtableBases read, searched and updated from the thread: records, fields, comments, on your yes.
ConfluencePages searched, read, written and updated from the thread, each new version on your yes.
Connect BambooHR in a minute.
Ask who is out next week, then see the approval he proposes for the next request.
100K credits ($50) on sign up. No card needed.