Greenhouse, kept current from the hiring channel.
Ask where a candidate is, what the interviewers said and who is still waiting on feedback, and Cedric proposes the note, the stage move or the rejection before it is recorded.
$50 in free credits when you sign up. No card needed.
- Hiring conversations happen in the channel and the decisions belong in Greenhouse, which is where they tend not to end up.
- Ask in plain words: a candidate's profile and application history, everyone in the onsite stage for one role, the scorecards from yesterday's loop.
- Cedric can advance an application to the next stage or record a rejection with a reason, and post the note or activity entry that explains it.
- New candidates and prospects are added with resumes and files attached, and open jobs, departments, offices and hiring teams are one question away.
- Most writes are attributed to a specific user and may need approval, so each one waits for your yes, and Greenhouse's rate limits apply.
What can a Greenhouse AI agent do?
A Greenhouse AI agent reads the pipeline so the hiring manager does not have to. Cedric searches and retrieves candidate profiles, including contact details, tags and application history, and reviews each application's current stage, source and status across the pipeline. It lists open jobs, job posts, departments, offices and hiring team members, so "who is on the panel for the backend role" and "how many people are in phone screen for it" get answered in the thread. It reads interview scorecards, feedback and scheduled interviews for a candidate, which is what a debrief actually needs.
Writes are proposed first. Cedric advances an application to the next interview stage or records a rejection with a reason, and posts notes and activity feed entries so the recruiting record shows what was decided and why. It adds new candidates or prospects, attaches resumes and files, and updates their details when a referral arrives in the channel rather than through the careers page. Most write actions in Greenhouse are attributed to a specific user and may need approval, which is one more reason each one waits for your yes.
For reporting, Cedric pulls offer details, users and custom fields, so a weekly hiring summary by role and stage can be drafted from the data rather than from memory, the same way a weekly report is. Two things the connection cannot do: send candidate emails or book interview times. Those still happen in Greenhouse or the calendar, and Cedric says so rather than pretending. Requests are rate limited.
After the debrief
Four scorecards read, one stage move proposed.
Tomasz Nowak9:14 AM
@Cedric where is Amara Osei for the Senior Backend role, what did the onsite panel say, and if everyone was a yes move her to Offer with a note that comp discussion is Thursday.
CedricAPP9:15 AM
Amara Osei, Senior Backend Engineer, source: referral, stage Onsite since 1 September. Four scorecards submitted: three Strong Yes (Lea, Dev, Priyanka) and one Yes (Hugo, note: "wants more depth on data modeling, not a blocker"). No scorecard outstanding. Proposed: advance the application to Offer and post a note: "Panel unanimous. Comp discussion Thursday." Recorded under your name. Nothing is changed yet.
Looked up
A candidate's profile, tags and application history, and each application's stage, source and status across the pipeline.
Read
Scorecards, interviewer feedback and scheduled interviews for a candidate, and the open jobs, departments and hiring teams behind them.
Recorded
A stage advanced or a rejection filed with a reason, a note or activity entry posted, a candidate added with the resume attached, on your yes.
Connect Greenhouse in a minute
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. It joins your Slack like any other member, and everyone shares the same Cedric.
- 02
Connect Greenhouse from the dashboard
Open the Integrations page and sign in with Greenhouse on its own screen. Cedric never sees or stores your password, and you can revoke the connection in one click at any time.
A fresh connection can look but not touch: read-only until you say otherwise.
- 03
Ask in plain words
Back in the channel, try it: "who is in the onsite stage for the backend role?". You describe the outcome; Cedric picks the Greenhouse 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 Greenhouse 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
A referral arrives in Gmail with a resume attached; Cedric can add the candidate to Greenhouse with the file and the referrer noted, on your yes. The interview loop then lives in Google Calendar, where Cedric can read who is booked when, since Greenhouse's own API does not book interview times.
The hiring plan is a table in Notion and the sourcing happens on LinkedIn. Ask Cedric how each open role is tracking and it reads the plan, the pipeline stages in Greenhouse and the outreach, then names the roles that are behind.
Where the limits are
Greenhouse is a catalog connection, not a built-in playbook. Cedric works from what the Greenhouse connection can read and do; ask in plain words and it says what it can reach there, and what it cannot.
It does not email candidates or book interviews. Greenhouse's API cannot send candidate emails or schedule interview times, so Cedric drafts the note for the record and leaves the scheduling to the calendar.
Writes carry a name and may need approval. Most write actions are attributed to a specific user and may need approval in Greenhouse, so Cedric proposes each stage move, rejection or note and waits for your yes.
Cedric sees what the Greenhouse connection grants and nothing more. Access is scoped, logged, and revocable from the dashboard, effective immediately.
Nothing sends itself. An email, a post, a change to a record: anything with consequences comes back as a preview for a human yes. That is the design, not a beta caveat.
FAQ
Yes. Greenhouse is one of the 3,200+ apps in Cedric's catalog: connect it once from the dashboard, on Greenhouse's own sign-in screen, and ask in plain words. There is no built-in playbook for it, so Cedric works from what the connection can read and do, and tells you when something is out of reach.
It can record a rejection with a reason on an application, and it shows the candidate, the role and the reason before doing so. The rejection email, if any, is sent from Greenhouse itself; the connection does not send candidate emails.
Yes. It reads the submitted scorecards and feedback for a candidate, names who has not submitted yet, and summarizes the ratings and the comments so the debrief starts from the same page.
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 fresh connection can look but not touch until you say otherwise. Even with write access granted, anything that changes or sends waits for an approval.
Every workspace starts with $50 in credits, free, no card. Each task consumes credits in proportion to the work involved. See pricing for the plans.
Connect Greenhouse in a minute.
Ask who is in the onsite stage for one role, then see the note it drafts after the next debrief.
100K credits ($50) on sign up. No card needed.