← ClaudeAtlas

exa-webhooks-eventslisted

Build event-driven integrations with Exa using scheduled monitors and content alerts. Use when building content monitoring, competitive intelligence pipelines, or scheduled search automation with Exa. Trigger with phrases like "exa monitor", "exa content alerts", "exa scheduled search", "exa event-driven", "exa notifications".
ComeOnOliver/skillshub · ★ 46 · Web & Frontend · score 80
Install: claude install-skill ComeOnOliver/skillshub
# Exa Webhooks & Events ## Overview Build event-driven integrations around Exa neural search. Exa is a synchronous search API (no native webhooks), so this skill covers building async patterns: scheduled content monitoring with `searchAndContents`, similarity alerts with `findSimilarAndContents`, new content detection using date filters, and webhook-style notification delivery. ## Prerequisites - `exa-js` installed and `EXA_API_KEY` configured - Queue system (BullMQ/Redis) or cron scheduler - Webhook endpoint for notifications ## Event Patterns | Pattern | Mechanism | Use Case | |---------|-----------|----------| | Content monitor | Scheduled `searchAndContents` with `startPublishedDate` | New article alerts | | Similarity alert | Periodic `findSimilarAndContents` + diff | Competitive monitoring | | Content change | Re-search + compare result sets | Update tracking | | Research digest | Scheduled `answer` + email/Slack | Daily briefings | ## Instructions ### Step 1: Content Monitor Service ```typescript import Exa from "exa-js"; import { Queue, Worker } from "bullmq"; const exa = new Exa(process.env.EXA_API_KEY!); interface SearchMonitor { id: string; query: string; webhookUrl: string; lastResultUrls: Set<string>; intervalMinutes: number; searchType: "auto" | "neural" | "keyword"; } const monitorQueue = new Queue("exa-monitors", { connection: { host: "localhost", port: 6379 }, }); async function createMonitor(config: Omit<SearchMonitor, "lastResultUrls