Greenhouse, without opening Greenhouse.
Move the candidate through the pipeline without leaving the thread.
- Free to start
- No card
- Every write waits for you
- Your own account, not a shared login
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Greenhouse details, and Ray takes it from there.
@Ray move that candidate to the onsite stage and book the panel.
@Ray how many candidates are sitting in the take-home stage?
@Ray add a note on that candidate about the reference check.
@Ray reject the two who withdrew and say why.
What Ray can and cannot do in Greenhouse
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
25 reads wired, 24 actions that wait for a human.
Runs on its own
What Ray reads in Greenhouse
- Jobs, openings, job posts, and who owns them
- Candidates, applications, their stages, and scorecards
- Interviews, interview kits, offers, notes, and rejection reasons
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Add a candidate, an application, or a job
- Move an application to another stage, or mark it hired
- Reject an application, with the reason on the card
- Schedule an interview
- Create an offer
- Note on a candidate or a job, and tag a candidate
- Request approvals, or replace an approver
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 demographic, EEOC, or pay data
- Delete an application, an attachment, or a candidate tag
- Create or deactivate a user, or change their permissions
- Do any of it in bulk
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Greenhouse actions Ray can take, each one stopping in the thread with the real content before it happens.
- Tag a Greenhouse candidate
- Add a Greenhouse application
- Add a candidate to Greenhouse
- Add education to a Greenhouse candidate
- Add employment to a Greenhouse candidate
- Create a Greenhouse candidate tag
- Schedule a Greenhouse interview
- Create a Greenhouse job
- Note on a Greenhouse job
- Note on a Greenhouse candidate
Tag a Greenhouse candidate
Showing Candidate id, each carrying the exact content that will land.
How Ray works with Greenhouse
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Greenhouse
One click, right where you asked. Ray posts a connect card, you authorise Greenhouse with your own account, and the work you asked for picks up where it left off.
- 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 Greenhouse, and tell Dana it is being looked at.
Tag a Greenhouse candidate
- Waiting on
- your approval
Ray uses Greenhouse together with the rest of your tools.
One ask can read Greenhouse, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.
What does connecting Greenhouse to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Greenhouse and it can do the Greenhouse 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.
Every person on the team connects their own Greenhouse account, so Ray can only reach what that person can already reach, and the history in Greenhouse shows who actually asked.
Security and permissions
- You authorise Greenhouse on its own login screen. Your password never passes through Ray.
- 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.
- Disconnect Greenhouse in a message, or uninstall Ray and every connection it held is revoked.
Greenhouse and Ray, answered
The questions teams ask before they connect Greenhouse. Every answer is how this integration is built rather than a promise about it.
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 Greenhouse.
Free to start, no credit card, and it asks before it acts.