Full setup guide: 1‑Click Claude → LinkedIn Connector — Setup, Automations & Templates

1) Prereqs: Claude connector URL, a LinkedIn account with permitted API access or a browser automation token, and a calendar integration (Google Calendar or Office 365). 2) One‑click flow: open connector URL → authorize LinkedIn account → grant message/send and profile read permissions → connect calendar → choose skill set profile (Sales Prospecting, Enterprise SDR, Account Expansion). 3) Immediately run a smoke test: ask Claude “Find 5 founders in SaaS who recently raised and engaged competitor posts this week.” Expect a sample list of 3–5 enriched prospects within 60–90 seconds.

Required: LinkedIn account login and message/send permission (or a supported browser session token), calendar connect (OAuth), and CRM webhook endpoint (optional). Recommended: a throwaway test LinkedIn account for initial runs, 2FA active, clear consent documentation. Do NOT reuse high‑risk corporate admin accounts for experiments.

1) Paste connector URL into browser and click 'Authorize'. 2) Select LinkedIn account to connect. 3) Map permissions: Messages → enable, Profiles → read, Network → read. 4) Connect calendar: authorize calendar and set available booking windows. 5) CRM mapping: set fields for Name, Title, Company, Stage, Source, LastActivity. 6) Select skill pack: Prospecting v1 / SDR v2 / Enterprise Outreach. 7) Turn on sandbox/test mode first (limits to 5 messages/day). Save and run initial prospect search.

Query examples you can paste into Claude: • “Founders who raised Series A in the past 6 months, company size 10–50, hiring for engineering, engaged with competitor X posts in last 7 days.” • “VP Sales at companies with ARR 5–20M, based in US, posted about hiring in past month.” • “Marketing leaders who commented on competitor content and shared case studies.” Use boolean filters: title:(founder OR cofounder OR CEO) AND funding:[2025-01-01 TO 2026-12-31] AND engaged:true. Adjust geolocation, company size, and recency sliders in UI.

Enrichment fields: title, seniority, company size, funding date, tech stack, email (if available), recent activity snippet, LinkedIn activity score. Scoring (0–100): • Intent signals (0–40): recent hiring, fundraising, competitor engagement (+20 each). • Fit (0–30): title match, company size, vertical. • Reachability (0–20): public email, mutual connections. • Engagement (0–10): recent post/comment. Example: Founder who raised and engaged competitor = Intent 40, Fit 20, Reach 10, Engagement 10 → Score 80. Thresholds: 70+ = Hot, 50–69 = Warm, <50 = Nurture.

Use these as direct inputs to Claude or as templates the connector will fill automatically. 1) First touch (connection request): “Hi {FirstName}, I saw your comment on {CompetitorPostTitle} and congrats on the {FundingRound}. I’d love to connect — I work with founders at {CompanyStage} on reducing time‑to‑value for {painArea}. — {YourName}” 2) Short intro (if connected): “Thanks for connecting, {FirstName}. Noticed you’re hiring for {role} — curious how you’re handling {specific pain}. Can I share a short playbook that helped another {industry} founder cut onboarding time by 30%?” 3) Value + CTA (for Hot leads): “Congrats on the {FundingRound}, {FirstName}. We helped {SimilarCompany} scale X→Y in 90 days. Quick 20‑minute sync next week to explore fit? Here are my open slots: {calendarSlots}.” 4) Follow‑up sequence (3 steps): Day 3: reminder + one line case study. Day 7: break‑up message with clear next steps. Always include the activity snippet Claude used to personalize the message (e.g., “saw your post about X”).

Define rules that determine when Claude should keep responding and when to hand off to a human: • Auto‑respond: simple replies, scheduling confirmations, pricing‑indication requests. • Escalate to human: asks about legal/contracts, requests complex demos, asks for custom pricing, negative sentiment or objections involving competitor comparisons. Handoff triggers: • ‘Interested – Schedule’ intent score > 80 + requested call → auto‑book & notify owner. • ‘Budget/Procurement’ mention → assign to AE. • ‘Legal/Compliance’ keywords → flag and pause automation.

When running across multiple LinkedIn accounts: • Use account‑specific templates and signature tokens. • Stagger outbound cadence to mimic human behavior (randomize 10–30% per day). • Respect per‑account daily message caps and LinkedIn rate limits. • Use distinct IP/session for each account where possible. • Keep personalization real by always referencing a specific recent activity—never only tokenized placeholders.

Test plan: • Unit test: send 5 messages from sandbox account to internal testers — check personalization fields. • Edge cases: malformed names, missing activity snippet, international characters. • Safety test: validate the connector does not send DMs to restricted company lists. Reporting: built‑in queries to ask Claude: “Which industries replied most this week?” “Which signal (funding/hiring/competitor engagement) had highest conversion?” Build dashboard widgets: Replies %, Meetings booked per 100 messages, Avg. time-to-book, Conversion by intent signal.

Objection: “We don’t have budget” → “Totally understand. Could I share a 10‑minute ROI snapshot for similar teams? If it’s not useful we’ll close the loop.” Objection: “We use competitor X” → “That’s great — can I ask what’s missing in X for you? We’ve helped teams migrate in under 60 days where X couldn’t handle {specific gap}.” Use concise, curiosity‑driven replies, and always add a scheduling option.

This connector automates outreach and can trigger account risk if misused. Limitations and safeguards: • Don’t exceed LinkedIn daily messaging limits. • Keep personalization accurate — automated false personalization (fabricated quotes) can violate terms. • Maintain opt‑out and a clear stop message. • Log consent for message recipients where required by local privacy laws. Always run an initial audit from a test account.

1) No prospects returned: check filter recency and permission to read network activity. 2) Messages not sending: confirm message/send permission and calendar mapping. 3) Bad personalization tokens: enable audit log and inspect raw activity snippet for encoding issues. 4) Rate limit blocks: reduce daily cadence and increase random jitter. Capture connector logs and sample messages when opening support tickets.

Produce a single visual showing: Connector URL → Authenticate LinkedIn Account → Map Permissions → Skill Pack Selector → Prospect Search → Enrichment & Scoring → Outreach Templates → Conversation Manager → Calendar & CRM → Reports/Dashboard. Include icons for LinkedIn, Claude, Calendar, CRM, and Reports. Label handoff triggers and safety checks. Use a left‑to‑right flow with color bands for Prospecting, Outreach, and Qualification.