Replies Overview
Replies Overview
When a lead replies to a campaign, MachFive POSTs an email.replied webhook. Your system answers with Send a reply. Adding the webhook and checking its signature are in Webhooks.
Owners and admins create the API key. See Getting Started. AI replies bot is a reasonable name.
Plans
API keys are on every plan. Webhooks and POST /api/v1/replies need a plan with sending.
email.replied
data.lead.list_lead_id is what you send back to answer in this thread.
| Field | Description |
|---|---|
step | Sequence step the lead replied to. |
automated | true for an out-of-office reply or another automatic reply. Skip those. A bot that answers them will write back to a vacation message. |
untracked | true when the reply was not tied to a sequence step. The text is still the lead's reply, and you answer it the same way when list_lead_id is set. |
subject | Subject of the reply. |
text | The lead's own reply, with the quoted history removed. |
lead.list_lead_id | Set when the reply is placed on a list. null only when MachFive knows the person and cannot place them on a list. Skip a null id. POST /api/v1/replies needs that id, and there is no thread to answer. |
lead | id, email, and fields from the list row. |
campaign | { id, name } of the campaign, or null. |
list | { id, name } of the list, or null. |
occurred_at | When the reply happened (ISO 8601). |
{
"id": "msg_a1b2c3d4e5f60718293a4b5c6d7e8f90",
"type": "email.replied",
"created_at": "2026-11-12T22:15:00.000Z",
"workspace_id": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa",
"data": {
"step": 1,
"automated": false,
"untracked": false,
"subject": "Re: Quick question",
"text": "Yes, send the deck over.",
"lead": {
"id": "11111111-1111-1111-1111-111111111111",
"list_lead_id": "22222222-2222-2222-2222-222222222222",
"email": "ada@example.com",
"fields": {
"First Name": "Ada",
"Last Name": "Lovelace",
"Company": "Analytical Engines",
"Email": "ada@example.com"
}
},
"campaign": { "id": "cccccccc-cccc-cccc-cccc-cccccccccccc", "name": "Q1 Outbound" },
"list": { "id": "dddddddd-dddd-dddd-dddd-dddddddddddd", "name": "Directors" },
"occurred_at": "2026-11-12T22:14:58.000Z"
}
}The outer id, type, created_at, and workspace_id are the webhook envelope.
Keeping the conversation going
Each new message from the lead is a new email.replied, with a new id and a new webhook-id. Answer each one with the same list_lead_id. A retry of a delivery you already accepted reuses that webhook-id. Skip it, as described in Webhooks.
Opt-outs
Send a reply will not email a lead who has opted out or unsubscribed. That includes a lead tagged Not interested. The response is 409 CONFLICT:
{
"error": "CONFLICT",
"message": "This lead has unsubscribed and cannot be emailed.",
"detail": { "reason": "unsubscribed" },
"request_id": "9f1c0b3a-0000-4000-8000-000000000000"
}An opt-out uses the same status, with message "This lead has opted out and cannot be emailed." and detail.reason opted_out.