IT OPS
Cross-System Access Reconciliation Report
On a weekly schedule, compares the authoritative roster against actual account membership across SaaS systems, flags hires with missing or orphaned access.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly scheduled reconciliation
- ActionLoad roster and expected-access mapPostgres
- ActionQuery actual Slack membershipSlack
- ActionQuery group memberships via internal directoryCustom MCP server
- LogicDiff expected vs actual access
- ActionWrite reconciliation snapshot to sheetGoogle Drive
- OutputPost discrepancy summary to governance channelSlack
What it does
Proves that what should be true about access actually is. It pulls the authoritative hire roster, then queries each connected SaaS system for who actually has accounts and group memberships, diffs the two, and produces a report listing every hire who is missing expected access or holds access they shouldn't.
When to use it
Use this for periodic access governance — catching provisioning that never completed and stale grants that drift in over time. Especially valuable ahead of security audits or SOC 2 reviews where you must demonstrate least-privilege enforcement.
How it works
- 1A weekly schedule starts the reconciliation.
- 2The flow loads the authoritative roster and expected-access map from Postgres.
- 3It queries Slack for actual workspace and channel membership.
- 4It queries the internal directory via custom MCP for group memberships across other SaaS systems.
- 5It diffs expected versus actual, producing missing-access and orphaned-access lists.
- 6It writes the reconciliation snapshot to a Google Sheet for the audit trail.
- 7It posts the summary with counts and the top discrepancies to the IT governance channel.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect Custom MCP serverConnect any MCP-compatible tool you own.
- 4Connect Google DriveDocs, sheets, slides, files.
- 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
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.