CHATBOTS
Weekly Ownership Coverage Audit to Slack
Each week, cross-checks the service catalog against the live service inventory and posts a Slack report of unowned services, missing runbooks, and SLA gaps with direct fix links.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionPull the live service inventory from GitHubGitHub
- ActionPull current ownership rows from the Postgres catalogPostgres
- LogicDiff inventory vs catalog to find unowned, no-runbook, and SLA gaps
- ActionWrite this week's coverage snapshot for trend trackingPostgres
- OutputPost the grouped coverage report with fix links to SlackSlack
What it does
Gives platform leads a weekly scorecard of ownership hygiene. It compares the catalog against the actual set of deployed services, then posts a Slack report highlighting services with no owner, no runbook link, or no SLA tier set, plus how coverage changed week over week.
When to use it
When you want a recurring, visible accountability signal rather than discovering gaps mid-incident. Good for platform or SRE teams driving an ownership-completeness goal.
How it works
- 1A weekly schedule fires.
- 2It pulls the live service inventory from GitHub (repos or a manifest of deployed services).
- 3It pulls the current catalog rows from Postgres.
- 4A logic step diffs the two to find unowned services, missing runbooks, and unset SLA tiers, and computes the delta versus last week's snapshot.
- 5It writes this week's coverage snapshot back to Postgres for trend tracking.
- 6It posts a formatted Slack report grouping each gap type with links to fix each entry.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Chatbots workflows
Discord Onboarding Completion to CRM Sync
The moment a member finishes Discord onboarding, captures their submitted profile answers, creates or updates a contact in HubSpot.
Discord FAQ-Gated Role Concierge
Greets each new Discord member in a private onboarding thread, walks them through required FAQ steps one at a time.
Discord FAQ Free-Text Answer Grader
When a member submits a free-text answer in their onboarding thread, an agent grades it against the canonical FAQ knowledge base, replies with targeted feedback.
Discord verify-button onboarding via web form webhook
Receives a completed external verification form by webhook, matches it to the Discord account, grants the verified role, and confirms back to the member in Discord.
Discord intro-gated role granting concierge
Watches your #introductions channel, uses AI to confirm a new member's intro is genuine and complete, then auto-assigns the verified Member role and welcomes them.
Daily Discord Digest of Repeated WAF False-Positive Reports
Each morning, scans logged Discord WAF reports in Postgres, groups them by the Cloudflare rule that keeps firing.
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.