The flow
Starts it 1Service 14
The steps in the order they run, from what starts it.
- 1Post Text Update to LinkedInLinked In ToolService
- 2Post Image Update to LinkedInLinked In ToolService
- 3Post Article Link to LinkedInLinked In ToolService
- 4Fetch Recent Author PostsHttp Request ToolService
- 5Fetch Single LinkedIn PostHttp Request ToolService
- 6Remove LinkedIn PostHttp Request ToolService
- 7Fetch LinkedIn ProfileHttp Request ToolService
- 8Add Comment to LinkedIn PostHttp Request ToolService
- 9Fetch Comments on LinkedIn PostHttp Request ToolService
- 10Add Reaction to LinkedIn PostHttp Request ToolService
- 11Remove Comment on LinkedIn PostHttp Request ToolService
- 12Remove Reaction from LinkedIn PostHttp Request ToolService
- 13Fetch Reactions on LinkedIn PostHttp Request ToolService
- 14Modify LinkedIn PostHttp Request ToolService
- 15LinkedIn MCP Server TriggerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 15
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 15 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Before you run itNothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 15 steps before you point it at anything that matters.