Personal interviewer coaching notes every weekday in Slack

Every weekday at 8am, review yesterday's interviews and DM each interviewer a short coaching note with two wins and one thing to try next.

Agentic Task
MetaviewGoogle CalendarSlackHR & PeopleOperationsMeeting WorkflowsDaily DigestsAI Reports
PromptCreate

Every weekday morning at 8am, run me a personal interviewer coaching loop across Google Calendar, Metaview, and Slack. Timezone: my local timezone. Scope: interviewers on my team (I will provide a list of interviewer emails, or default to everyone I have calendar access to).

Step 1 — Pull yesterday's meetings. For each interviewer, use Google Calendar's List Events on their primary calendar with timeMin/timeMax set to yesterday 00:00 through 23:59 in their timezone (singleEvents=true so recurring meetings expand). Identify which events were candidate interviews using lightweight heuristics: title contains words like interview, screen, phone screen, onsite, loop, technical, behavioral, or the candidate's name pattern; and/or the event has at least one external attendee (email domain does not match the interviewer's). If in doubt, favor recall over precision — it is fine to look one up and then drop it if Metaview has nothing.

Step 2 — Fetch the transcript and AI notes from Metaview. Metaview exposes its data through an MCP server, so tool names are not fixed. Call Metaview's List Available Tools once at the start of the run to discover the current catalog and their input schemas. Then, for each candidate interview from Step 1, use Call a Tool with the appropriate discovered tool names to (a) find the matching Metaview interview by candidate name, interviewer, and start time, (b) pull its transcript, and (c) pull its AI notes / scorecard summary. Match tolerantly on time (±30 min) and interviewer email. If Metaview has no record, skip that interview.

Step 3 — Score against a lightweight rubric. For each interview, produce a short internal score (do not send this raw) on: opening and rapport, coverage of the role's key competencies, question quality (open-ended, probing, non-leading), listen-to-talk ratio, and follow-up depth. Use the transcript and AI notes as evidence. Cite one or two specific moments (a question asked, a follow-up missed, a strong summary) so the feedback is concrete.

Step 4 — Draft one coaching note per interviewer (not per interview). If an interviewer ran multiple interviews yesterday, roll them up into a single note. The note should be short and human: a one-line greeting, two specific things they did well (with a brief example each), and one specific thing to try next time, phrased as a suggestion not a scold. No em dashes. No corporate hedging. Around 120–180 words total.

Step 5 — Deliver via Slack. For each interviewer with at least one scored interview, use Slack's Send a Message to DM them the coaching note (open a DM first if needed by looking up their Slack user via workspace email match). Skip anyone with no interviews yesterday, no Metaview data, or no Slack account. At the end, DM me a one-line summary of who got a note, who was skipped, and why.

Guardrails: never post to a public channel; DMs only. Never include candidate PII beyond the candidate's first name. If any step returns an error or empty result for an interviewer, log it and continue with the rest of the team — one bad interview should not block the run.

Additional information

What does this prompt do?
  • Pulls yesterday's calendar for each interviewer on your team and picks out the candidate interviews automatically.
  • Reads the matching Metaview transcripts and AI notes so the feedback is grounded in what actually happened in the room.
  • Scores each interview against a simple rubric: rapport, competency coverage, question quality, listening, and follow-up.
  • Sends every interviewer a short Slack DM with two things they did well and one specific thing to try next time.
What do I need to use this?
  • A Metaview account with access to your team's interview transcripts and AI notes.
  • A Google Workspace login with permission to see the calendars of the interviewers you want to coach.
  • A Slack workspace where those interviewers can be reached by direct message.
  • An optional list of interviewer emails, so the workflow knows exactly who is on your team.
How can I customize it?
  • Change the run time or move it to a weekly cadence instead of every weekday.
  • Swap the rubric so the wins and suggestions match your own interviewer training materials.
  • Route the note to a private coaching channel instead of a DM, or copy the hiring manager on the same message.
  • Narrow the scope to a single team, role, or interview stage (for example, only onsites, only phone screens).

FAQs

Will interviewers who did not interview yesterday still get a note?
No. Anyone with no candidate interviews on yesterday's calendar is quietly skipped, so quiet days do not produce empty coaching messages.
How does the workflow know which meetings are interviews?
It looks at each meeting's title and attendees. Anything that reads like an interview, has an external attendee, or matches your usual naming pattern is picked up. You can tighten or loosen these rules in the prompt.
Can I preview the coaching notes before they go to my team?
Yes. Point the Slack step at your own DM for the first few runs while you tune the tone and rubric, then flip it back to the interviewers once you are happy.
What happens if an interview has no transcript in Metaview yet?
That interview is skipped and the workflow moves on, so a recording that is still processing never blocks the rest of your team's coaching.
Does this only work with Google Calendar?
This starter uses Google Calendar, which is the fastest path to yesterday's interview list. You can adapt it to another calendar tool by swapping the calendar step in the workflow.

Related templates

Turn website roof inspection requests into JobNimbus leads

New roof inspection requests from your website form land in JobNimbus within a minute, with no duplicate records and nothing retyped by your team.

JobNimbus
Google Forms
Slack
Agentic Task
Triage new Jira Service Management requests before anyone opens them

Every new customer request gets a priority, triage labels, a friendly reply with the right help article, and a Slack ping only when it is truly urgent.

Jira Service Management
Jira
Slack
Agentic Task
Risk-check every dependency upgrade pull request in GitHub

When a bot opens a version bump pull request, we read the real documentation for that exact version and tell you whether it is safe to merge.

Context7
GitHub
Slack
Agentic Task
Launch an Ironclad contract when a HubSpot deal is won

The moment a deal hits Closed Won, the right contract starts in Ironclad, the link lands on the deal, and your sales channel hears who owns the next step.

Ironclad
HubSpot
Slack
Agentic Task
Weekly Ironclad contract renewal digest in Slack and Asana

Every Monday, find contracts renewing or expiring in the next 90 days, post a ranked digest to Slack, and open Asana tasks for the ones that need a decision now.

Ironclad
Slack
Asana
Agentic Task
Turn repeat support tickets into draft help articles

Every Friday, spot the questions your team keeps answering by hand and get a ready-to-review help article drafted from real fixes.

Jira Service Management
Confluence
Slack
Agentic Task

Turn yesterday's interviews into today's interviewer coaching.

Connect Metaview, Google Calendar, and Slack once, and every weekday morning your team gets a short, specific note on what they did well and what to try next.