HR & RECRUITING

Offboarding Checklist Verification Sweep

On a daily schedule, re-checks every recently offboarded employee against live system state and flags any account that is still active so revocations never silently fail.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerschedule
Steps7
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionQuery employees offboarded in last 14 daysAirtableAirtable
  • ActionCheck Outlook account enabled stateOutlook
  • ActionCheck GitHub org membershipGitHubGitHub
  • LogicCompare expected vs. actual per system
  • ActionFlag mismatches on employee recordAirtableAirtable
  • OutputPost exceptions report to security channelSlack

What it does

Closes the trust gap in offboarding: instead of assuming a revocation worked, it independently verifies it. Each day it pulls everyone offboarded in the last 14 days and queries the actual systems to confirm their accounts are truly disabled, then raises an alert for anything still live.

When to use it

Use it as the safety net behind any deprovisioning process. API calls fail, admins forget, accounts get re-enabled — this sweep catches lingering access before it becomes a security finding or an audit failure.

How it works

  1. 1A daily schedule fires the sweep.
  2. 2It queries Airtable for employees offboarded in the trailing 14 days.
  3. 3For each, it checks whether the Outlook account is still enabled.
  4. 4It checks whether the user still belongs to the GitHub org.
  5. 5A logic step compares expected (revoked) vs. actual state per system.
  6. 6Any mismatch is written back to the employee record as "Verification failed".
  7. 7A consolidated exceptions report is posted to the security channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect OutlookMail, calendar, contacts.
  3. 3
    Connect GitHubRepos, issues, pull requests, actions.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.