> ## Documentation Index
> Fetch the complete documentation index at: https://docs.origami.chat/llms.txt
> Use this file to discover all available pages before exploring further.

# Reply received

> Origami POSTs this event when an inbound email or LinkedIn DM
matches one of your active sequences. We also stop any matched
sequences that should pause on reply; `data.newly_stopped` tells
you whether THIS event's sequence transitioned to stopped.

Branch on `data.channel` to handle email vs LinkedIn.

**`outreach_target` is the replier.** `sender` is the identity
they replied TO (your mailbox or LinkedIn account).

**Multi-match case.** A single inbound can legitimately match
more than one sequence if you ran parallel campaigns to the
same recipient. The primary match goes on `sequence_id` +
`newly_stopped`; tail matches appear on
`additional_matched_sequence_ids` (and
`additional_newly_stopped_sequence_ids` when relevant). Both
`additional_*` fields are **absent** from the payload in the
common single-match case.

**Default in the picker:** on.




## OpenAPI

````yaml /openapi-webhooks.yaml webhook sequence.reply.received
openapi: 3.1.0
info:
  title: Origami Webhooks
  version: '1.0'
  description: |
    Outbound events Origami POSTs to your servers when sequencer activity
    happens. Verify the `webhook-signature` header on every request
    before acting on the payload — see the signatures guide. Receivers
    MUST dedupe on the `webhook-id` header. Configure endpoints in
    **Settings → Developers → Webhooks**.
servers: []
security: []
paths: {}

````