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.
Body
Equal to the webhook-id HTTP header. Stable across retries —
use for receiver-side deduplication.
Event time (when the business action happened), set once at
publish and replayed on retries. NOT the dispatch time — that
lives in the webhook-timestamp HTTP header and is recomputed
per send.
Common case mirrors the send events: one sequence_id plus a
newly_stopped flag. The optional additional_* arrays only
appear when a single inbound matched more than one outbound
sequence (rare; parallel campaigns to the same recipient).
Response
Receiver acknowledged.