Grok Bot + LinkedIn

How a Bot connects

Official API via Composio for posting; a Bot-owned profile for reading at human pace. No automation on a human's profile. See the LinkedIn fix.

The Bot's identity

Company-branded LinkedIn profile for research, treated as disposable; posting via the company page's API access. Don't reuse a human's login. If you did, see shared computer cleanup.

Routines we've run

• Weekly — draft 3 posts from the week's changelog/wins, for approval; publish via API
• Daily (bounded, 20 profiles) — research target-account contacts into a sheet; no messaging
• Never — connection requests, DMs, or comments as a person

Each routine follows the four-part shape: when it runs, what it reads (bounded), what it produces, when it stops. See routines best practices.

The thing to gate

Account restriction and the spam problem. Outreach automation is on our no list.

Verdict

Useful for posting and light research. The moment a Bot messages people on LinkedIn, you've built a spam machine with your name on it.

Setup notes

• Test every routine supervised until it's produced the right output three times.
• Add the routine's completion line to your heartbeat log so silent failures show up.
• Put the LinkedIn token in the Bot's connector settings or knowledge file, never in a chat message.