IT OPS
Onboarding Access Completion Verifier and Nudge
On a new hire's start date, verifies every required account was actually created across systems and nudges IT about any gaps before the employee logs in.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily start-date morning schedule
- ActionLoad today's hires and expected accessPostgres
- ActionVerify Teams account and licenseMicrosoft Teams
- ActionVerify drive access is liveGoogle Drive
- LogicCompile per-hire gap report
- OutputNudge IT on gaps or post all-clearSlack
What it does
Closes the loop on onboarding by confirming provisioning actually succeeded. On the start date it checks each required system for a live account, builds a gap list, and chases the missing items so the hire is not blocked on day one.
When to use it
Use this as a safety net behind any provisioning flow. Account creation can silently fail on seat limits or sync delays; this catches those before the employee notices and files a frustrated ticket.
How it works
- 1A scheduled trigger runs early on each business morning.
- 2A Postgres action loads the list of hires whose start date is today and their expected access profile.
- 3A Microsoft Teams action checks whether each user's account and license actually exist.
- 4A Google Drive action verifies their home folder and shared-drive access are live.
- 5A logic step compiles a per-hire gap report of anything missing.
- 6If gaps exist, a Slack action pings the assigned IT owner with the exact missing items; if clean, it posts an all-clear to #it-onboarding.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect Microsoft TeamsChannels, chats, files.
- 3Connect Google DriveDocs, sheets, slides, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More IT Ops workflows
Recurring Sensor Fault Root-Cause Investigator
On a schedule, an agent reviews recent Monday work orders and BigQuery telemetry to identify equipment with repeating faults, drafts a root-cause hypothesis with a recommended fix.
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.
Agentic Inactive-Seat Reclamation Review
An agent investigates each idle SaaS seat by correlating SSO login gaps with HR status and ticket history, classifies it as reclaim, hold, or escalate, and drafts a reasoned…
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.
Approved-Seat Deprovision Execution
Fires when an IT approver confirms a seat for removal, then executes deprovisioning via the IdP API and logs the action to an audit table and a Linear cleanup ticket.
HVAC Anomaly Detection to Severity-Routed Work Orders
Ingests building HVAC telemetry via webhook, flags out-of-band temperature, pressure, or runtime readings.
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.