Direct answer: LinkedIn is a native Finta integration delivered through the first-party Finta Chrome extension. After the user enables page context and grants LinkedIn site permission, Aurora can use the visible text of the active LinkedIn page when the user sends a request. Finta also supports an optional LinkedIn Connections CSV import for point-in-time network mapping. This is not an official LinkedIn API integration or continuous background synchronization.
Finta can use selected LinkedIn page context alongside CRM, deal, and imported network evidence to evaluate a possible warm path. A LinkedIn connection is evidence of access, not evidence of relationship strength or a person's willingness to make an introduction.
Current status
| Connection detail | Current evidence |
|---|---|
| Connection model | Native Finta Chrome extension plus optional Connections import |
| LinkedIn Connections import | Code-backed point-in-time snapshot |
| Finta Chrome page context | Code-backed, first-party, and user-invoked per site |
| Continuous LinkedIn synchronization | Not supported or claimed |
| Controlled production import receipt | Pending |
| Controlled LinkedIn page-context receipt | Pending |
| External LinkedIn write action | Not part of this workflow |
Finta classifies LinkedIn as Native because the supported browser workflow is delivered by Finta's own Chrome extension. The optional Connections import is a separate point-in-time input. Page content is read on demand from the active tab only after the user enables Use page, grants site permission, and sends the Aurora request.
What is documented and what Finta verified
Finta's current source supports the following import, browser, network, and relationship tools. No public claim should convert these into continuous LinkedIn API access.
| Tool or capability | Purpose | Finta evidence |
|---|---|---|
| Connections.csv import | Create a Finta Network from a first-degree connections export | Code-backed; controlled production import pending |
| Chrome Use page | Send the active page URL, title, and extracted text with an Aurora prompt | Code-backed; controlled LinkedIn page receipt pending |
| search_network_contacts | Search imported network contacts | Code-backed; known-contact receipt pending |
| search_contacts and get_contact | Compare the candidate with Finta CRM | Code-backed Finta tools |
| search_deals and get_deal | Connect the target to an active capital process | Code-backed Finta tools |
| propose_send_email | Optionally prepare an introduction request through a separately connected mailbox | Code-backed confirmation flow; owner consent still required |
Setup and proof path
- Open Finta Networks and select New LinkedIn network.
- Open LinkedIn's data-export workflow from the Finta dialog.
- In LinkedIn, request the Connections data through Settings, Data privacy, and Download your data.
- Download and extract the archive when LinkedIn makes it available.
- Name the new Finta Network and upload Connections.csv.
- Confirm that the file is CSV and no larger than 10 MB, then create the network.
- Reconcile a small known sample and the final imported row count before describing the import as successful.
- For selected-page context, install the official Finta Chrome extension and sign in.
- Open the specific LinkedIn profile or company page the user wants Aurora to consider.
- Turn on Use page and approve Chrome's permission request for that origin if needed.
- Send the Aurora prompt and verify the returned URL, title, and expected page text.
- Keep network search, page context, and owner consent separate in the resulting warm-path decision.
Flagship workflow
Target investor to credible path to human-owned introduction request
The relationship-intelligence layer is the evidence that sits between a possible path and a trustworthy request for help.
- Start with a named investor or firm.
- Search imported Finta Networks for matching people and companies.
- Show the source network and whether the result comes from an owned or shared network.
- Treat the imported connection as a path candidate, not proof of relationship quality.
- Compare candidates using verified interactions, CRM history, recency, and explicit owner knowledge when available.
- Name every evidence gap and stale-snapshot risk.
- Ask the relationship owner to confirm whether the path is real and an introduction is appropriate.
- Prepare the request only after that human confirmation, and retain email confirmation before sending.
Sample prompts
Search my imported networks for people connected to the selected fund. Show the source network and evidence available for each candidate. Do not treat a LinkedIn connection as a warm relationship.Use this selected LinkedIn profile as context, compare it with Finta CRM and Networks, and tell me whether I already have a credible path. Do not create or update records.For this target investor, rank possible introduction paths by verified interaction evidence. List what the relationship owner must confirm before I ask for an introduction.
Expected output
The output specification below describes the evidence a useful result should contain. It is not presented as a live tool receipt unless the verification ladder says otherwise.
| Output field | Expected evidence |
|---|---|
| Target | Name, company, and selected page URL when available |
| Source network | Network name, owner, access type, and snapshot status |
| Path candidate | Matching person and relationship route |
| Verified interaction evidence | CRM history, known interaction, recency, or explicit owner note |
| Evidence gap | What Finta cannot infer from the connection snapshot |
| Owner confirmation | The person who must confirm relationship strength and willingness |
| Recommended next step | Human-owned path validation or direct outreach |
| Introduction request | Not prepared until owner confirmation is complete |
Permissions and limitations
- LinkedIn's export covers first-degree connections and can omit email addresses when the connection has not allowed access.
- CSV or vCard exports may not support every extended character or field.
- The Finta import is a point-in-time snapshot and does not update automatically.
- Re-import is required to reflect later LinkedIn changes.
- Finta accepts a CSV up to 10 MB, and no current credit price should be published without checking the live policy.
- Missing email addresses are represented internally with non-deliverable placeholders and must never be treated as sendable addresses.
- A default relationship score from import must not be marketed as proof of a strong tie.
- Chrome optional site permissions are requested one origin at a time after the user invokes Use page.
- Finta does not automate LinkedIn messages, invitations, or profile changes through this workflow.
- A connection or mutual is not consent to make an introduction or lend reputation.
Verification ladder
| Evidence level | Evidence | State |
|---|---|---|
| Level 0 | LinkedIn export and Chrome permission documentation reviewed | Complete, August 22, 2026 |
| Level 1 | Finta import, parser, extension, and page-context source inspected | Complete, August 22, 2026 |
| Level 2 | Controlled Connections.csv imported in production | Pending |
| Level 3 | Imported row count reconciled with a known sample | Pending |
| Level 4 | Known connection returned by search_network_contacts | Pending |
| Level 5 | Missing-email and placeholder suppression verified | Pending |
| Level 6 | Per-site Chrome permission granted on a controlled LinkedIn page | Pending |
| Level 7 | Expected URL, title, and page text received by Aurora | Pending |
| Level 8 | No LinkedIn write or background extraction confirmed | Pending |
| Level 9 | Public page, corrected connection model, image, and responsive rendering | Complete, August 22, 2026 |