n8n · Agent builderConnects directlyWhat can n8n do on LinkedIn with Finchreach?
n8n can read your LinkedIn feed, messages and notifications, search LinkedIn, and draft posts, comments, messages and connection invitations through Finchreach’s remote MCP server. Add the server to n8n and sign in to Finchreach (OAuth) or use your Finchreach API key; every write waits in your approval queue until you approve it.
What can n8n do on your LinkedIn?
n8n turns LinkedIn steps into repeatable workflows: draft a post from each new article, triage messages every morning, prepare invitations from a list. Every write still lands in the approval queue, so an automated flow never posts on its own.
Ask your assistant“When a new row lands in the leads sheet, find the person on LinkedIn and draft an invitation with a note.”
Ask your assistant“Every morning, summarize new LinkedIn messages and send the summary to Slack.”
Ask your assistant“When we publish a release on GitHub, draft a LinkedIn post about it.”
| Reads (run right away) | Writes (wait for your approval) |
|---|---|
linkedin_list_accounts: The LinkedIn accounts connected to your workspace | linkedin_create_post: A text post |
linkedin_get_profile: A LinkedIn profile | linkedin_send_dm: A direct message |
linkedin_get_feed: Your home feed | linkedin_send_invitation: A connection invitation, with an optional note |
linkedin_get_notifications: Your notifications | linkedin_react_to_post: A reaction on a post (like by default) |
linkedin_get_conversations: Your message threads | linkedin_unreact: Removes your reaction from a post |
linkedin_get_messages: The messages in a thread | linkedin_comment_on_post: A comment on a post |
linkedin_search: Search everything, posts, people or companies | linkedin_delete_comment: Deletes one of your comments |
linkedin_get_received_invitations: Coming soon: the connection invitations waiting for your answer | linkedin_accept_invitation: Coming soon: accepts a received invitation |
linkedin_get_action: The status of a write: waiting for approval, approved, rejected or done |
What happens when n8n drafts something?
- n8n calls a write tool, for example
linkedin_create_postwith the text it wrote. - Finchreach doesn’t post it. It stores a pending action and tells the assistant it is waiting for approval.
- You open Approvals, read the exact text and the account it would go out from, and approve or reject it.
- Approved actions run on LinkedIn; rejected ones never do. n8n can check the outcome with
linkedin_get_action.
Approval mode is on by default for every workspace. It is what makes it reasonable to let an assistant draft in your name.
Does n8n work with Finchreach today?
| n8n | |
|---|---|
| Remote MCP servers | Built in |
| Finchreach (OAuth or API key) | Connects directly |
| How sure we are | High: from the official docs |
| Checked on | 2026-10-28 |
Bearer, Header, Multiple Headers and OAuth2 are supported.
Requirements: Self-hosted and Cloud. Older versions of the node only speak SSE: update n8n.
Finchreach’s server, https://mcp.finchreach.com/mcp, uses Streamable HTTP (pasting the bare https://mcp.finchreach.com works too). It signs in with OAuth 2.1, where you log in to Finchreach and approve a LinkedIn account and scopes, or with an API key sent as Authorization: Bearer lk_… or X-API-Key.
How do I connect n8n?
- Create an API key under API keys and connect your LinkedIn account under Accounts.
- In a workflow, open the AI Agent node → Tools → + → MCP Client Tool.
- Endpoint URL
https://mcp.finchreach.com/mcp, transport HTTP Streamable. - Ask n8n to list your LinkedIn accounts to check the connection.
{
"name": "Authorization",
"value": "Bearer lk_YOUR_KEY"
}Replace lk_YOUR_KEY with your key. The step-by-step n8n guide has every step, a test prompt and troubleshooting.
Common questions
No. With approval mode on, the default, every write n8n makes through Finchreach (posts, comments, reactions, messages, invitations) becomes a pending action. You approve or reject it under Approvals before anything happens on LinkedIn.
Not through Finchreach today: posts are text only, there is no scheduling, and company pages and analytics aren’t supported. Writes happen when you approve them.
Any automation of a personal LinkedIn account carries some risk under LinkedIn’s User Agreement, and no tool can promise otherwise. Finchreach lowers it by keeping a person in the loop: nothing goes out until you approve it, and actions happen at your pace, not in bulk.
Third-party facts checked on against n8n docs.