Skip to main content

New Connection Trigger Now Updates the Matched Contact

The New Connection trigger now writes connection status straight back to the matched contact — and returns three new payload fields for anyone building custom logic around a connection.

Daniel Marr

What's New

  • Three new fields on the trigger payload: is_relationshipinvitation_status, and network_distance (returns FIRST_DEGREE for new connections)
  • A non-blocking write-back: if a contact was matched, the trigger now stamps that record after it sends — Is Connection → true, Invitation Status → cleared, Network Distance → FIRST_DEGREE
  • Previously, the trigger fired and stopped there — the matched contact was never touched, and every workflow had to add its own Update Contact step to record the connection

Why It Matters

  • One less step in every New Connection workflow — connection status lands on the contact automatically
  • The write-back runs after the trigger sends, so it never adds delay or blocks the rest of your workflow
  • The new payload fields give you connection context — relationship status, invitation state, network distance — without a separate lookup

Read the New Connection documentation