# Daily Workable interview prep briefs by Slack and email > Every weekday at 7am, each interviewer gets a one page brief on the candidates they are meeting today, in Slack and in their inbox. - Workflow type: agent - Services: Workable, Slack Bot, Gmail - Categories: HR & People - Published: 2026-08-10 ## What it does - Reads the day's scheduled interviews, calls, and meetings straight out of Workable, so no calendar connection is needed - Builds a one page brief per interview: who the candidate is, their most relevant experience for that exact role, where they sit in the pipeline, and four or five questions worth asking - Sends each interviewer their brief as a Slack direct message and as an email, so it is readable on a phone right before the call - Rolls a busy day into a single message per person, ordered by start time, instead of a pile of separate pings ## What you'll need - A Workable account where your interviews are scheduled and your candidates and jobs are tracked - A Slack workspace where the assistant is allowed to send direct messages - A Gmail account to send the briefs from - Interviewer email addresses in Workable that match the ones they use for Slack and email, so briefs reach the right person ## Prompt Every weekday at 7am, send each interviewer a prep brief for the interviews they are running that day. Start with the Workable List Events operation to pull scheduled events for the current day, and keep the ones that are interviews, calls, or meetings tied to a candidate. For each event, record the start time, the candidate it is for, the job it is against, and the interviewers assigned to it. Use the Workable List Members operation to resolve interviewer names and email addresses, since the email address is what links a Workable member to their Slack account and their inbox. For each candidate on the schedule, use the Workable List Candidates operation to pull their profile and resume detail. Workable exposes list operations only, so narrow down with the filters List Candidates supports, which are job, stage, email, and date, rather than reaching for a single candidate lookup that does not exist. Use the Workable List Jobs operation to pull the role they are interviewing for, including title, department, location, and description, so the brief is written against the real requirements of that specific job instead of generic role assumptions. Write a one page brief per interview with four parts. First, who the candidate is in two sentences. Second, their most relevant experience for this specific role, drawn from their resume and matched against the job description, calling out what is a strong match and what is thinner than it looks. Third, where they sit in the pipeline and what has happened so far, including the stage they are in and any prior activity on their profile. Fourth, four or five suggested questions aimed at the gaps in their background or the claims worth probing. Keep it skimmable and specific to this candidate, not generic interview advice. Deliver each brief two ways. Use the Slack Bot Look Up User by Email operation to find the interviewer from their Workable email address, then Open a Conversation to get the direct message channel, then Send a Message to send them the brief as a direct message. Then use the Gmail Send a Message operation to email the same brief to that interviewer so it is readable on mobile before the call. If an interviewer has more than one interview that day, combine their briefs into one Slack message and one email, ordered by start time, with a short header listing the day's schedule at a glance. If an interviewer has no interviews scheduled, send them nothing at all. If a candidate or job cannot be matched to an event, still send the brief with whatever detail is available and note what was missing, rather than dropping the interview silently. If the Slack lookup finds no matching user, continue and send the email anyway. Make the run time, how far ahead it looks, and the delivery channels easy to change. A same day 7am run and a run 24 hours ahead of each interview are both reasonable defaults, and some teams will want Slack only or email only. ## How to customize - Change the timing. A 7am same day run is the default, but you can send briefs 24 hours ahead so people can read them the night before - Pick your delivery. Keep both Slack and email, or turn either one off if your team only reads one of them - Reshape the brief. Adjust how many suggested questions it ends with, and which event types count as an interview worth prepping for ## Example output Your interviews today (2) 9:30am Priya Raman Senior Backend Engineer 2:00pm Tom Whelan Senior Backend Engineer --- 9:30am Priya Raman Senior Backend Engineer Who she is: Priya is a backend engineer with seven years of experience, currently at a mid size payments company where she leads a team of four. She has spent most of her career on high throughput transaction systems in Go and Python. Most relevant experience: The role asks for distributed systems ownership at scale. Priya rebuilt her current employer's ledger service to handle a 12x volume increase and moved it off a single Postgres instance, which is the closest match to what this team is hiring for. Her Kubernetes exposure looks real but secondary, mostly as a consumer rather than an operator. Where she sits: Technical screen, passed. Recruiter screen notes flag salary expectations at the top of the band. This is her second conversation with the team and the first with an engineer. Worth probing: 1. The ledger migration is the headline. What specifically did she design versus inherit or delegate? 2. She led a team of four but is applying to an individual contributor role. Where does she want to sit in two years? 3. Her resume lists Kafka on three projects but never describes a failure or a rebalance she had to debug. Ask for one. 4. No public writing or open source since 2022 despite listing it as an interest. Low signal, but worth a light touch. 5. She has changed roles roughly every two years. Ask what would make this one different. ## FAQ ### Do I need to connect a calendar for this to work? No. Workable already keeps track of scheduled interviews, calls, and meetings, so the workflow reads the day's schedule directly from Workable. There is nothing to sync from Google Calendar or Outlook. ### What happens if someone has three interviews in one day? They get one message rather than three. The briefs are combined into a single Slack message and a single email, ordered by start time, with the day's schedule summarized at the top. ### Can I get the brief the day before instead of the morning of? Yes. The timing and how far ahead it looks are both settings you can change. Running it at 7am for that day's interviews and running it 24 hours ahead are both common choices. ### What if an interviewer is not in our Slack workspace? The workflow matches interviewers to Slack using their email address. If no Slack account matches, the email still goes out, so they are not left without a brief. ### Does the brief include the candidate's full resume? It summarizes the experience that actually matters for the role being interviewed rather than pasting in the whole resume. The point is something you can read in two minutes before a call. Use this prompt in General Input: https://www.generalinput.com/prompts/daily-workable-interview-prep-briefs-by-slack-and-email