CHATBOTS
Teams 'Who Owns This Service?' Bot
An MS Teams bot that answers 'who owns service X' by reading the service catalog and the most recent commits, then replying in-channel with the owner, team, and last contributor.
How it runs
The automated pipeline, trigger to output.
- TriggerTeams message mentions the bot with a service nameMicrosoft Teams
- ActionLook up the service in the Postgres catalogPostgres
- LogicBranch: catalog hit vs. no match
- ActionFetch the repo's 5 most recent commitsGitHub
- OutputReply in the Teams thread with owner, team, and last committerMicrosoft Teams
What it does
When a teammate types a question like 'who owns the billing-api' in a Teams channel, this bot looks up the named service in your Postgres service catalog and cross-checks the most recent GitHub commits to that repo. It replies with the registered owner, the owning team, the on-call alias, and the person who last touched the code.
When to use it
Use it when engineers waste time pinging the wrong people about a service during incidents or change requests. It turns tribal knowledge into a one-message lookup, right where people already work.
How it works
- 1A Teams message mentioning the bot triggers the flow and the service name is extracted from the text.
- 2The catalog query runs against Postgres to find the matching service row (owner, team, on-call).
- 3If no row matches, the bot replies asking the user to check the spelling or register the service.
- 4The GitHub step pulls the last 5 commits to the mapped repo to identify the most recent contributor.
- 5The bot posts a formatted reply in the same Teams thread with owner, team, on-call alias, and last committer.
Set it up
What you configure once, before turning it on.
- 1Connect Microsoft TeamsChannels, chats, files.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.
