HR & RECRUITING

Discord Alert for Double-Booked Interview Panels

When a new interview event is added to the hiring team's Google Calendar, it checks every required panelist for overlapping meetings and posts a conflict alert to the recruiting…

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew interview event on hiring calendarGoogle CalendarGoogle Calendar
  • LogicExtract required panelists from attendees
  • ActionCheck each panelist calendar for overlapsGoogle CalendarGoogle Calendar
  • LogicBranch only if a conflict exists
  • OutputPost conflict alert to recruiting Discord channelDiscordDiscord

What it does

Detects when a freshly scheduled interview collides with an existing commitment for any required panelist, and raises the conflict in Discord while there is still time to reschedule.

When to use it

Use it when interview panels are booked across busy calendars and conflicts only surface the morning of, forcing awkward candidate reschedules. Ideal for teams running interviews off a shared Google Calendar.

How it works

  1. 1A new event on the hiring Google Calendar triggers the flow.
  2. 2Parse the attendee list to identify each required panelist.
  3. 3For each panelist, query their calendar for events overlapping the interview window.
  4. 4A logic step decides: if any panelist has an overlap, mark a conflict; otherwise exit quietly.
  5. 5Post a structured Discord message to the recruiting channel listing the candidate, the conflicted panelists, and the clashing meetings so the coordinator can swap a slot.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect DiscordCommunity channels + voice + bots.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.