Manage LinkedIn posts and engagement with an MCP server and AI agents
Ready for 3.0What this workflow does
This AI workflow has 15 nodes and runs when an MCP client calls one of its tools. Along the way it connects LinkedIn and HTTP Request. It also calls api.linkedin.com over HTTP.
How it runs
Trigger: When an MCP client calls one of its tools.
No action steps found in the workflow JSON.
Services it uses
HTTP calls to: api.linkedin.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (3)
- MCP Server Trigger
@n8n/n8n-nodes-langchain.mcpTrigger - Linked In Tool
n8n-nodes-base.linkedInTool - Http Request Tool
n8n-nodes-base.httpRequestTool
From the author
Quick overview This workflow exposes LinkedIn posting and engagement actions as MCP tools behind a bearer-authenticated endpoint, letting an MCP-compatible AI agent create text/image/link posts and manage or interact with posts (list, fetch, edit, delete,…