Handle Linkedin Profile View Signal

Template placeholders

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

• {{PROFILE_OWNER}} — Full name of the team member whose LinkedIn is tracked (e.g. "Jane Doe")
• {{INTERNAL_DOMAINS}} — Your own company domain(s) (e.g. "acme.com")
• {{NOTIFICATIONS_CHANNEL}} — Slack channel reference for outcome/debug posts
• {{ENRICHMENT_TOOL}} — Primary contact-enrichment tool available to the agent
• {{FALLBACK_SCRAPER}} — Fallback LinkedIn profile scraper (e.g. an Apify actor)
• {{CRM}} — Your CRM (e.g. HubSpot)
• {{CRM_HYGIENE_SKILL}} — Sub-skill reference: how to create/update companies & contacts in your CRM
• {{EXISTING_RELATIONSHIP_SKILL}} — Sub-skill reference: handling accounts with an open/lost deal
• {{HIGH_INTENT_SKILL}} — Sub-skill reference: potential-MQL scoring & routing
• {{AWARENESS_SKILL}} — Sub-skill reference: net-new ICP awareness logging
• {{TIER_SCALE}} — Your lead-score tiers, low→high (default: Bronze / Silver / Gold / Diamond)
• {{SOLE_SIGNAL_CAP_TIER}} — Max tier when a profile view is the only 1st-party signal (default: Silver)
• {{COOLDOWN_WINDOW}} — Same-session dedup window (default: 1 hour)

Overview

This skill fires when your profile-view tracker (e.g. LeadShark) detects a new view on {{PROFILE_OWNER}}'s LinkedIn profile. Goal: behave exactly like a website visit — resolve the viewer, run the same ICP gate, register them as a known contact only when they pass, and feed them into the MQL pipeline.

The golden rule: the CRM is never polluted. Only a viewer who is identified + company-resolved + not-internal + not-customer + ICP-matched ever reaches a CRM write. Everyone else is silently discarded or logged to org memory only.

The webhook trigger handles only one thing: ignoring events that are not new.profile.visit. All logic lives here.

Channel rule: When outreach is triggered by a LinkedIn profile view signal, keep it LinkedIn-only. Do not create email steps. The contact came to you via LinkedIn — stay on that channel.

---

Step 1 — Parse & Validate

The payload arrives as text. Extract the fields listed in references/webhook-payload.md. Key ones:

• data.profile_owner — confirm this is {{PROFILE_OWNER}}; if not, stop silently.
• data.lead.is_anonymous — if true, stop immediately and silently. No enrichment, no CRM writes, no memory writes, no channel post. Anonymous viewers (LinkedIn Premium private mode) are fully discarded.
• data.lead.title is the LinkedIn headline — it often contains no company. Never treat it as a company name.
• data.visit.id is a stable unique token per visit; data.lead.actor_id identifies the person across visits.

---

Step 1.5 — Idempotency (Before Any Enrichment)

Profile-view trackers emit multiple visit records for a single viewing session — same person, same actor_id, different visit.id each time. Run two checks before paying for enrichment:

Read the org-level memory note "Profile Views — {{PROFILE_OWNER}} — Processed Visit IDs" (create it if it doesn't exist). Each entry stores: visit.id | actor_id | timestamp.

Check 1 — Exact retry guard: If data.visit.id is already in the note → duplicate webhook redelivery → stop silently. No enrichment, no CRM, no memory writes, no channel post.

Check 2 — Per-person session cooldown: If data.lead.actor_id appears in the note with a timestamp within the last {{COOLDOWN_WINDOW}} → same viewing session split into multiple events → stop silently.

Otherwise: Append data.visit.id | data.lead.actor_id | data.visit_timestamp to the note and continue. Keep only the most recent ~200 entries.

Critical: A genuine repeat view from the same person outside the cooldown window has the same actor_id but passes both checks and re-scores as a stronger signal. This is intentional — the cooldown only collapses rapid same-session duplicates, never real repeat intent.

---

Step 2 — Resolve Viewer Identity & Company (Mandatory)

Identifying the person is not the same as resolving the company. You must have both before proceeding.

Do NOT infer the company from the LinkedIn headline. Headlines like "Product | Strategist | Building 0→1" are not company names.

1. Run {{ENRICHMENT_TOOL}} on linkedin_username (or linkedin_url) to retrieve: current company name, company domain, confirmed job title, and country/location.
2. If {{ENRICHMENT_TOOL}} does not return a confident company name + domain — even if it identified the person — you MUST run {{FALLBACK_SCRAPER}} on the profile URL to obtain the current company, domain, and country. The fallback is required here, not optional. A guessed company is worse than UNRESOLVED.
3. You must exit this step with: viewer full name, confirmed title, company name, company domain (both required), country.

Exit condition — UNRESOLVED: If after both tools you still cannot confidently determine a company name + domain:

• Set outcome = UNRESOLVED
• Append the raw data (name, title, linkedin_url, visit.id, timestamp) to the org memory note "Profile Views — {{PROFILE_OWNER}} — Unresolved Viewers"
• Do NOT write anything to {{CRM}}, account memory, or the channel
• Stop.

---

Step 3 — Internal Check

If the resolved domain is {{INTERNAL_DOMAINS}} or any other internal domain → stop silently. No CRM, no memory, no channel post.

---

Step 4 — CRM Relationship Check (Mirror Your Website-Visit Skill)

Look up the company in your workspace + {{CRM}}:

• Active partner → stop silently. No CRM writes, no scoring, no channel post. Partner accounts are managed by their owner — do not create noise.
• Current customer (Closed Won) → set outcome = EXISTING CUSTOMER. Do NOT create or update any CRM records. Jump to Step 8.
• Active deal or Closed-Lost → open the {{EXISTING_RELATIONSHIP_SKILL}} sub-skill and follow it. After it returns, jump to Step 8 with outcome = EXISTING RELATIONSHIP.
• No existing relationship (net-new) → continue to Step 5.

---

Step 5 — ICP Check

Compare the company against your ICP segments.

• Not ICP → set outcome = NOT ICP. Do NOT create or update any CRM records. Do NOT write to account memory. Jump to Step 8.
• ICP match → continue to Step 6.

---