AI AGENTS
Weekly Competitor Watch Digest to Slack
On a weekly schedule, researches a tracked list of competitors for new launches, pricing changes, and press, then posts a deduplicated, sourced digest to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionSearch each competitor for recent newsPerplexity
- LogicDedupe and filter to material updates
- ActionGroup and summarize with citationsOpenAI
- OutputPost digest to Slack channelSlack
What it does
Runs a standing competitive-intelligence sweep across the companies you track and delivers one clean Slack digest a week. Each item is summarized in a sentence with a source link, so the team sees only what actually moved.
When to use it
Use it when you maintain a competitor list and want a low-noise, recurring pulse instead of ad-hoc Googling. Ideal for product, sales, and founder updates where stale or duplicate news erodes trust in the report.
How it works
- 1A weekly schedule fires the workflow with the configured competitor list.
- 2Perplexity searches each competitor for the past seven days of launches, pricing, and press, returning sourced results.
- 3A logic step deduplicates against last run's items and filters out anything immaterial or already reported.
- 4If no material updates remain, the workflow exits without posting to avoid empty noise.
- 5OpenAI groups the surviving items by competitor and writes a one-line, cited summary per item.
- 6The formatted digest is posted to the designated Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect PerplexitySearch-grounded answers with citations.
- 2Connect OpenAIModels, embeddings, files.
- 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 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.