Webhooks

email.replied

Fires the first time a recipient replies to an email you sent.

The email.replied event fires the first time a recipient replies to an email you sent. The reply arrives as an inbound message on one of your receiving domains and is matched back to the original send (via its threading headers, or the latest email sent to the replying address).

Repeat replies to the same email do not re-fire the event — each reply is still stored as its own received email (with an email.received event) and linked to the sent email via reply_to_email_id.

{
  "type": "email.replied",
  "created_at": "2026-06-22T23:41:12.126Z",
  "data": {
    "email_id": "49a3999c-0ce1-4ea6-ab68-afcd6dc2e794",
    "received_email_id": "4ef9a417-02e9-4d39-ad75-9611e0fcc33c",
    "from": "recipient@example.com",
    "subject": "Re: Sending this example",
    "occurred_at": "2026-06-22T23:41:11.894Z"
  }
}

Payload

typestringoptional

The event type that triggered the webhook.

created_atstringoptional

ISO 8601 timestamp when the webhook event was created.

dataobjectoptional

Event-specific data. The fields below live inside this object.

data.email_idstringoptional

The id of the sent email that was replied to.

data.received_email_idstringoptional

The id of the received reply. Fetch its content from GET /emails/receiving/:id — including the AI-classified reply intent (category).

data.fromstringoptional

The replying sender's address.

data.subjectstringoptional

The reply's subject line.

data.occurred_atstringoptional

ISO 8601 timestamp when the reply was recorded.

Replies also flip the sent email's status/last_event to replied and can trigger automations via the email.replied engagement trigger.

This is one of several events MailBlastr can deliver. See the full list of webhook event types.