Agent skill · marketing growth · jeremylongshore
serpapi-webhooks-events
Implement SerpAPI asynchronous searches and scheduled change detection without inventing a webhook callback contract. Use when building long-running searches or SERP monitoring. Trigger with "build SerpAPI async monitoring".
Why this skill is useful
Provides specific implementation patterns for SerpApi async search and monitoring that the AI wouldn't reliably generate on its own.
What it needs
Requires node-cron installed locally. Requires serpapi account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
SerpAPI Async Search and Scheduled Monitoring Overview Use documented async submission plus Searches Archive polling, or scheduled synchronous searches, with explicit state, budgets, and reconciliation. Prerequisites An engine and use case that justify background processing or repeated monitoring Poll deadline, schedule, allowance and throughput budgets, checkpoint store, and downstream owner Data classification, retention decision, and sanitized state-machine fixtures Tool Discipline Use Read, Glob, and Grep to inspect jobs and consumers, WebFetch to verify async and archive contracts, and Write or Edit for state machines, schedules, checkpoints, fixtures, and redacted receipts. Current Contract SerpAPI documents async=true to submit without holding the connection and the Searches Archive API to retrieve the search by ID. Status can move through queued or processing to success or error. async must not be combined with nocache and is not for accounts with Ludicrous Speed. The public contract does not define a generic callback webhook for completed searches. Authentication Use SERPAPIKEY in the server-side submitter and poller. Persist search IDs and safe state, never key-bearing archive URLs. Authenticate and authorize any downstream notification endpoint using its own documented mechanism. Instructions 1. Confirm async is supported for the engine/account and that polling improves the use case over a bounded synchronous call. 2. Define states SUBMITTED, QUEUED, PROCESSING, SUCCEEDED, FAILED, EXPIRED, and TIMEDOUT with terminal behavior. 3. Submit with a parameter mapping containing "async": true; persist the search ID, normalized request hash, owner, deadline, and attempt budget. 4. Poll through the official client's archive method or documented archive endpoint with increasing delay, jitter, and a hard deadline. 5. On success, validate and normalize once; make downstream processing idempotent by search ID and payload version. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/serpapi-webhooks-events