Agent skill · marketing growth · jeremylongshore
apollo-webhooks-events
Implement Apollo.io webhook and event-driven integrations.
Why this skill is useful
Provides specific API integration patterns and polling scripts for Apollo.io that the AI wouldn't reliably generate on its own.
What it needs
Requires node installed locally. Requires apollo, make, pipedream, zapier account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Apollo Webhooks & Events Overview Build event-driven integrations with Apollo.io. Apollo does not have a native webhook system like Stripe — instead, you build real-time sync by polling the API for changes or using third-party webhook platforms (Zapier, Pipedream, Make) that trigger on Apollo events. This skill covers both approaches plus the Contact Stages and Tasks APIs for workflow automation. Prerequisites Apollo account with master API key Node.js 18+ with Express For polling: a scheduler (cron, Cloud Scheduler, BullMQ) For webhook platforms: Zapier/Pipedream/Make account Instructions Step 1: Poll for Contact Changes Since Apollo lacks native webhooks, poll the Contacts Search API for recently updated records. Step 2: Track Contact Stage Changes Apollo has a Contact Stages system. Use the List Contact Stages endpoint to get stage IDs, then filter contacts by stage. Step 3: Monitor Sequence Engagement Poll sequence data for replies, bounces, and engagement events. Step 4: Create Tasks for Follow-Up Actions Use Apollo's Tasks API to create actionable follow-ups triggered by your polling logic. Step 5: Set Up a Cron-Based Sync Service Output Contact change poller with timestamp-based incremental sync Contact stage tracking and updates via the Stages API Sequence engagement monitoring with reply/bounce/open rates Task creation API for automated follow-ups Cron-based scheduler for periodic sync Examples For a contact-stage automation, run the poller with a persisted watermark and an idempotency record keyed by Apollo contact ID plus update timestamp. Process one small staging window, record only IDs, stage IDs, counts, and redacted failure reasons, then prove that replaying the same window creates neither a duplicate CRM update nor a duplicate follow-up task. Paginate any full result window before advancing the watermark. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/apollo-webhooks-events--15b0cd