AI AGENTS
Weekly Sector Scan Brief from Primary Sources
Every Monday, an agent searches the web for the week's developments in a target sector, fetches and reads the underlying primary sources.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule (Mon 6am)
- ActionSearch recent sector itemsExa
- ActionScrape source pages to markdownFirecrawl
- LogicFilter low-relevance / duplicates
- ActionDraft cited briefOpenAI
- OutputPublish brief to NotionNotion
What it does
Each week this agent assembles a desk-ready intelligence brief on a sector you define (e.g. "enterprise AI infrastructure"). It runs neural search to surface recent items, reads the actual source pages rather than summaries, and writes a structured brief with an executive summary, key developments, and a citation list — published as a Notion page.
When to use it
For analysts, founders, or strategy teams who need a consistent Monday-morning read on a market without manually trawling news. Best when you want primary-source grounding (filings, blog posts, releases) instead of aggregator headlines.
How it works
- 1A scheduled trigger fires every Monday at 6am.
- 2Exa runs neural search over the past 7 days for your sector keywords and returns ranked result URLs.
- 3Firecrawl scrapes the top results into clean markdown so the agent reads full text, not snippets.
- 4The agent (OpenAI) clusters items into themes, drafts an executive summary, and pulls direct quotes with source attribution.
- 5A filter drops low-relevance or duplicate items below a confidence threshold.
- 6The finished brief is written to a new Notion page in your research database.
Set it up
What you configure once, before turning it on.
- 1Connect ExaNeural search across the web.
- 2Connect FirecrawlCrawl, scrape, structured extract.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect NotionPages, databases, comments.
- 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.