Relation New Webhook

Unipile new_relation (v1) / relation.new (v2): a connection was accepted. Stamps invite_accepted_at on any matching waiting sequence.

Why this exists (need.md §3.2/§3.3): today acceptance is detected by the DM gate spending a real profile view per waiting lead per day — roughly 200/day on a busy seat against a 120/day budget that ONLY discovery reads and is never blocked by, so the failure is silent: discovery stops enriching and scores leads blind while outreach looks healthy. Unipile does the polling for this event on their side at randomised intervals, so it costs us nothing against LinkedIn. Documented latency is up to 8 hours.

Always 200, even when nothing matched. Most relation events are the seat's own organic networking, and a non-2xx makes Unipile retry a delivery that was correctly a no-op.

Idempotent by construction: record_acceptance is write-once, so a re-delivered event cannot walk the timestamp forward.