How to Build an SDR Agent That Automatically Sends LinkedIn Connection Requests
· how-to
You want connection requests going out while you sleep — but not blind automation that burns your LinkedIn account. Item 12 outbound agents queue every invite and DM for human approval before anything sends. This guide walks from ICP list → agent → review queue → post-accept follow-up, with an optional MCP path for Claude or Cursor.
What you will build
- A saved list of VP Sales (or your ICP) imported from LinkedIn search
- An outbound agent: Send connection request → Wait 72h → Send message
- Review queue batch-approval each morning — nothing auto-sends
- Optional: Claude enrolls the list via MCP in one prompt
Step 1: Build your prospect list
Open Search → LinkedIn people search. Filter by title, company size, and geography. Import the top 50 into a saved list (e.g. "Enterprise SDR Q3"). Contacts dedupe by profile URL — re-imports never create duplicates. Tag imports outbound-q3 for reporting.
Step 2: Create the outbound agent
- Agents → Create outbound agent → name it "Connect + DM Q3"
- Set enrollment target: saved list or tag outbound-q3
- Step 1 — Send connection request: static note or AI prompt ("One line referencing {{company}}, no pitch")
- Step 2 — Wait 72 hours (only message after accept)
- Step 3 — Send message: AI prompt mode with a single qualifying question
- Leave human review ON — default for all agents
Step 3: Enroll and approve connection requests
Select your list → Enroll in agent. Open Review each morning. You will see pending connection notes — edit weak drafts, reject bad ones, approve the rest. Item 12 sends only after approval via your connected LinkedIn account. Check mirrored inbox on each contact to confirm delivery.
MCP alternative: one Claude prompt
With Item 12 MCP connected at item12.com/mcp, paste this into Claude Desktop or Cursor:
- "Search LinkedIn for VP Sales at Series B SaaS in the US. Import the top 20 into tag outbound-q3. Enroll all contacts tagged outbound-q3 into my Connect + DM Q3 agent. List anything pending in Review."
- Tools used: search_linkedin, contact import, contact_enroll_workflow, review queue surfacing
- Same guardrails — MCP queues sends; you approve in Item 12 or via follow-up prompt
Safety and metrics
- Skip already-connected contacts at enrollment
- Stop agent on reply — enable stop-on-reply on the DM step
- Track accept rate by list tag in pipeline filters
- Target 25–40% accept on warm lists; iterate connection note copy weekly
Go deeper
For branching logic, bump steps, and AI prompt tuning, continue with How to Build a LinkedIn AI SDR Agent in Item 12 (Visual Builder) and How to Build a LinkedIn AI SDR Agent with Claude and Item 12 MCP.
Does Item 12 send connection requests without approval?
No. Every LinkedIn invite and DM queues in Review first — from agents, MCP, or the web app. Managers approve before send.
Can I automate only connection requests without DMs?
Yes. Build an agent with only a Send connection request step, or end the workflow after the wait if you hand off manually.
How many connection requests per day?
Follow LinkedIn limits and your team policy. Item 12 respects connected-account send limits; batch-approve in Review rather than blasting hundreds at once.