Zintara reply.received webhook: payload and matching limits

Define the decision

In the reviewed inbox code, reply.received is dispatched when a message is classified as a reply and matched to a lead. The payload contains email, subject and leadId. It is not a complete inbox-message export or proof of sales qualification.

Work through the procedure

1. Subscribe an active endpoint to reply.received.
2. Verify the signature over the exact raw request body before parsing.
3. Validate the event and required data fields.
4. Store the notification durably before acknowledging it.
5. Use a separate reviewed process for retrieving context or assigning a sales outcome.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

{"event":"reply.received","data":{"email":"[email protected]","subject":"Re: evaluation","leadId":"00000000-0000-4000-8000-000000000001"},"timestamp":"2026-09-16T10:00:00Z"}

Read the result

The subject is message content supplied by an external sender, so render it as text and avoid using it as a command or unique identifier. A reply can be negative or merely informational.

Check before moving on

1. Confirm the event arrives only at the intended integration.
2. Test repeated notification handling without creating repeated sales tasks.

Limits and next action

The current envelope has no stable event ID or reply-body field, and dispatch is best-effort. Do not promise complete history or exactly-once delivery from this webhook alone.

Source: Zintara product context