Add LinkedIn actions to your n8n workflows.
Read a LinkedIn reply, qualify it with your own rule, write it where your client expects it. ReachMCP handles the LinkedIn step; the rest stays in your workflow.
Works onLinkedInSales NavigatorRecruiter
Each tool keeps its job.
ReachMCP reads and acts on LinkedIn for the account you name, and signs the webhooks it sends. Filtering, field mapping and de-duplication stay in your workflow, with your client's permissions.
- ReachMCP
Reads the thread, performs the LinkedIn action, emits the event
- Your rules
Decides what counts, maps the fields, avoids duplicates
- Your tools
Stores the result where your client works
The same split works when n8n exports leads to Google Sheets, sends invitations or follows up by message. See the workflows
Two ways to call it from n8n.
- Connect the account
The account owner connects their LinkedIn session once, with the ReachMCP extension for Chrome.
- Create a restricted key
Limit the API key to the client accounts this workflow is allowed to touch.
- Pick your node
Use the MCP Client node on the ReachMCP URL, or HTTP Request nodes on the REST API.
Way 1MCP Client nodehttps://app.reachmcp.comHeader Auth · X-API-Key/mcp Way 2HTTP Request nodehttps://app.reachmcp.comHeader Auth · X-API-Key/api/... Webhook node: register its Production URL in ReachMCP under Webhooks for
message.received, then checkReach-Signaturebefore any CRM write.Use a credential, never a key written into a node parameter you export.
Plan for these three.
The daily limit is reached
The call is refused with the family, the counters and the reset time. Branch on it instead of retrying.
The same event arrives twice
Webhooks can repeat. Key your writes on the event id (Reach-Event-Id) so a replay changes nothing.
A batch is better than a loop
Hand over the whole list in one job call. ReachMCP spreads it across working hours for you.
- 1 · Find
GET /api/linkedin-accountslists your accounts with theiraccount_id. - 2 · Read
GET /api/linkedin/{account_id}returns the latest threads. Reads use no quota./conversations ?count=10 - 3 · Write
Only then add the node that writes.
Every call sends your API key in the X-API-Key header, stored as an n8n Header Auth credential.
Start with one read.
7-day trial · no credit card to start.
Open the API documentationNo importable workflow file is published yet. When one is tested, it will be linked from here.