HR & RECRUITING

Departure-Triggered Access Mirror and Deprovision

When an employee is marked as departing, it reverses their original provisioning checklist into revoke tasks, assigns them to the same owners, and confirms deprovisioning in Slack.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEmployee marked departing (HRIS webhook)HTTP webhook
  • ActionLoad original provisioning itemsPostgreSQLPostgres
  • LogicInvert grants into revoke tasks with due dates
  • ActionCreate revoke tasks for original ownersAsanaAsana
  • OutputPost deprovisioning summary to security + HRSlack

What it does

Uses the provisioning record you built at hire time as the authoritative list of what to take back at departure. It generates one revoke task per granted item, routes each to the same owning team, and tracks completion so nothing stays granted after someone leaves.

When to use it

Use it when offboarding is risky and inconsistent — orphaned accounts, unreturned laptops, lingering door access — and you want deprovisioning to be the exact mirror of what was originally granted.

How it works

  1. 1A webhook fires from your HRIS when an employee is marked as departing, carrying their employee ID and last day.
  2. 2The flow loads that person's original provisioning items from Postgres.
  3. 3A logic step inverts each grant into a revoke action and computes a due date tied to the last working day.
  4. 4It creates an Asana revoke task per item assigned to the original owning team.
  5. 5A deprovisioning summary is posted to the security and HR Slack channel, listing every access being pulled and its owner.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect AsanaTasks, projects, milestones — everywhere.
  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.