Ashby interview prep brief in Slack DM for each interviewer

Build me an agent workflow that sends each interviewer a personalized prep brief in Slack a few hours before they interview a candidate.

Trigger: poll Ashby for the interview_schedule_created event. The workflow should run when a new interview schedule is created, and re-evaluate so the brief lands roughly 2 hours before the interview start time (configurable). If the schedule is created less than 2 hours out, send the brief immediately.

Data assembly steps in Ashby. From the new interview schedule, take the application id and the list of scheduled interview events with their interviewers, start times, and stage. Then call:

1. Get Application Info on the application id to get the candidate id, job id, and current stage.

2. Get Candidate Info on the candidate id for name, current title and company, resume highlights, and contact info.

3. List Candidate Notes on the candidate id to capture recruiter screen notes and prior interviewer feedback. Skip any note tagged confidential.

4. Get Job Info on the job id for the role title, team, level, and job description.

5. List Interview Stages for that job's interview plan, and Get Interview Stage Info for the stage each event belongs to, so the brief reflects what that specific stage is meant to assess.

Light web research. Do a small amount of public web research on the candidate's current company and recent work, for example a one-line description of the company and one or two recent projects, talks, or posts if they are publicly visible. Keep this section short and only include items you can actually source. Skip if nothing credible is found.

For each interviewer on the schedule, build a 5 to 8 line brief with these sections:

- Who: candidate name, current role and company, one-line summary.

- Why a fit: 1 to 2 lines tying their background to the role, drawn from the resume highlights and recruiter notes.

- Focus for your stage: 1 to 2 lines on what this specific stage is meant to assess, derived from the stage definition and any rubric in the interview plan.

- 3 to 5 tailored questions for that stage, grounded in both the candidate's background and the focus area.

Slack delivery. For each interviewer, look them up in Slack by the email Ashby has on file (List Users or Get User Info), then Open a Conversation to get a DM channel id, then Send a Message with the brief. Format the message in Slack mrkdwn with a short header line that says the candidate name, stage, and start time in the interviewer's timezone. If the interviewer cannot be matched to a Slack user, log it and continue with the rest.

De-duplication. Track which (interview schedule id, interviewer id) pairs have already been briefed. If the schedule fires again because of an update, only DM new interviewers. Never send the same interviewer two briefs for the same schedule.

Tone: practical, plain English, no fluff, no em dashes. Treat this as a tool for the interviewer's two-minute pre-read, not an exhaustive dossier.

Additional information

What does this prompt do?

Watches Ashby for new interview schedules and runs a few hours before the interview starts.
Pulls together candidate background, recruiter notes, the role they applied for, and the specific stage each interviewer is responsible for.
Adds light public web research so the brief reflects the candidate's current company and recent work.
Sends every interviewer on the schedule a 5 to 8 line Slack DM with a focus area and 3 to 5 tailored questions, and skips anyone who already received a brief for that interview.

What do I need to use this?

An Ashby account with permission to read candidates, applications, jobs, and interview schedules.
A Slack workspace where the agent can send direct messages to interviewers.
Interviewer email addresses in Ashby that match their Slack accounts so each brief reaches the right person.

How can I customize it?

Change how far ahead of the interview the brief is sent, for example 4 hours instead of 2.
Adjust the tone and length of the brief, or add sections like risks, signals to look for, or a link to the candidate's resume.
Limit which stages get a brief, for example only technical screens and onsite loops, and skip recruiter calls.

Frequently asked questions

Will every interviewer get the same message?

No. Each interviewer gets their own DM tailored to the stage they are running. A hiring manager and an engineering interviewer on the same loop will see different focus areas and different suggested questions.

What if an interviewer was already sent a brief for this interview?

They are skipped. The agent tracks who has already received a brief for a given interview schedule, so you do not get duplicate messages if the schedule is updated or rerun.

Can I use this if interviewers do not have Slack accounts that match their Ashby emails?

The agent looks up interviewers in Slack by the email Ashby has on file. If the emails do not match, that interviewer is skipped and logged. You can fix it by aligning the email in Ashby and Slack, or by adding a manual mapping.

Does this work for last-minute interviews?

Yes. If an interview is scheduled less than the lead time you set, the brief is sent right away rather than at the scheduled lead time.

Will this leak sensitive recruiter notes?

You can control what the agent includes. By default it summarizes recruiter notes into a short focus area rather than pasting them verbatim, and you can tell it to exclude any note tagged confidential.