HR & RECRUITING

Slack Deactivation and Channel Cleanup on Departure

Triggered by an HR webhook, this workflow deactivates a departing employee's Slack account, removes them from private channels, and confirms the cleanup back to HR.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHRIS webhook for confirmed departureHTTP webhook
  • LogicVerify signature and last day reached
  • ActionDeactivate Slack accountSlack
  • ActionRemove from private channels and groupsSlack
  • OutputNotify manager and return confirmationSlack

What it does

Cuts a departing employee's Slack access cleanly. On a signed webhook from your HRIS, it deactivates the user's Slack account, removes them from private channels and groups so they lose access to ongoing conversations, and reposts any pending direct-message handoff note to their manager. It returns a confirmation listing exactly what was removed.

When to use it

Use it the moment HR confirms a last working day, especially for sensitive departures where lingering Slack access is a real risk. Good for organizations whose HRIS can emit a webhook but where Slack admin steps are otherwise done by hand.

How it works

  1. 1An HRIS webhook with the employee identifier and last-day fires the trigger.
  2. 2A logic step verifies the payload signature and that the last day has passed.
  3. 3The workflow looks up the Slack user and deactivates the account.
  4. 4It removes the user from all private channels and member groups.
  5. 5It notifies the employee's manager in Slack of the deactivation.
  6. 6A structured confirmation of channels removed is returned to the HRIS via the webhook response.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  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.