HR & RECRUITING

Stale Candidate Re-Engagement Nudge

Runs daily to find candidates stuck in a screening stage past your SLA, then nudges the owning recruiter in Slack and emails a polite status update to the candidate so no one…

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionQuery Airtable for SLA-breached candidatesAirtableAirtable
  • LogicSplit recruiter nudges vs. candidate updates
  • ActionPost stalled-candidate digest to recruitersSlack
  • OutputEmail holding note and log run in AirtableGmailGmail

What it does

Keeps your pipeline honest by catching candidates who have sat in the same stage too long. Each day it scans for records that breached your stage SLA, reminds the recruiter to act, and sends the candidate a courteous "still reviewing" note so your employer brand stays intact.

When to use it

Use this when candidates routinely stall between screening and scheduling and your team needs a safety net. It is ideal for protecting time-to-respond commitments and reducing silent drop-off.

How it works

  1. 1A daily schedule triggers the workflow each morning.
  2. 2The flow queries Airtable for candidates whose stage has not changed within the SLA window for that stage.
  3. 3A branch splits results: candidates needing a recruiter nudge versus those also due a candidate-facing update.
  4. 4Slack posts a digest to each recruiter listing their stalled candidates and how long each has waited.
  5. 5Gmail sends an automated holding note to candidates past the response SLA, and the run timestamp is logged on each record in Airtable.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  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.