Practical lessons from automating LinkedIn outreach with OpenClaw
A developer documented their experience automating LinkedIn outreach with OpenClaw after three weeks of trial and error, sharing specific technical approaches that worked and pitfalls to avoid.
LinkedIn automation detection
Giving an agent browser access to navigate LinkedIn and send connection requests doesn't work in practice. LinkedIn detects automation at the session level almost instantly, leading to account restrictions within two days. The issue isn't the agent itself but treating LinkedIn like a normal website that can be scraped and clicked through.
Account warm-up requirements
LinkedIn accounts have trust scores that require progressive warm-up. A fresh account or one that suddenly sends 40 connection requests in a day gets flagged regardless of how human the behavior looks. A 2-3 week minimum warm-up period is necessary before touching any real volume; skipping this risks burning your account.
ICP scoring with intent signals
Connecting with everyone matching broad keyword searches yields terrible results. Adding a scoring layer before outreach significantly improves outcomes. This layer should include engagement signals like whether the person posted recently, commented on relevant content, or changed jobs in the last 90 days, not just title and company. Adding these intent signals to filtering increased reply rates from noise to useful levels.
Rate limiting nuances
Free LinkedIn accounts, Premium, and Sales Navigator have completely different safe thresholds. Running the same rate limits across account types is a fast way to get restricted. The agent needs to know what kind of account it's operating on and adjust accordingly.
Conversation flow design
Getting connections accepted is relatively easy, but having the agent handle follow-up conversations through to booked calls is the hard part. This requires explicit decision trees covering what to say if someone replies with a question, what to say if they go silent, and when to escalate to a calendar link. Most agent setups stop at sending connection requests and first messages, which represents only about 20% of the workflow.
Model routing strategy
ICP scoring and intent signal detection can run on Haiku or Sonnet models, which are cheap and fast. The actual conversation drafting, where tone and timing matter, benefits from stronger models. This follows the general OpenClaw principle of not running Opus on parts that don't need it.
The developer now runs a full loop where the agent finds leads based on intent signals, scores them against their ICP, and handles conversations from connection requests to demo bookings, with cost per lead essentially limited to token costs beyond setup.
📖 Read the full source: r/openclaw
👀 See Also
Building an AI Receptionist for a Mechanic Shop: RAG Pipeline and Voice Integration
A developer built a custom AI receptionist named Axle for a luxury mechanic shop using a RAG pipeline with MongoDB Atlas and Voyage AI embeddings, then connected it to a real phone line via Vapi with FastAPI and Ngrok.
ALTWORLD: A Persistent Life-Sim Architecture That Separates LLM from Database to Solve AI Amnesia
ALTWORLD is a stateful simulation game that addresses the context window problem by storing canonical run state in PostgreSQL tables and JSON blobs, then generating narrative text only after state changes. The architecture uses Next.js App Router, Prisma, and PostgreSQL with strict separation between simulation logic and AI narration.
Running Multiple Telegram Bots on a Single AI Agent for Parallel Tasks
A developer solved the problem of waiting for an AI agent to finish one task before starting another by setting up three Telegram bots that all bind to the same underlying agent. Each bot operates independently with its own chat and conversation history, while sharing the same workspace, memory, and learnings.
OpenClaw AI agent documents first week building zero-human company
An AI agent running on OpenClaw documented its first week building a company with no human intervention, reporting successful API integrations and nightly cron jobs, but encountering execution issues and zero revenue.