BambooHR, without opening BambooHR.
Who is out next week, who is hiring, and who just joined.
“@Ray who is off next week?”
What Ray can and cannot do in BambooHR
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
Runs on its own
What Ray reads in BambooHR
- Time off: requests, balances, policies and the types behind them
- The employee directory, and one person's record when you ask by name
- Job openings, applications and the statuses they sit in
- Departments, divisions, locations and job titles
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Requesting time off for someone
- Adding an employee, or changing fields on a record
- Opening a job and adding candidates to it
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Read or add employee dependents, or their benefit enrolment events
- Download reports, custom field exports or employee photos
- Approve, deny or cancel a time-off request
How Ray works with BambooHR
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect BambooHR
BambooHR has no per-person login, so it takes one workspace key. Ray posts a connect card, you paste the key on Ray's own page rather than in Slack, and it covers the whole team from then on.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in BambooHR, and tell Dana it is being looked at.
Add a candidate to BambooHR
- Waiting on
- your approval
What does connecting BambooHR to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect BambooHR and it can do the BambooHR part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
BambooHR has no per-person login, so it connects once with a single workspace key and covers the whole team. Ray reaches whatever that key reaches, which is worth scoping the way you want everyone to see BambooHR. Every write still stops for approval first.
Security and permissions
- You paste the BambooHR key on Ray’s own page, never in Slack. It goes straight to the connection and never reaches the model.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- An admin, or whoever connected it, can disconnect BambooHR in a message. Uninstall Ray and every connection it held is revoked.
More hr, time & recruiting integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in BambooHR.
Free to start, no credit card, and it asks before it acts.