handle-linkedin-connection-request-signal

Template placeholders

Replace every {{...}} before enabling. See the setup checklist reference for the full setup list.

• {{PROFILE_OWNER}} — Team member whose inbound connection requests are processed
• {{CRM}} — Your CRM (e.g. HubSpot, Attio)
• {{INTERNAL_DOMAINS}} — Your company domain(s); requests from these stop silently
• {{VISIBILITY_CHANNEL}} — Slack channel that gets one visibility post per processed request
• {{CRM_HYGIENE_SKILL}} — Sub-skill reference: how to create/update companies & contacts in your CRM
• {{LEAD_SCORING_SKILL}} — Sub-skill reference: your lead scoring & qualification methodology (its normal MQL alerting stays on)
• {{REACTIVATION_SKILL}} — Sub-skill reference: how you handle closed-lost account reactivation (optional — skip the reactivation branch's owner notification if you don't have one)
• {{SELF_SERVE_THRESHOLD}} — Company profile below which accounts route self-serve rather than MQL (default: fewer than 50 employees AND ≤$10M raised)
• {{REACTIVATION_WINDOW}} — Minimum time since a closed-lost deal before a request counts as a reactivation signal (default: ~90 days)

Overview

This skill runs when someone sends {{PROFILE_OWNER}} a LinkedIn connection request. The requester reached out to YOU — this is a deliberate, active first-party intent signal, meaningfully stronger than a passive profile view. The job is: resolve + enrich the requester and their company, gate it, attach to CRM per standard hygiene, and score the signal.

Golden rule — the CRM is never polluted. Only a requester who is identified + company-resolved + not-internal + not-a-current-customer + ICP-matched ever reaches a CRM write. Everyone else is silently discarded or logged to account memory only.

The webhook trigger only validates + routes. All behavior lives here.

Payload shape

The routing trigger passes a single, already-deduplicated signal with the person's name, LinkedIn member id / URL, headline, and the invitation note (or null), plus a detection timestamp. Be robust to both a structured person object and a stringified context blob carrying the same fields.