IT OPS

Self-Service Keep-or-Release Nudge for Idle Seats

When Snowflake flags a user as idle past threshold, emails the user directly asking them to keep or release the seat.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps4
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule finds newly idle usersSnowflakeSnowflake
  • ActionEmail user a keep-or-release promptGmailGmail
  • LogicResolve response or expire grace window
  • OutputWrite seat disposition to Airtable queueAirtableAirtable

What it does

Instead of IT guessing, this workflow asks the actual seat holder. It emails idle users a simple keep-or-release prompt, honors their choice, and reclaims silently abandoned seats once the response window closes — no manager chasing required.

When to use it

Use it when you want reclamation to scale without a human reviewing every seat. It works best for self-serve tools where the user is the right decision-maker and a polite nudge clears most of the backlog.

How it works

  1. 1A daily schedule queries Snowflake for users newly crossing the idle threshold.
  2. 2For each, the flow emails the user via Gmail with a keep-or-release link and a stated grace window.
  3. 3A logic step waits for the response: keep marks the seat retained, release queues it for reclamation.
  4. 4If no response lands before the grace window expires, the seat defaults to the reclamation queue.
  5. 5The final disposition for every seat is written to Airtable for the deprovisioning team to action.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  2. 2
    Connect GmailRead, draft, send, label.
  3. 3
    Connect AirtableBases, tables, views, automations.
  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.