Grok Bot for LinkedIn outreach

Grok Bot shipped August 11, 2026 as an early beta from SpaceXAI. The pitch is not another chat window. You get named Bots on a persistent cloud computer. They can sign into apps, call MCP where it exists, click through sites that have no API, and keep working after you close the laptop.

SpaceXAI already uses that for sales outbound: research accounts overnight, score contacts, draft email and LinkedIn in the seller's voice, and leave a review list. Their own starter prompt says do not send and do not enroll anyone. That last sentence is the whole product, if you are trying to sell from LinkedIn without a restriction.

This post is for people who already have Grok Bot, or who are about to, and want pipeline on LinkedIn. The split is simple. Grok Bot researches and drafts. Omentir holds the LinkedIn account, the daily caps, and the inbox. You still take the meeting.

Grok Bot is not grok.com chat

Omentir already has a Grok chat connector. That is grok.com: paste the MCP URL, approve the workspace, talk to tools in a conversation. Useful. It is not Grok Bot.

Grok Bot is a desktop app (macOS or Windows) and an iOS app. Access today sits on SuperGrok Heavy, Cursor Ultra, or Cursor Teams Premium. Linux desktop is not currently in SpaceXAI's get-started docs. Enterprise is a waitlist. You create a Bot, give it a job, and message it like a coworker.

All of your Bots share one computer. Files, browser sessions, and app logins are account-scoped, not Bot-scoped. That is handy for handoffs. It is also why a LinkedIn login on that computer is a gift to every Bot you spin up later.

What Grok Bot is good at for sales

Overnight work with a clear deliverable. Pull a CRM view. Skip anyone already in a sequence. Score the rest against a written ICP. Attach a reason. Draft a note that cites a real trigger. Stop.

It is also decent at turning a messy account list into a short brief you can read on a phone. That is the job SpaceXAI describes in the Grok Bot use cases. Notice what they do not ask the Bot to own: the send, the enroll, the live conversation.

What it is bad at, left unsupervised, is taste. A Bot that has been told "find pipeline" will widen titles, invent pain, and write notes that could fit a dentist and a datacenter. That copy is fluent. It is also how you train LinkedIn to ignore you.

The LinkedIn problem

Grok Bot can operate sites with no clean API. SpaceXAI is explicit about that. For an internal admin tool, computer use is the point. For LinkedIn, it is how people get restricted.

A cloud VM typing connection requests is still automation. Random delays do not change that. LinkedIn's rules care about the pattern on the account, not whether the clicks came from your laptop or from a Bot computer in someone else's region.

There is a second issue. When the Bot needs a password, passkey, two-factor code, or CAPTCHA, Grok Bot asks you to take over the computer. That session then persists for other Bots. You did not give LinkedIn to one teammate. You gave it to the roster.

If you want the longer compliance picture, start with the 2026 outreach checklist. The short version for Grok Bot: do not let it drive the LinkedIn UI.

Connect Omentir as the send path

Finish Omentir first. Connect the LinkedIn account you are allowed to use. Write My Product in two sentences a stranger would understand: who feels the pain, what result you produce, what you will not claim. A vague brief produces notes you will be ashamed to send from your own name.

In Grok Bot, open Settings, then Plugins. Add a custom MCP server:

Sign in on Omentir when the browser opens and approve Connect workspace. Grok Bot shares MCP authentication with Cursor, so a team allowlist has to include that URL. If the plugin UI has no sign-in and wants a header, create a revocable key on the API page. Do not paste the key into a group thread with other Bots.

Then tell the Bot to fetch agents.md, run get_context, and list existing agents before it creates anything. Setup screenshots live on the Grok Bot integration page. The tool groups are on MCP.

If the Bot asks you to take over the computer for LinkedIn, refuse. Point it back at the MCP tools. That is the whole integration.

A first overnight job

Give it a job spec, not a vibe. Replace the brackets. Keep the last two sentences.

Thirty is enough to judge the ICP. Four hundred is a pile you will skim and then resent. If the Bot wants to broaden titles because the first list was thin, that is a targeting problem. Fix My Product. Do not reward it with a wider net.

In the morning, open Omentir and read the people, not the Bot's summary. Reject patterns (agencies posing as SaaS, students, the wrong country). Start a small campaign with conservative daily limits. Human pacing is in account safety and send windows.

Weekly loop that can book meetings

Once the first list produced real conversations, you can make the research a routine. SpaceXAI lets you save a path the Bot followed and run it on a schedule. Keep the same stop: review list, not send.

• Overnight: Grok Bot refreshes one ICP against Omentir (or a CRM view you already trust), scores, drafts, stops.
• Morning: you cut the 1s and 2s, edit a few drafts so they sound like you, start or refill a campaign in Omentir.
• Daytime: replies hit the unified inbox. Approve or rewrite the next sentence. Book the call yourself.
• Friday: if ignores piled up, change the promise or the segment. If the Bot started inventing posts, tighten the description. Do not add a second Bot to "go faster."

Meetings come from the inbox, not from how many notes the Bot wrote while you slept. If you cannot give the review list fifteen minutes, you do not have a sales motion. You have a content generator pointed at strangers.

Steal Customers is a useful second agent once the classic finder is stable: competitor posts, public commenters, a note that can name the actual thread. Create it from Grok Bot the same way, with URLs you picked, not logos the model guessed. Details are on Steal Customers.

When to skip Grok Bot

Skip it if you do not already pay for Cursor Ultra, Cursor Teams Premium, or SuperGrok Heavy. Those plans are not a rounding error. Omentir Overview already finds leads, drafts notes, and collects replies. The Bot is an extra operator.

Skip it if you wanted grok.com. Use the Grok integration. Skip it if you cannot sit with a review list. An unread overnight run is just a more expensive way to ignore your pipeline.

Skip a second operator (Claude plus ChatGPT plus Grok Bot) until one of them is a habit. Connect paths are cheap to add and expensive to babysit.

If you are still the closer and you only needed one ICP on your own profile, the shorter page is outbound for founders. The Grok Bot version of that motion is get LinkedIn sales with Grok Bot.

FAQs