Webhook events - Reply API Documentation

This page lists all webhook event types supported by the Reply API. Each event links to its payload schema on the Webhook event payloads page.

To create or manage webhook subscriptions, see the Webhooks API. To retrieve supported event types programmatically, use the List supported event types endpoint.

When creating or updating a subscription, pass the event name as the eventType value.

Email engagement

Event	When it fires	Payload
`email_sent`	Reply sends an email from a sequence step.	View
`email_opened`	A recipient opens a tracked email.	View
`email_link_clicked`	A recipient clicks a tracked link in an email.	View
`email_replied`	Reply detects an incoming reply to a sequence email, or a direct email reply not tied to a sequence. Fires once per detected reply.	View
`reply_categorized`	An email reply is assigned a category automatically or by a user.	View
`email_bounced`	A sent email bounces or is rejected by the recipient’s mail server.	View
`email_auto_reply`	An incoming message is identified as an auto-reply or out-of-office message.	View

Email account health

Event	When it fires	Payload
`email_account_connection_lost`	A connected mailbox can no longer authenticate, such as after an OAuth revocation or password change.	View
`email_account_error`	A mailbox reports an IMAP or SMTP error, such as an authentication failure, send failure, or rate limit.	View

LinkedIn

Event	When it fires	Payload
`linkedin_connection_request_sent`	Reply sends a LinkedIn connection request on behalf of a user.	View
`linkedin_connection_request_accepted`	A previously sent LinkedIn connection request is accepted.	View
`linkedin_message_sent`	Reply sends a LinkedIn message or InMail.	View
`linkedin_message_replied`	A contact replies in a LinkedIn conversation.	View
`linkedin_reply_categorized`	A LinkedIn conversation is assigned a category.	View
`linkedin_account_alerts`	A LinkedIn account requires attention, such as a disconnected Sales Navigator account, usage limits, or low InMail credits.	View
`linkedin_comment_posted`	Reply posts an AI-generated comment on a contact’s most recent LinkedIn post.	View
`linkedin_comment_skipped`	A “Comment on a recent post” step skips a contact instead of posting a comment; the payload carries the reason.	View

Calls

Event	When it fires	Payload
`contact_called`	A call with a contact reaches a final status, such as connected, missed, voicemail, or logged.	View

Contact lifecycle

Event	When it fires	Payload
`contact_replied`	A contact enters the replied state — a reply is detected on any channel (email, LinkedIn, or SMS), or the contact is manually marked as replied. Channel-agnostic status signal.	View
`contact_finished`	A contact completes or exits a sequence.	View
`contact_opted_out`	A contact opts out through an unsubscribe link, manual action, or Do Not Contact setting.	View

Sequence automation

Event	When it fires	Payload
`autopilot_stopped`	An evergreen sequence’s autopilot is disabled.	View