The installed content script runs on permitted LinkedIn pages. Full-network import and authenticated profile enrichment require an Introd session, while the page script can still inspect visible LinkedIn content before that server-side work occurs.
Last verified against current extension and API source on August 11, 2026.
Prerequisites
- The Introd-provided extension build is loaded.
- You are connected to Introd in the extension.
- LinkedIn is signed in in the same Chrome profile.
- LinkedIn can load its connections page.
Two different data behaviors
Contextual capture while browsing
With the shipped default settings, Enable extension and Auto-capture profile context are on. As LinkedIn pages change, the extension looks for visible profile links and nearby identity or relationship text. It can store local profile-view signals, upload unsynced signals on a schedule, and submit derived profile fields for enrichment while signed in to Introd. Signed-out use can still leave local signals in Chrome storage.
This behavior is not limited to a full-network sync or to a person’s main profile page. Current selectors cover visible identity containers on profiles, feeds, comments, messaging surfaces, hover cards, organization people pages, events, discovery results, and list items. Captures are deduplicated for a period, but page processing continues as visible content changes.
Full-network connection import
Choosing Start Sync starts a resumable import from LinkedIn’s connections page. After that start, an incomplete run can automatically continue every few minutes or after progress becomes stale. The extension can reuse an existing connections tab or create one in the background without replacing the page you are viewing.
In testing build 1.8.4, popup copy that says Nothing is sent automatically refers only to outreach. It is not a data-transfer boundary: profile signals, diagnostics, enrichment requests, and connection-import batches can be sent automatically. The control matrix below describes the implemented behavior.
Start a sync
- Open any LinkedIn page.
- Open the Introd extension popup.
- Confirm that the popup recognizes the LinkedIn session.
- Choose Start Sync.
- Watch the popup for the initial progress.
The popup reports imported connections, the LinkedIn-visible total when available, progress, and last-sync time. Closing the connections tab is not a stop control: an incomplete run can recreate or reuse a background tab. Choose Pause Sync to stop automatic full-network resume.
Sync states
Connection data used
When available on processed LinkedIn surfaces, contextual capture and connection import can derive:
- name and profile identifier or URL
- headline, current and past work, education, company, and location when visible on the current profile or identity container
- profile image
- first-degree or mutual-connection context
- sync checkpoint and progress information
The documented profile payload contains identity and relationship fields, not a dedicated message-body field. However, current relationship parsing can fall back to text from the surrounding identity container, and those containers include LinkedIn messaging surfaces. Introd has not completed a runtime data-flow attestation proving that message-page text cannot leave the browser.
Do not treat Pause Sync as a privacy control for ordinary browsing. If you do not want Introd code to inspect a sensitive LinkedIn page, disable the extension in chrome://extensions before opening that page.
Stop or limit each behavior
On-page path context
On a supported LinkedIn identity, the extension can offer Open Introd paths or display path and connector context only when Introd returns usable graph evidence.
The extension does not send an introduction request. Use First Warm Introduction Draft to save a reviewed draft.
Limitations
- LinkedIn renders large networks incrementally, so imported totals can remain below the visible total.
- A partial sync is not a completed sync, even though already imported records remain available.
- Missing role, company, image, or mutual data can produce an incomplete contact.
- A synced target can still have no verified warm path.
- LinkedIn interface changes can interrupt row detection until the extension is updated.
Verify in Introd
Open Network Setup or Integrations. Confirm the LinkedIn status, imported count, and last-sync time before relying on the data. 
