HR & RECRUITING

Polite Rejection Email on Trello Reject Move

When a recruiter moves a candidate card into the 'Reject' list, sends a courteous, role-specific rejection email via Outlook, archives the card.

CategoryHR & Recruiting
Enginesim
Difficultybeginner
Triggerevent
Steps6
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerTrello card moved to Reject listTrelloTrello
  • ActionRead candidate details from cardTrelloTrello
  • ActionSend respectful rejection email via OutlookOutlook
  • LogicCheck for future-fit label
  • ActionSet 90-day re-engage reminderGoogle CalendarGoogle Calendar
  • OutputArchive the Trello cardTrelloTrello

What it does

Handles the closing step of the pipeline gracefully. Moving a card to 'Reject' triggers a warm, personalized rejection email to the candidate, archives the Trello card to keep the board clean, and—when the recruiter tags the card as a future fit—sets a calendar reminder to re-engage them down the line.

When to use it

When you want every declined Indeed applicant to get a timely, respectful response without a recruiter writing each email by hand, and you want to keep a warm bench of near-miss candidates.

How it works

  1. 1A Trello card entering the 'Reject' list triggers the flow.
  2. 2The candidate's name, email, and applied role are read from the card.
  3. 3An Outlook email sends a respectful, role-specific rejection note.
  4. 4A logic step checks for a 'future-fit' label on the card.
  5. 5If present, a Google Calendar reminder is created to revisit the candidate in 90 days.
  6. 6The Trello card is archived to clear the active board.

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 Google CalendarEvents, attendees, availability.
  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.