IT OPS

Self-Service Reclaim Email for Idle Users

Detects users idle in a SaaS app past the threshold and emails each one a keep-or-release link; unanswered seats after the deadline are auto-flagged for removal.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly idle-sweep schedule
  • ActionQuery idle users from SSO logsPostgreSQLPostgres
  • ActionEmail keep-or-release link to each userGmailGmail
  • LogicSplit keep vs release/no-response
  • OutputSend removal roster to SlackSlack

What it does

This workflow finds users who haven't logged into a tracked app recently and, instead of cutting them off, sends each a polite email asking whether they still need the seat. Non-responses past the deadline roll up into a removal list, so reclamation is humane and defensible.

When to use it

Use it in orgs where abruptly revoking access causes friction. The self-service step shifts the keep/release decision to the user, dramatically shrinking IT's manual follow-up while still recovering genuinely dead seats.

How it works

  1. 1A weekly schedule starts the sweep.
  2. 2The flow queries Postgres for users whose last SSO login exceeds the idle threshold.
  3. 3Each idle user is emailed a personalized keep-or-release message with a response deadline.
  4. 4The flow waits for responses; a logic step separates Keep replies from silence and Release replies.
  5. 5Users who chose Release or never answered are written to a reclamation roster, and IT is notified in Slack with the final removal list.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect GmailRead, draft, send, label.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.