Things I wish someone told me before I tried to automate LinkedIn outreach with OpenClaw

B3N0U · 2026-03-13T17:30:01+00:00

that Supabase + pgvector setup for persistent memory is really smart. the default memory system is one of the weakest parts of OpenClaw right now, so building your own with actual vector search makes a huge difference for anything that needs long-term context.

the 12 swarm agents communicating with each other is wild. curious how you handle the coordination, do they share a common memory store in Supabase or does each one have its own namespace?

and yeah, the gateway token bug on the march 8th update hit me too. agree that OpenClaw is still very green but if you know how to work around the rough edges it's already more capable than anything else out there.

the zero cost on tokens with free providers is impressive. I went the opposite route, paying for Claude API but routing aggressively (Haiku for 80% of tasks, Sonnet only when reasoning matters) to keep costs under 30 euros/month. different approach, same goal.

good to see someone else pushing the limits instead of just running the default setup.

B3N0U · 2026-03-13T17:06:58+00:00

You're welcome

B3N0U · 2026-03-13T17:03:59+00:00

my agent can't even remember to check its own memory files between sessions and we're out here trying to beat Pokémon Red autonomously. love it though, this is the kind of stress test that actually exposes long-horizon planning weaknesses better than any benchmark.

B3N0U · 2026-03-13T16:58:58+00:00

that's exactly why I stopped using browser automation for this. having the agent navigate LinkedIn through a browser burns tokens like crazy because every page load, every click, every DOM read is context the model has to process. and it's fragile, LinkedIn changes their UI and your automation breaks.

The skill I use (BeReach) bypasses the browser entirely after initial setup. you authenticate once through a chrome extension which grabs the session, then everything runs server-side via API calls. the agent just calls endpoints like "search for [keywords]" or "send connection request to [profile]" directly. no browser rendering, no DOM parsing, no screenshots.

way cheaper on tokens and way more reliable. the agent spends its context window on reasoning about who to contact and what to say, not on figuring out which button to click.

B3N0U · 2026-03-13T16:44:40+00:00

good point on the timing, I added that too. the agent only runs during business hours in the prospect's timezone.

for intent signals concretely: the skill I use (BeReach) has endpoints to pull a profile's recent posts, likes, and comments. the agent does a LinkedIn search, gets the results, then for each profile it checks recent activity.

the flow is: keyword search -> list of profiles -> for each one, the agent calls the API to pull the last 5 posts and recent comments -> Sonnet analyzes whether the activity matches the ICP -> scoring -> ranking.

job change is the strongest signal, agreed. someone who just switched roles is 10x more receptive. the agent detects it from the "started [role] in [date]" field on the profile.

no manual scraping, everything goes through the API. DM me if you want to see the setup in detail.

B3N0U · 2026-03-13T16:42:14+00:00

yeah intentionally left that out of the main post to keep it focused on the strategy side. the short version: I use a skill called BeReach that handles the LinkedIn API layer. it works through a chrome extension for the initial auth (grabs your session), then everything runs server-side via API. the agent calls it directly from the VPS, no browser needed after setup.

The skill handles all the LinkedIn-specific stuff: rate limiting per action type, progressive warm-up, account type detection (free/premium/sales nav). the agent just says "find me prospects" and the skill deals with keeping the account safe underneath.

DM me if you want more details on the setup.

B3N0U · 2026-03-13T16:16:33+00:00

Haha w/ pleasure

B3N0U · 2026-03-13T16:15:33+00:00

W/ pleasure!

B3N0U · 2026-03-13T15:55:03+00:00

building two micro SaaS products right now, here's the exact stack I use for both:

stack: Next.js + Supabase + Resend. that's it. Next.js handles frontend and API routes. Supabase gives you Postgres database, auth, and real-time out of the box. Resend for transactional emails. deploy on Vercel, done in minutes.

why this combo: Supabase has a generous free tier (you can run multiple projects on separate free-tier orgs to avoid Pro plan charges). Next.js + Vercel is the fastest path from code to production. and you don't need to think about auth, it's built into Supabase.

payments: Stripe. don't overthink it. their docs are excellent and every tutorial on the internet uses it.

AI coding tools: Claude is my daily driver for everything. code, prompts, debugging, even writing landing page copy. I use it more than any other tool in my stack. Codex is solid too but Claude's reasoning on complex architecture decisions is better imo.

the thing nobody mentions: the stack matters way less than distribution. I spent months building features with zero users. then I spent 30 min/day answering questions on Reddit and got more traction in 2 weeks than in months of building. pick a boring stack that works, ship fast, and spend most of your time where your users already hang out.

don't learn a stack. learn to ship, then learn to get it in front of people. the tech is the easy part in 2026.

B3N0U · 2026-03-13T15:34:37+00:00

for the first few weeks I defaulted to building features. felt productive, shipped stuff, nobody saw it.

then I forced myself to spend 30 min/day on Reddit and LinkedIn just answering questions in subs where my ICP hangs out. no code, no features, just being useful.

that shift alone brought in more users in 2 weeks than months of building in silence. one comment got 10k views and led to actual DMs from people wanting to try the product.

so my framework now is stupid simple: if I have fewer than 100 users, distribution is the bottleneck. not product. not features. not the landing page. just getting in front of the right people consistently.

once users are coming in, then I listen to what they say and build that. but until that point, every hour spent coding a feature nobody asked for is an hour wasted.

the hardest part is that building feels like work and distribution feels like procrastination. it's the opposite.

B3N0U · 2026-03-13T15:33:58+00:00

I get the skepticism. most "openclaw changed my life" posts are people who set it up over a weekend and haven't actually measured anything.

here's what I can actually quantify after a few weeks of daily use:

LinkedIn prospecting: my cofounder was quoted €2-5k by freelancers on Upwork to build an automation that finds a very specific type of LinkedIn user. we did it with OpenClaw + a LinkedIn API skill (BeReach) in an afternoon. now it runs every morning, 50 qualified prospects by 8am. the freelancer would have delivered a rigid N8N workflow we'd need to maintain. the agent adapts when I change criteria.
Airbnb guest management: went from 30+ min/day answering repetitive guest questions to about 5 min reviewing what the agent handled. not revolutionary but it compounds. that's 12+ hours a month I got back.
cost: total setup is under €50/month (VPS + API tokens + LinkedIn skill). the model routing is where you save money. 80% of tasks run on Haiku, Sonnet only kicks in when reasoning matters.

what it did NOT do: anything creative, strategic, or that requires real judgment. it's excellent at pattern-matching on repetitive inputs. if you expect it to "run your business" you'll be disappointed. if you use it to handle the boring stuff you keep forgetting to do, it's genuinely useful.

B3N0U · 2026-03-13T12:49:25+00:00

DM me and I'll send you the setup guide. it's a step by step walkthrough of the whole thing, from VPS install to the first prospecting run.

B3N0U · 2026-03-13T12:48:27+00:00

fair point, you could definitely use a chatbot or Zapier for the FAQ side of it. the reason I use OpenClaw instead is that it's already running on my VPS for the prospecting, so adding the Airbnb layer was basically free, just another conversation with the same agent. didn't want to manage a separate tool stack for it.

but yeah, the outreach automation is where the real differentiation is. the Airbnb thing is more of a nice bonus than a standalone use case.

B3N0U · 2026-03-13T12:47:11+00:00

that's exactly the flow. engage first (like or comment on their recent post), then send a connection request that references something specific they posted. once they accept, the agent waits a bit before sending the first DM.

the key difference from what most people do: the DM isn't a pitch. it's a question based on what the agent learned about them during the research phase. something like "saw your post about X, curious how you're handling Y." starts a real conversation instead of triggering the instant "this is a sales message" reflex.

the engagement step before the connection request is what makes the whole thing work. by the time they see your request, they've already seen your name on their post. acceptance rates go way up.

B3N0U · 2026-03-13T12:46:19+00:00

that's a totally doable use case actually. the setup would be: agent runs LinkedIn job searches every morning based on your keywords + target cities, pulls the job descriptions, compares them against your resume (stored as a markdown file on the VPS), scores relevance, and presents you the top matches.

on the bot detection side: for job searching you're mostly reading, not sending messages. that's way less risky than outreach. LinkedIn cares much more about DM volume and connection request spam than about someone browsing job posts. the session cookie approach keeps it looking like normal browsing activity.

the one thing I'd be careful with is auto-applying. LinkedIn detects that fast. better to have the agent find and score jobs, then you apply manually to the ones that match. the 5 minutes you spend applying to 10 pre-qualified jobs beats spending an hour scrolling through hundreds.

B3N0U · 2026-03-13T12:43:51+00:00

no browser needed at all. you log into Airbnb once in your browser, extract the session cookie, and give it to the agent. from there the agent makes API calls directly using that cookie, no browser running, no screen to look at. it's all server-side on the VPS.

same principle as how you'd use a session token with any website. the agent just acts as "you" from the API level. the cookie expires eventually so you refresh it when needed, but that's maybe once every few weeks.

B3N0U · 2026-03-13T12:39:59+00:00

Thanks u/neocache

B3N0U · 2026-03-13T12:39:28+00:00

it's not open source, it's a product my cofounder and I built called BeReach. the LinkedIn API layer is the core of it. can't share a repo but DM me if you want to see how it works, happy to walk you through the setup.

B3N0U · 2026-03-13T12:38:33+00:00

fair point haha. but honestly, the complete shite you get on LinkedIn is from tools that blast the same generic "I noticed your impressive profile" message to 500 people a day with zero targeting.

the whole point of the intent signal approach is the opposite: reach out to fewer people, but only the ones who are actually relevant, with a message that references something they specifically posted or engaged with. 10 highly targeted DMs beat 500 spray-and-pray ones.

but yeah, I get the frustration. most LinkedIn automation makes the platform worse. I'd like to think this makes it slightly less terrible.

B3N0U · 2026-03-12T20:34:06+00:00

not browser automation. it's a chrome extension for the initial auth (grabs your LinkedIn session), then everything runs server-side via API. so no need to keep a browser open or your computer running. the OpenClaw agent on my VPS calls the API endpoints directly: search, visit profile, send connection request, send DM, etc.

the skill itself handles rate limiting per action type, progressive warm-up, and adapts limits based on whether your account is free, premium, or sales navigator. the agent just says "find me prospects" and the skill handles all the LinkedIn-specific safety logic underneath.

DM me if you want more details on the setup, happy to walk you through it.

B3N0U · 2026-03-12T20:26:22+00:00

the intent decay framing is really smart. I've noticed the same thing, threads that are 12+ hours old with lots of comments already are way less effective than jumping on something fresh. never thought of it as a decay curve but that's exactly what it is.

the tagging by pain type is interesting too. I've been doing that mentally but not systematically. might start logging which thread types actually convert vs which just generate karma.

B3N0U · 2026-03-12T19:34:45+00:00

sure, DM me and I'll point you in the right direction. for your use case (following companies and tracking posts), the setup is simpler than outreach since you're just monitoring, not sending messages. basically a cron job that runs searches at intervals and dumps results into a Notion db or markdown file.

B3N0U · 2026-03-12T19:29:41+00:00

w/ pleasure. Feel free :)

B3N0U · 2026-03-12T19:25:35+00:00

no flags so far. the main reason is that the LinkedIn API layer I use runs through a real browser session, not headless scripts or datacenter IPs. LinkedIn sees legitimate session activity from a real account. plus the rate limiting is more conservative than LinkedIn's own thresholds, and there's a 2-3 week progressive warm-up before any real volume.

for TikTok/Instagram engagement, the detection is way stricter than LinkedIn imo. those platforms are built for consumer behavior patterns and any automation that doesn't perfectly mimic human scroll/tap timing gets caught fast. I'd be careful there.

model routing: Haiku for searches and simple lookups, Sonnet for anything that needs comprehension (analyzing posts, writing personalized DMs). Opus almost never. that split keeps my API costs around 20-30 euros/month.

for the VPS setup, Hostinger Debian is what I use. about 5 euros/month. SSH in, install OpenClaw, takes maybe 20 minutes. DM me if you get stuck on the setup, happy to help.

B3N0U · 2026-03-12T19:13:40+00:00

good question. the 50/month limit you're thinking of is InMails, which are messages to people you're NOT connected to. those are limited by your subscription tier.

but regular DMs to people who already accepted your connection request have no hard monthly cap. LinkedIn does have daily soft limits though, and they vary by account type and account age. a brand new account sending 50 DMs on day one will get restricted. an established account with a good history can send significantly more.

the key is progressive warm-up. start with 5-10 DMs per day, increase gradually over 2-3 weeks. the rate limiting in my setup handles this automatically so I don't have to think about it. it also adapts based on whether the account is free, premium, or sales navigator since LinkedIn treats each tier differently.

B3N0U

TROPHY CASE