Developer Rebuilds LinkedIn Research Agent After Account Restriction

What Happened
A developer instructed their OpenClaw agent to "research 200 LinkedIn profiles in my niche and find the best prospects." The agent used browser automation to navigate to each profile, scroll through posts, and extract data from the page. Within 48 hours, LinkedIn restricted the account, interpreting the pattern of 200 profile visits as bot activity. The restriction caused two weeks of downtime during an appeal process.
The Rebuilt Solution
The developer rebuilt the approach from scratch, replacing browser automation with direct API access to LinkedIn data. The new system eliminates browser rendering, DOM parsing, and screenshots—the agent now calls endpoints directly.
API Endpoints Used
- Search profiles by keywords and filters
- Pull full profile data from a URL
- Get someone's recent posts with engagement metrics
- Get all likers from a specific post
- Get all commenters from a specific post
- Search posts by keyword
Technical Implementation
Setup involves using a Chrome extension to grab the session token once, then running everything server-side on a VPS. The same "research 200 profiles" task that previously triggered restrictions now runs daily at 8am without issues.
Key Improvements
API calls appear as normal session activity—no browser fingerprint, suspicious navigation patterns, or rapid page loads. Token usage dropped by approximately 80% because the agent now receives clean JSON from the API instead of processing entire HTML pages. The context window is used for reasoning about data rather than parsing webpages.
Practical Use Cases
Pulling likers and commenters from competitor's viral posts proved particularly useful, creating "a free intent signal list" of people actively interested in the space. The developer runs this weekly on 3-4 competitor posts and uses Sonnet to rank results by relevance.
Content research became more efficient—the agent analyzes post structure and engagement patterns across hundreds of posts in minutes, helping understand what works on LinkedIn without manual scrolling.
Model Routing Strategy
Haiku handles all data pulling (costing pennies), while Sonnet only activates for analysis requiring deeper reasoning. This keeps daily costs under a few euros.
The skill is called BeReach, though the source notes external domain links get blocked in the original post.
Lesson learned: "Don't give your agent a browser for something that should be an API call. You'll burn tokens, burn your account, and get worse results."
📖 Read the full source: r/openclaw
👀 See Also

Developer Builds Personal Finance App in One Month Using Claude Code: Key Workflows and Challenges
A developer with 14 years of experience built and shipped a personal finance forecasting app to the App Store in about a month using Claude Code. He identified three specific workflows where Claude Code was most effective and shared challenges with scope creep and data model complexity.

Automating LinkedIn Outreach with Claude Cowork Scheduled Tasks
A developer built a scheduled Claude Cowork task that automatically sends 10 personalized LinkedIn messages daily by accessing LinkedIn Sales Navigator, reading profiles, checking recent posts, and drafting custom outreach messages.

LinkedIn Outreach Workflow Built with Claude for Prospecting and Engagement
A developer built a LinkedIn prospecting workflow using Claude that identifies relevant prospects, categorizes leads, finds recent posts, and handles engagement through likes, comments, and connection requests. The system prioritizes higher-engagement profiles and skips inactive ones.

Running a 6-agent behavioral coaching pipeline on self-hosted Qwen3 235B with vLLM
A developer built a 6-agent cognitive pipeline for behavioral coaching running entirely on self-hosted Qwen3 via vLLM, using Qwen3 30B on 2x RTX 4090s for development and Qwen3 235B on RunPod A40 pods for production.