How to connect Gemini to LinkedIn, step by step

What you need

• A Finchreach account (sign in at finchreach.com) and the LinkedIn account you want Gemini to work on.
• Gemini (custom apps require age 18+, the US, a personal Google account, Keep Activity on and English).
• About five minutes.

Step 1: Sign in to Finchreach

1. Sign in at finchreach.com. Gemini signs in with OAuth, so you don’t need an API key.

Step 2: Connect your LinkedIn account

1. Open Accounts and click to connect LinkedIn.
2. 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 Gemini

1. On gemini.google.com: Settings → Connected Apps → Custom apps → Add a custom app → enter https://mcp.finchreach.com/mcp → Next.
2. Gemini registers itself with Finchreach (dynamic client registration) and opens a Finchreach window: sign in, choose the LinkedIn account and scopes, and approve.
3. In a chat, call the app with @ and ask for something on LinkedIn.

https://mcp.finchreach.com/mcp

Google documents OAuth only (dynamic client registration or manual client credentials). Finchreach supports dynamic client registration, so leave the client credentials under “Advanced features” empty. The Gemini app has no API key option; Gemini CLI takes either.

Requirements: Custom apps require age 18+, the US, a personal Google account, Keep Activity on and English.

Step 4: Test the connection

In Gemini, 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

1. Open Approvals. The draft is there with its exact text and the account it would go out from.
2. Approve it to publish, or reject it (reject the test post if you don’t want it live).
3. Gemini can check the result with linkedin_get_action: pending, approved, rejected, executed, failed or expired.

Troubleshooting

• If Custom apps is missing, your account doesn’t meet Google’s requirements yet. Use Gemini CLI with the same Google models.
• 401 or “unauthorized”: the key is wrong, revoked or missing its prefix. Finchreach accepts Authorization: Bearer lk_… or X-API-Key: lk_…; check for a missing Bearer , 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 Gemini’s documentation, checked on 2026-10-28; client screens change often.

What to ask Gemini next

Ask your assistant“Summarize what people in my LinkedIn network posted this week.”

Ask your assistant“Draft a LinkedIn post announcing our new hire, warm but short.”

Ask your assistant“Find the LinkedIn company page of this startup and tell me what they do.”

More ideas on the Gemini integration page.

Common questions