HR & RECRUITING

Post-Interview Scorecard Chaser Before Debrief

Runs a few hours after each interview block and emails any panelist who hasn't submitted their scorecard yet.

CategoryHR & Recruiting
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled run after interview window
  • ActionRead roster + submitted scorecardsAirtableAirtable
  • LogicDiff assigned vs. submitted to find missing
  • ActionDraft personalized reminder per laggardOpenAI
  • OutputEmail reminders to missing panelistsGmailGmail

What it does

On a schedule it scans the day's completed interviews, checks which scorecards are still missing against the assigned panel, and sends each laggard a personalized nudge with a direct link to the candidate's scorecard form. It stops chasing once a panelist submits.

When to use it

Use it when debriefs routinely stall because two of five interviewers forgot to write up notes. Recruiters spend hours manually pinging people; this automates the chase and timestamps who is blocking the loop.

How it works

  1. 1A schedule fires a few hours after the daily interview window closes.
  2. 2The flow reads the interview roster and the submitted-scorecard list from the intake table.
  3. 3A logic step diffs assigned panelists against submitters to build the missing list.
  4. 4For each missing panelist it drafts a short, friendly reminder naming the candidate and the deadline.
  5. 5It sends those reminders by email.
  6. 6It writes a status row marking who is still outstanding so the recruiter sees the blockers at a glance.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect GmailRead, draft, send, label.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.