AI AGENTS
Slack-Triggered Vendor Comparison with Sourced Cells
A teammate posts a vendor-evaluation request in Slack; an agent researches the category and replies in-thread with a ranked, fully cited comparison table.
How it runs
The automated pipeline, trigger to output.
- TriggerSlack message mentions the agent with a vendor requestSlack
- LogicParse requirements into weighted criteria
- ActionFan out research across Exa and BraveExa
- ActionExtract facts and rank vendors with citationsOpenAI
- OutputReply with the ranked table in the Slack threadSlack
What it does
Someone drops a request into a Slack channel naming a category and the must-have requirements. The agent runs a research fan-out, builds a ranked comparison table where each fact carries an inline source link, and posts it back into the same thread so the whole team sees it.
When to use it
When vendor questions surface mid-conversation in Slack and you want an answer without leaving the channel or spinning up a doc. Best for quick shortlists and "who else is in this space" scans that the team can react to immediately.
How it works
- 1A Slack message in the watched channel mentioning the agent triggers the run, carrying the category and requirements as text.
- 2The agent parses the requirements into weighted criteria.
- 3It fans out queries to Exa and Brave Search and pulls the strongest sources.
- 4An OpenAI step extracts per-vendor facts, ranks vendors against the weights, and attaches a source URL to each cell.
- 5The agent posts the ranked table back into the originating Slack thread.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect ExaNeural search across the web.
- 3Connect Brave SearchWeb, news, image, video search.
- 4Connect OpenAIModels, embeddings, 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 AI Agents workflows
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.
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.
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.
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.
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.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.