AI AGENTS
Weekly Literature Scan into a Notion Knowledge Base
On a weekly schedule an agent searches academic and web sources for new work on your tracked topics, deduplicates against your knowledge base.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionRead tracked topics from Notion configNotion
- ActionSearch recent sources per topic (Exa)Exa
- LogicDedupe against existing knowledge-base entries
- ActionWrite structured cited summaries (OpenAI)OpenAI
- OutputFile new pages in Notion knowledge baseNotion
What it does
Maintains a living literature review. Each week the agent searches the web and academic sources for new papers, reports, and articles on the topics your team tracks, summarizes each with a citation, and files them as structured pages in a Notion knowledge base, skipping anything already captured.
When to use it
When a research, policy, or product team needs to stay current on a defined set of topics and wants a curated, deduplicated, cited archive rather than a noisy feed.
How it works
- 1A weekly scheduled trigger fires.
- 2The agent reads the list of tracked topics from a Notion config page.
- 3Exa runs neural searches for recent sources on each topic.
- 4A logic step dedupes results against existing entries in the Notion database by title and URL.
- 5OpenAI writes a structured summary for each new source: key finding, method, and relevance, with citation.
- 6Each summary is created as a new page in the Notion knowledge base.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 2Connect ExaNeural search across the web.
- 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 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.