Skip to main content ホーム クリエイター comeonoliver skillshub apollo-webhooks-events
apollo-webhooks-events 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".
インストールへ移動 Skills Marketplace コミュニティが作成したAIスキルを発見・探索
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ComeOnOliver/skillshub --skill apollo-webhooks-eventsコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Zipをダウンロード ダウンロード中... このリポジトリの他の Skills Review product and feature risk before an AI coding agent starts implementation.
Use Xquik for X data and confirmation-gated X actions: tweet search, user lookup, follower export, media download, monitors, webhooks, MCP, and SDK workflows.
Canton Network open-source ecosystem guide covering DAML SDK, Canton runtime, and Splice applications. Use when working with Canton Network, DAML smart contracts, or building decentralized applications.
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.0.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> compatible-with claude-code, codex, openclaw tags ["saas","apollo","webhooks"]
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.
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 ;
}
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
new
Date
lastSyncAt
const
contacts
filter
(c : any
new
Date
updated_at
if
length
0
console
log
`Found ${newChanges.length} contact changes since ${state.lastSyncAt} `
for
const
of
await
handleContactChange
lastSyncAt
new
Date
toISOString
return
async
function
handleContactChange
contact : any
console
log
`Contact updated: ${contact.name} (${contact.email} ) — stage: ${contact.contact_stage_id} `
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.
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 ,
}));
}
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 ;
}
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.
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.
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 ,
priority : 'high' ,
status : 'open' ,
});
return { taskId : data.task .id , type : data.task .type , dueDate : data.task .due_date };
}
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
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 () };
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);
}
});
cron.schedule ('*/15 * * * *' , async () => {
const activeSequenceIds = ['seq-1' , 'seq-2' ];
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
Next Steps Proceed to apollo-performance-tuning for optimization.
