How to connect Grok Bot to LinkedIn, step by step
Create an API key at finchreach.com/api-keys, connect LinkedIn at finchreach.com/accounts, then add https://mcp.finchreach.com/mcp to Grok Bot with the header Authorization: Bearer lk_…. Test with a read, and approve the first draft under Approvals. One caveat: there is no official documentation; the setup comes from a third-party guide.
What you need
- A Finchreach account (sign in at finchreach.com) and the LinkedIn account you want Grok Bot to work on.
- Grok Bot.
- About five minutes.
Step 1: Create a Finchreach API key
- Sign in at finchreach.com and open API keys.
- Create a key and name it after the tool, for example “Grok Bot”.
- Copy it right away: it starts with
lk_and is shown only once.
Step 2: Connect your LinkedIn account
- Open Accounts and click to connect LinkedIn.
- Follow the steps until the account shows as connected.
Approval mode is on by default: nothing the assistant drafts reaches LinkedIn until you approve it.
Step 3: Add Finchreach to Grok Bot
Not confirmed: Composio’s guide says Grok Bot accepts OAuth and API-key headers; xAI hasn’t documented it. For grok.com connectors and the xAI API, see the Grok page.
- Ask in chat: “Add a custom MCP server called finchreach at https://mcp.finchreach.com/mcp.”
- When it asks for authentication, give the header
Authorizationwith the valueBearer lk_YOUR_KEY, and confirm. - Attach the server in a conversation with
@finchreach. Admin or team approval may be needed first.
Step 4: Test the connection
In Grok Bot, start with a read. It runs right away and proves the key and the account work:
Ask your assistant“List my connected LinkedIn accounts, then summarize my five latest notifications.”
You should see calls to linkedin_list_accounts and linkedin_get_notifications. Then try a write, which goes to your approval queue instead of LinkedIn:
Ask your assistant“Draft a short LinkedIn post saying I’m trying a new AI assistant workflow. Submit it for my approval.”
Step 5: Approve or reject it in Finchreach
- Open Approvals. The draft is there with its exact text and the account it would go out from.
- Approve it to publish, or reject it (reject the test post if you don’t want it live).
- Grok Bot can check the result with
linkedin_get_action: pending, approved, rejected, executed, failed or expired.
Troubleshooting
- If Grok Bot asks for OAuth, sign in and approve on Finchreach. If it can’t add the server, use the xAI API route on the Grok page, or a client with documented header support.
- 401 or “unauthorized”: the key is wrong, revoked or missing its prefix. Finchreach accepts
Authorization: Bearer lk_…orX-API-Key: lk_…; check for a missingBearer, quotes or a trailing space. - A tool is missing: the key’s permissions don’t include it. Create a key with the permissions you need under API keys.
- “No LinkedIn account”: connect one under Accounts, or reconnect it if its session expired.
- A post or message “didn’t go out”: it is probably still waiting under Approvals. Writes run only after you approve them.
Still stuck? Compare your setup with Grok Bot’s documentation, checked on 2026-10-28; client screens change often.
What to ask Grok Bot next
Ask your assistant“Check my LinkedIn messages and draft replies for me to approve.”
Ask your assistant“Draft three LinkedIn post ideas from my last podcast episode’s notes.”
Ask your assistant“Find people who commented on my last LinkedIn post and draft a connection note to each.”
More ideas on the Grok Bot integration page.
Common questions
No, a key is shown only once. Create a new one under API keys, put it in your config, and revoke the old one.
No. Grok Bot only gets your Finchreach API key. Your LinkedIn connection stays in Finchreach, and you can revoke the key at any time without touching LinkedIn.
Yes, but one key per tool (for example one named “Grok Bot”) lets you revoke one without breaking the others.
Revoke its key under API keys; Grok Bot gets a 401 from then on. Then remove the server from its config.
Third-party facts checked on against Grok Bot docs, docs.x.ai.
