IT OPS
Reclaim agent that warns idle users before revoking seats
An agent reviews flagged idle SaaS seats, messages each holder a keep-or-release prompt, waits a grace period, and revokes seats from non-responders via the app's admin API.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook delivers flagged idle-seat batchHTTP webhook
- ActionAgent assesses each seat's safety to prompt
- ActionDM holders a keep-or-release prompt in SlackSlack
- LogicAfter grace period, split keepers from non-responders
- ActionRevoke seats for non-keepers via admin APIHTTP webhook
- OutputPost reclaim summary to IT channelSlack
What it does
This workflow handles reclamation with a human-friendly grace window. An agent takes the list of idle seats, reasons over each holder's role and usage history, sends a direct Slack message asking whether they still need the license, waits out a configurable grace period, and then revokes the seat from anyone who didn't respond or chose to release it.
When to use it
Use it when you want to reclaim seats without surprising active-but-quiet users. The agent's judgment plus the warning step avoids cutting off someone mid-project while still recovering genuinely dead licenses.
How it works
- 1A webhook delivers the flagged idle-seat batch from your audit run.
- 2The agent evaluates each seat against role and recent-activity signals to decide who is safe to prompt.
- 3It sends each holder a Slack keep-or-release message and records responses.
- 4After the grace period, a logic step splits responders from silent or release-it holders.
- 5An HTTP call to the SaaS admin API revokes seats for the non-keepers.
- 6The agent posts a reclaim summary to the IT channel.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More IT Ops workflows
Outlook Room Conflict Resolver with Approval Gate in Teams
When an Outlook room clashes, proposes a rebooking and asks the bumped meeting's organizer to approve the move in Microsoft Teams before any change is made.
Outlook Room Double-Booking Resolver with Auto-Rebook
Detects when two meetings claim the same Outlook room resource and automatically relocates the lower-priority meeting to a comparable free room.
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.
Reconcile SSO logins against expense spend to find unmanaged tools
Joins SSO usage data with expense/payment records in Snowflake to surface tools that are being used but not paid for, or paid for but never logged.
Indoor Air Quality Breach to Tenant Notice and Work Order
Listens for CO2, VOC, or humidity sensor alerts via webhook, and when a zone exceeds occupant-safety limits it emails affected tenants, opens a Monday remediation task.
Daily Building Anomaly Digest to MS Teams
Each morning queries BigQuery for the prior day's flagged sensor anomalies, summarizes them by site and system into a ranked briefing.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.