HR & RECRUITING

Stale Candidate Follow-up Nudge from Trello

Runs daily to find Trello cards stuck in screening or interview lists past an SLA threshold, posts a digest to Slack tagging the card owner.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily weekday morning schedule
  • ActionPull Screen and Interview cards with activity datesTrelloTrello
  • LogicFlag cards past the response SLA
  • ActionSend holding email to overdue candidatesOutlook
  • OutputPost overdue-card digest to SlackSlack

What it does

Keeps candidates from going cold. Each morning it scans your hiring board for cards that have sat untouched too long, builds a digest of who's overdue and where, posts it to the recruiting Slack channel, and sends a holding email to candidates whose last update predates your response SLA.

When to use it

When good Indeed candidates slip through the cracks because cards stall mid-pipeline. Use it to enforce response-time SLAs and protect your employer brand with timely candidate communication.

How it works

  1. 1A daily schedule triggers the flow each weekday morning.
  2. 2Trello cards in the 'Screen' and 'Interview' lists are pulled with their last-activity dates.
  3. 3A logic step flags cards whose last activity exceeds the SLA (for example, 3 business days).
  4. 4For flagged candidates, an Outlook holding email is sent acknowledging the wait.
  5. 5A Slack digest is posted listing every overdue card, its list, and its owner so the team can clear the backlog.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect TrelloKanban boards for everything.
  2. 2
    Connect OutlookMail, calendar, contacts.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.