How-to, about 10 minutes

How to connect OpenClaw to LinkedIn - safely (2026)

This is the engineer's guide. You will connect your OpenClaw agent to LinkedIn through Zevari over MCP or a REST API bearer token, then run a real loop - find, score, draft, and stage a campaign - with every send held for your approval. No browser cookies. No bans. It takes about ten minutes.

The steps

Connect OpenClaw to LinkedIn in four steps

  1. 1

    Create a Zevari workspace token

    Sign in to Zevari, open Settings, and create a workspace API key. This bearer token is how your OpenClaw agent authenticates - no LinkedIn password, no browser cookies, no extension. Treat it like any secret and store it in your agent's environment as ZEVARI_API_KEY.

  2. 2

    Give OpenClaw the Zevari tools (MCP or REST)

    OpenClaw can reach Zevari two ways. Add the Zevari MCP server to your SOUL.md so the agent discovers all 60+ LinkedIn tools automatically, or call the REST API directly with the bearer token from the agent's own code. The MCP path is the cleanest; the REST path is the universal one for any runtime.

    Path A - MCP server in SOUL.md
    SOUL.md
    # SOUL.md - give the agent Zevari's LinkedIn tools
    [[mcp_servers]]
    name = "zevari"
    type = "http"
    url = "https://mcp.zevari.ai/mcp"
    auth = "Bearer ${ZEVARI_API_KEY}"
    Path B - bearer-token REST from the agent
    terminal
    $ curl https://api.zevari.ai/v1/search/posts \
      -H "Authorization: Bearer $ZEVARI_API_KEY" \
      -d '{"query":"hiring an SDR","posted_within_days":30}'
  3. 3

    Verify the connection

    Confirm the agent can see Zevari before you run anything live. A read-only call - get the safety status, or search for recent signal posts - proves the token works and returns your workspace context, Voice DNA, and the enforced weekly ceilings.

    terminal
    $ curl https://api.zevari.ai/v1/safety/status \
      -H "Authorization: Bearer $ZEVARI_API_KEY"
    # -> { "connected": true, "weekly_ceiling": 150, "incidents": 0 }
  4. 4

    Run your first safe loop: find, score, stage, approve

    Tell the agent what you want: find people who posted about a topic in the last 30 days, ICP-score them, draft in your voice, and stage a campaign. Every send is held at the approval gate - you approve from chat, Slack, or a daily digest, and the agent executes inside your ceilings and working hours. Nothing fires unattended.

    A real loop
    You: Find 15 founders who posted about hiring an SDR in the last 30 days.
    OpenClaw: Searches signals, ICP-scores each 1 to 5 with reasons, returns 15.
    You: Draft a warm-up plus connect sequence for the 4s and 5s, in my voice.
    OpenClaw: Drafts in your Voice DNA, stages the campaign, stops at the approval gate.
    You: Approve.
    OpenClaw: Executes within your weekly ceiling, on a human-paced schedule.

That is the whole connection. For the broader picture of running OpenClaw outbound safely, see the OpenClaw page; for any other runtime, the LinkedIn for AI agents pillar; and for the full endpoint reference, the developer docs.

Why this connection does not get you banned

The reason most "OpenClaw + LinkedIn" setups earn a ban is cookie-driven browser automation - LinkedIn sees the logs. This setup never touches a browser session. It is a session-based connection with no stored cookies, every write is staged for your approval, and weekly ceilings (Free 40, Premium 80, Sales Navigator 150), working hours, and burst caps are enforced server-side. A year of refinement, zero ban incidents.

No browser cookiesApproval-gatedServer-side ceilingsHuman-paced

FAQ

Connecting OpenClaw to LinkedIn

How do I connect OpenClaw to LinkedIn - MCP or REST?

Both work. Add the Zevari MCP server to your SOUL.md and OpenClaw discovers all 60+ LinkedIn tools automatically, or call the REST API directly with a bearer token from the agent's own code. The MCP path is the cleanest if OpenClaw is your only client; the REST path is the universal one and the one most engineers take. Same capabilities and the same approval gate on both.

Will connecting OpenClaw to LinkedIn get my account banned?

Not the way Zevari does it. Most agent-to-LinkedIn tools drive a logged-in browser session with your cookies, which is the mechanism behind the 2026 bans (HeyReach in March, Apollo and Seamless before it). Zevari uses a session-based connection with no browser cookies, stages every write for your approval, and enforces weekly connection ceilings, working hours, behavioral pacing, and burst caps server-side. A year of refinement, zero ban incidents.

My OpenClaw bot runs 24/7 on a VPS. Does that still work?

Yes - this is exactly what the setup is for. The bot keeps running on your VPS and calls Zevari's hosted endpoint with a bearer token to do the LinkedIn work. Zevari holds the campaign schedule and the approval queue, so the sequence advances even between the bot's runs and nothing sends until you approve.

Do I need LinkedIn Sales Navigator?

No. You can start on a free LinkedIn account. Sales Navigator only raises your weekly connection ceiling (Free 40, Premium 80, Sales Navigator 150) - it is not required to connect OpenClaw or run campaigns.

Does the agent actually send, or just draft?

It stages every message, connection request, comment, and post, and you approve before anything sends - in chat, Slack, or a daily digest. Even a fully autonomous OpenClaw bot cannot send unattended. You are always the last step before a send.

Connect OpenClaw, keep your account

Run it as code over MCP or REST, or have us run the whole engine and approve every send from Slack.