apollo-webhooks-events
Process Apollo.io events through API polling or third-party webhooks.
Install
mkdir -p .claude/skills/apollo-webhooks-events && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9371" && unzip -o skill.zip -d .claude/skills/apollo-webhooks-events && rm skill.zipInstalls to .claude/skills/apollo-webhooks-events
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Implement Apollo.io webhook and event-driven integrations.Key capabilities
- →Implement polling for contact changes
- →Track contact stage transitions
- →Monitor sequence engagement metrics
- →Automate task creation for follow-ups
- →Schedule periodic sync tasks
How it works
Since Apollo lacks native webhooks, this skill implements polling mechanisms that query the API for updates at defined intervals. It then processes these changes to trigger downstream actions like CRM updates or task creation.
Inputs & outputs
When to use apollo-webhooks-events
- →Build polling services for Apollo data updates
- →Handle contact state changes via automation
- →Sync Apollo data with external event triggers
- →Develop reactive workflows for lead management
About this skill
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.
// 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,
);
if (newChanges.length > 0) {
console.log(`Found ${newChanges.length} contact changes since ${state.lastSyncAt}`);
for (const contact of newChanges) {
await handleContactChange(contact);
}
state.lastSyncAt = new Date().toISOString();
}
return newChanges;
}
async function handleContactChange(contact: any) {
console.log(`Contact updated: ${contact.name} (${contact.email}) — 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.
// 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.
// 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.
// 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 immediately.`,
});
}
Step 5: Set Up a Cron-Based Sync Service
// src/sync/scheduler.ts
import cron from 'node-cron';
import { pollContactChanges } from './contact-poller';
import { checkSequenceEngagement } from './sequence-monitor';
const syncState = { lastSyncAt: new Date(Date.now() - 60 * 60 * 1000).toISOString() };
// Poll every 5 minutes for contact changes
cron.schedule('*/5 * * * *', async () => {
try {
const changes = await pollContactChanges(syncState);
console.log(`Sync complete: ${changes.length} changes`);
} catch (err) {
console.error('Contact sync failed:', err);
}
});
// Check sequence engagement every 15 minutes
cron.schedule('*/15 * * * *', async () => {
const activeSequenceIds = ['seq-1', 'seq-2']; // from your config
for (const id of activeSequenceIds) {
const stats = await checkSequenceEngagement(id);
if (stats && parseInt(stats.rates.replyRate) > 10) {
console.log(`High reply rate on "${stats.name}": ${stats.rates.replyRate}`);
}
}
});
console.log('Apollo sync scheduler started');
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
Error Handling
| Issue | Resolution |
|---|---|
| Missed changes between polls | Reduce poll interval or use sort_by_field: contact_updated_at |
| Rate limited during polling | Add backoff, reduce per_page, increase poll interval |
| Duplicate task creation | Track processed contact IDs in a Set or database |
| Third-party webhook delays | Zapier/Pipedream polling intervals vary (1-15 min on free tiers) |
Resources
- List Contact Stages
- Search for Contacts
- Create a Task
- Search for Sequences
- Apollo + Zapier Integration
Next Steps
Proceed to apollo-performance-tuning for optimization.
When not to use it
- →When real-time push webhooks are strictly required
- →When high-frequency polling exceeds rate limits
Prerequisites
Limitations
- →Polling latency depends on the chosen interval
- →Risk of hitting rate limits with frequent polling
How it compares
It provides a polling-based workaround for the lack of native webhooks, enabling event-driven behavior through scheduled API requests.
Compared to similar skills
apollo-webhooks-events side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| apollo-webhooks-events (this skill) | 0 | 26d | Caution | Intermediate |
| telegram-bot-builder | 106 | 6mo | Review | Intermediate |
| n8n-expression-syntax | 6 | 4mo | No flags | Beginner |
| reddit-api | 3 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
telegram-bot-builder
davila7
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.
n8n-expression-syntax
czlonkowski
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.
reddit-api
alinaqi
Reddit API with PRAW (Python) and Snoowrap (Node.js)
mcporter
openclaw
Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.
calcom-api
calcom
Interact with the Cal.com API v2 to manage scheduling, bookings, event types, availability, and calendars. Use this skill when building integrations that need to create or manage bookings, check availability, configure event types, or sync calendars with Cal.com's scheduling infrastructure.
instantly-webhooks-events
jeremylongshore
Implement Instantly webhook signature validation and event handling. Use when setting up webhook endpoints, implementing signature verification, or handling Instantly event notifications securely. Trigger with phrases like "instantly webhook", "instantly events", "instantly webhook signature", "handle instantly events", "instantly notifications".