Webhooks

lead_replied

An enrolled lead replied to a sequence email, and the enrollment was stopped as a result.

Narrower than message_received, and worth preferring for reply handling: auto-replies and out-of-office bounces pause the enrollment instead and do not fire this. Same payload shape as sequence_completed, with status: replied.

postWebhooklead_replied

Payload

eventstring

Event type. Also sent in the X-Webhook-Event header.

timestampstring date-time

When the event was delivered — not necessarily when it occurred.

webhook_idstring uuid

Delivery ID. Also sent as X-Webhook-ID. Use it to deduplicate retries.

organization_idstring uuid

Example payload

{
  "event": "contact_created",
  "data": {
    "status": "replied"
  }
}

Response

Return any 2xx to acknowledge. A non-2xx or a timeout is treated as a failed delivery and retried with backoff up to your configured max_retries.

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.