Available Events
Subscribe to any combination of these event types when creating or updating a webhook. Every delivery is a POST request whose JSON body has four top-level fields:id (the event ID), type (the event type), payload (event-specific data, shown per event below), and timestamp (ISO 8601 creation time). The examples below omit id for brevity.
Email Events
event
Fired when an email is successfully sent from a campaign sequence.
event
Fired when an email fails to send (SMTP error, authentication issue, etc.).
event
Fired when a sent email bounces back.
event
Fired when a recipient opens a tracked email.
Reply Events
event
Fired when a reply is received and matched to a lead/campaign.
event
Fired when a reply is categorized (by AI or manually). Since 2026-09-21 the automatic categorizer also reports how sure it was and the intents it read in the reply:
categoryConfidence (0 to 1 on the stored category), intents (a probability per intent: asks_question, wants_call, referral, mentions_pricing, objection_timing, objection_competitor, wants_more_info, hostile, plus _intent, the finer category answer such as not_now or wrong_person, _unsubscribe and _urgency), and categorizedBy. All three are null for a manual categorization.Campaign Events
event
Fired when a campaign transitions to active status.
event
Fired when a campaign is paused.
event
Fired when all leads in a campaign have been processed.
Lead Events
event
Fired when a new lead is created (via API, CSV import, or manually).
event
Fired when a lead’s information is updated.