Agent skill · software engineering · jeremylongshore
apify-webhooks-events
Implement Apify webhooks for Actor run notifications and event-driven
Why this skill is useful
Provides specific implementation patterns and event handling for Apify webhooks that the AI wouldn't reliably generate on its own.
What it needs
Requires apify-client, express installed locally. Requires apify account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Apify Webhooks & Events Overview Configure webhooks to receive notifications when Actor runs complete, fail, or time out. Apify supports both persistent webhooks (for all runs of an Actor) and ad-hoc webhooks (for a single run). Event-driven architecture is the recommended pattern for production Apify integrations. Prerequisites npm install apify-client in your project (and express if you build an HTTP handler) An API token in APIFYTOKEN — read it from the environment (process.env.APIFYTOKEN) or pass Authorization: Bearer $APIFYTOKEN on REST calls, never hard-code it A public HTTPS endpoint for Apify to POST to (use ngrok while developing) Familiarity with apify-sdk-patterns Event Types Event Fired When ------- ----------- ACTOR.RUN.CREATED A new Actor run starts ACTOR.RUN.SUCCEEDED Run finishes with SUCCEEDED status ACTOR.RUN.FAILED Run finishes with FAILED status ACTOR.RUN.ABORTED Run is manually or programmatically aborted ACTOR.RUN.TIMEDOUT Run exceeds its timeout ACTOR.RUN.RESURRECTED A finished run is resurrected Instructions Step 1: Create a Persistent Webhook Persistent webhooks fire for every run of an Actor. Set condition.actorId, list the eventTypes you care about, and shape the delivered body with payloadTemplate: The full payload template (all run fields) and the complete variable table are in payload templates & local testing. Step 2: Use Ad-Hoc Webhooks for Single Runs Ad-hoc webhooks are created at run time and fire only for that specific run — pass a webhooks array when starting the Actor: The equivalent REST/curl form is in payload templates & local testing. Step 3: Handle the Webhook Your endpoint must return a 2xx within 30 seconds, so acknowledge immediately and process asynchronously. On SUCCEEDED, fetch the dataset via defaultDatasetId; on FAILED/TIMEDOUT, pull the run log and alert: The full processWebhook switch (dataset fetch, log tail, oncall alerting) is in full implementation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/apify-webhooks-events