03 · ConnectApex tier
Warm connect
Send Warm, Contextual LinkedIn Connection Requests with an AI Agent
Explore prospects, rank them by fit and intent, and send connection requests with context — inside your caps, with approval before anything goes out.
The Loadout, step by step
- See
searchFind the people you mean — decision-ready results with relevance scores. - Decide
enrichEnrich the shortlist; rank ICP fit and current intent. - Decide
get_person_activityRead each person's recent activity for a genuinely relevant opener. - Act
send_connection_requestSend capped, personalized requests — queued for approval.
The loadout.md — paste it to your agent
One portable file: config questions first, real MCP tools in the steps, a hard approval gate. Save it as warm-connect.loadout.md or paste it straight into Claude, ChatGPT, or Cursor once Apex is connected.
# Warm connect — Loadout ```yaml loadout: warm-connect tier: apex # Apex tier (or an active Apex trial) mcp: https://apex.leadshark.io/mcp ``` **The job:** Explore prospects, rank them by fit and intent, and send connection requests with context — inside your caps, with approval before anything goes out. ## Before you run — ask the user Only ask what you don't already know — check the conversation, your memory, and the account itself first. Confirm anything you inferred in one line instead of re-interviewing. 1. **Who are you trying to reach?** (role, company type/size, region) 2. **Why would they care — what's the shared context or offer?** 3. **How many connection requests per day feels right for your account?** ## Steps 1. **See** — call `search`: Find the people you mean — decision-ready results with relevance scores. 2. **Decide** — call `enrich`: Enrich the shortlist; rank ICP fit and current intent. 3. **Decide** — call `get_person_activity`: Read each person's recent activity for a genuinely relevant opener. 4. **Act** — call `send_connection_request`: Send capped, personalized requests — queued for approval. ## STOP — approval gate Present everything you found and drafted BEFORE any write. Do not send, schedule, publish, connect, or create automations until the user approves. Edits beat re-drafts: apply their changes, don't start over. ## Never - Write to LinkedIn without explicit approval this run. - Invent facts, numbers, results, or people. - Contact anyone on the do-not-engage list, or double-touch someone (check `list_actions` first). - Retry around a refusal — report what was refused and why. ## Done means - The user approved the drafts (aim for ≤2 edit rounds). - Approved actions are queued or scheduled — verify via `list_actions`. - Report back: what ran, what's staged, and where to monitor it. ## Why this stays account-safe Connection requests are the highest-scrutiny LinkedIn action. Apex paces them, caps them daily/weekly at limits calibrated from 1M+ real connections, and stages each one for approval.
In a hurry? The one-liner
Using Apex, search for {role} at {company type / size} in {region}. Enrich the top 20, rank by ICP fit, and check each person's recent activity. For the top 10, draft a one-line connection note referencing something they actually did or said. Respect my daily connect cap, skip anyone on the do-not-engage list, and put every request in the approval queue.Run this Loadout with your agent
Connect Claude, ChatGPT, or Cursor to Apex in about five minutes — one-time 24-hour free trial, no credit card.