AI AGENTS
Slack /research slash command returns a sourced brief in-thread
A team types /research with a question in Slack; the agent decomposes it, gathers cross-checked sources, and posts a tight, cited brief back into the same thread within a minute.
How it runs
The automated pipeline, trigger to output.
- Trigger/research slash command in SlackSlack
- LogicSplit question into key facts to establish
- ActionMulti-engine search + de-duplicatePerplexity
- ActionCross-check sources, note disagreementsOpenAI
- LogicSet confidence; caveat low-agreement answers
- OutputPost cited brief in the Slack threadSlack
What it does
Gives every channel a research analyst on call. A teammate runs the /research slash command with any question, and the agent returns a concise, source-linked brief in the same Slack thread, no context-switch to another tool required.
When to use it
When questions come up live in standups, deal rooms, or leadership channels and you need a fast, defensible answer without leaving Slack. Ideal for quick competitive checks, "is this true" verifications, and pre-meeting prep.
How it works
- 1A user invokes /research with a question via the Slack slash command.
- 2The agent splits the question into the 2-4 facts it must establish to answer well.
- 3It runs a search across multiple engines and de-duplicates overlapping results.
- 4An LLM step cross-checks sources against each other and notes where they disagree.
- 5A logic step decides confidence: high-agreement answers ship as-is; low-agreement answers ship with an explicit caveat.
- 6The brief, with bullet findings and clickable source links, is posted back into the originating Slack thread.
Set it up
What you configure once, before turning it on.
- 1Connect PerplexitySearch-grounded answers with citations.
- 2Connect Brave SearchWeb, news, image, video search.
- 3Connect OpenAIModels, embeddings, 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 AI Agents workflows
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Datadog Bill Spike Attribution Agent
When a daily Datadog cost check detects a spend jump, an agent attributes the increase to the specific services and metric types driving it and posts a ranked breakdown to Slack.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
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.