CHATBOTS
Slack 'Who Owns This Service' Q&A Bot
Answers ad-hoc Slack questions about who owns a service, its runbook link, and SLA tier by querying your service catalog and replying in-thread with a sourced answer.
How it runs
The automated pipeline, trigger to output.
- TriggerEngineer mentions the bot or runs the slash command in SlackSlack
- ActionExtract the service name and question intent from the messageOpenAI
- ActionQuery the Postgres service_catalog for matching servicePostgres
- LogicIf no confident match, list top candidates and ask user to choose
- OutputReply in-thread with owner, on-call, runbook, and SLASlack
What it does
Gives engineers an instant, self-serve answer to 'who owns checkout-api?' or 'what's the SLA on the billing worker?' without pinging a channel. A teammate asks the bot in Slack, it looks the service up in your Postgres service catalog, and replies in the same thread with the owning team, on-call contact, runbook URL, and SLA tier.
When to use it
When ownership knowledge lives in someone's head and incidents stall while people hunt for the right team. Best for orgs with a maintained catalog table but no good front door to it.
How it works
- 1An engineer @-mentions the bot or uses a slash command in Slack with a service name or fuzzy phrase.
- 2The agent extracts the intended service and intent (owner, runbook, or SLA) from the message.
- 3It queries the Postgres `service_catalog` table, matching exact and near names.
- 4If no confident match is found, it returns the top candidates and asks the user to pick.
- 5It posts a formatted reply in-thread with owner, Slack handle, runbook link, and SLA, citing the catalog row's last-updated date.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect OpenAIModels, embeddings, files.
- 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.