Apollo Webhooks EventsSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-08Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: apollo-webhooks-events description: 'Implement Apollo.io webhook and event-driven integrations. Use when receiving Apollo notifications, syncing data on changes, or building event-driven pipelines from Apollo activity. Trigger with phrases like "apollo webhooks", "apollo events", "apollo notifications", "apollo webhook handler", "apollo triggers". ' allowed-tools: Read, Write, Edit, Bash(gh:*), Bash(curl:*) version: 1.13.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - apollo - webhooks compatibility: Designed for Claude Code --- # 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. ```typescript // src/sync/contact-poller.ts import axios from 'axios'; const client = axios.create({ baseURL: 'https://api.apollo.io/api/v1', headers: { 'Content-Type': 'application/json', 'x-api-key': process.env.APOLLO_API_KEY! }, }); interface SyncState { lastSyncAt: string; // ISO timestamp } export async function pollContactChanges(state: SyncState) { const { data } = await client.post('/contacts/search', { sort_by_field: 'contact_updated_at', sort_ascending: false, per_page: 100, }); const lastSync = new Date(state.lastSyncAt); const newChanges = data.contacts.filter( (c: any) => new Date(c.updated_at) > lastSync, ); // A full page is not a complete incremental window. Paginate before moving // the watermark so newer changes cannot hide records still on later pages. if (data.contacts.length >= 100) { throw new Error('Incremental window reached one page; paginate before advancing sync state'); } if (newChanges.length > 0) { console.log(`Found ${newChanges.length} contact changes since ${state.lastSyncAt}`); for (const contact of newChanges) { await handleContactChange(contact); } state.lastSyncAt = newChanges .map((c: any) => c.updated_at) .sort() .at(-1) ?? state.lastSyncAt; } return newChanges; } async function handleContactChange(contact: any) { console.log(`Contact updated: ${contact.id} — stage: ${contact.contact_stage_id}`); // Sync to your CRM, database, or notification system } ``` ### 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. ```typescript // src/sync/stage-tracker.ts export async function getContactStages() { const { data } = await client.get('/contact_stages'); return data.contact_stages.map((s: any) => ({ id: s.id, name: s.name, order: s.display_order, })); } // Find contacts that moved to a specific stage export async function getContactsByStage(stageId: string) { const { data } = await client.post('/contacts/search', { contact_stage_ids: [stageId], sort_by_field: 'contact_updated_at', sort_ascending: false, per_page: 50, }); return data.contacts; } // Update a contact's stage export async function updateContactStage(contactId: string, stageId: string) { await client.put(`/contacts/${contactId}`, { contact_stage_id: stageId, }); } ``` ### Step 3: Monitor Sequence Engagement Poll sequence data for replies, bounces, and engagement events. ```typescript // src/sync/sequence-monitor.ts export async function checkSequenceEngagement(sequenceId: string) { const { data } = await client.post('/emailer_campaigns/search', { ids: [sequenceId], per_page: 1, }); const seq = data.emailer_campaigns?.[0]; if (!seq) return null; return { name: seq.name, active: seq.active, metrics: { scheduled: seq.unique_scheduled ?? 0, delivered: seq.unique_delivered ?? 0, opened: seq.unique_opened ?? 0, replied: seq.unique_replied ?? 0, bounced: seq.unique_bounced ?? 0, unsubscribed: seq.unique_unsubscribed ?? 0, }, rates: { openRate: pct(seq.unique_opened, seq.unique_delivered), replyRate: pct(seq.unique_replied, seq.unique_delivered), bounceRate: pct(seq.unique_bounced, seq.unique_scheduled), }, }; } function pct(num?: number, denom?: number): string { if (!denom) return '0%'; return `${(((num ?? 0) / denom) * 100).toFixed(1)}%`; } ``` ### Step 4: Create Tasks for Follow-Up Actions Use Apollo's Tasks API to create actionable follow-ups triggered by your polling logic. ```typescript // src/sync/task-creator.ts export async function createFollowUpTask(params: { contactId: string; type: 'call' | 'action_item' | 'email'; dueDate: string; note: string; assigneeId?: string; }) { const { data } = await client.post('/tasks', { contact_id: params.contactId, type: params.type, due_date: params.dueDate, note: params.note, user_id: params.assigneeId, // Apollo user ID to assign to priority: 'high', status: 'open', }); return { taskId: data.task.id, type: data.task.type, dueDate: data.task.due_date }; } // Example: auto-create call task when a sequence reply is detected async function onSequenceReply(contactId: string, sequenceName: string) { await createFollowUpTask({ contactId, type: 'call', dueDate: new Date(Date.now() + 24 * 60 * 60 * 1000).toISOString().split('T')[0], note: `Reply detected on sequence "${sequenceName}". Follow up immed
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__apollo-webhooks-events.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Apollo Webhooks Events skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Apollo Webhooks Events safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Apollo Webhooks Events access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Apollo Webhooks Events work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-08. The repository is watched, and a new audit runs when it changes — this is the first audit.