Event Types
Drippi sends webhooks for the following automation events:| Event Type | Description | Triggers |
|---|---|---|
cold_dm.sent | Cold DM successfully sent | When an initial message is sent to a new lead |
followup.sent | Follow-up message sent | When a follow-up message is sent to an existing lead |
reply.received | Lead replied to automation | When a lead responds to your automation messages |
automation.paused | Automation automatically paused | When system pauses automation due to limits or issues |
automation.out_of_leads | Automation has no more leads | When automation runs out of available leads to contact |
Common Payload Structure
All webhook events share a common base structure:Base Fields
| Field | Type | Description |
|---|---|---|
event | string | The webhook event type |
user_id | string | Drippi user ID who owns the automation |
created_at | string | ISO 8601 timestamp when the event occurred |
data | object | Event-specific payload data |
Event Details
cold_dm.sent
Triggered when a cold DM is successfully sent to a new lead.followup.sent
Triggered when a follow-up message is sent to an existing lead.reply.received
Triggered when a lead replies to your automation messages.automation.paused
Triggered when an automation is automatically paused by the system (not by user action).automation paused - too many messagesautomation paused - account is not verifiedautomation paused - daily_message_limit_reacheddisconnected pause
automation.out_of_leads
Triggered when an automation runs out of available leads to contact.Lead Data Structure
Thelead_data field contains detailed Twitter profile information for the lead:
Handling Webhook Events
Example Event Handler
Idempotency
Implement idempotency to handle duplicate webhook deliveries:Next Steps
- Webhook Verification - Learn how to verify webhook signatures
- Webhooks Overview - Get started with webhooks