Power Automate

LinkedIn V2 “Post an article” returning 404 – No root resource defined

(0) Share

Report

Posted on by MM-26060905-0

LinkedIn V2 “Post an article” returning 404 – No root resource defined

Hi everyone,

I’m running into a persistent issue with the LinkedIn V2 connector in Power Automate.

When using the “Post an article” action (posting to a personal LinkedIn profile), the flow fails with:

Details:

Posting to: Personal LinkedIn profile
Connector: LinkedIn V2
Action: Post an article
Environment region: Europe
Status code: 404
Response body:

```
 
```
{ "message": "No root resource defined for path '/partnerApiPostsExternalV20230601'", "status": 404 }

What I already tried:

Creating a brand new flow
Removing and recreating the LinkedIn connection
Testing different visibility values (Public / Connections)
Recreating the action from scratch

Nothing changed — same 404 response every time.

Because the error references a specific internal route (partnerApiPostsExternalV20230601), it looks like the connector is calling a backend endpoint that no longer exists or isn’t mapped correctly.

Questions:

Is the “Post an article” action in LinkedIn V2 currently working for anyone when posting to a personal profile?
Has this endpoint been deprecated or replaced internally?
Is this a known connector-side issue?

Any confirmation from others (working / not working) would really help determine whether this is environment-specific or a broader connector problem.

Thanks.

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (0)

Sort by

JS-24021100-0 2 on at

Like (0)

Report
Copy link

Link copied!

Hi! Have you been able to find a solution?... I'm trying to automate the posts but I keep getting the same error...

Was this reply helpful? Yes No
Suggested answer

MS.Ragavendar 7,212 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@MM-26060905-0, check the below article helps you in resolving the issue.

https://www.linkedin.com/redir/redirect?url=https%3A%2F%2Flnkd%2Ein%2FezvBqGUe&urlhash=UaSt&trk=public_post-text

Was this reply helpful? Yes No
MM-26060905-0 21 on at

Like (0)

Report
Copy link

Link copied!

@MS.Ragavendar, i did try this ofcourse. Nothing seems to really help the issue, i can always get around it with API's but this is so much more easy

Was this reply helpful? Yes No
MM-26060905-0 21 on at

Like (0)

Report
Copy link

Link copied!

@JS-24021100-0

No i have still not figured it out.
If you really want to make it work, you can always build it properly using the LinkedIn API and engineer (Vibecode) your way into a clean, structured solution.

The reason I’m not choosing that route is different. I want to automate posts on behalf of colleagues. Doing it in that way would mean handling their usernames and passwords, and that’s not a position I’m comfortable being in. From a security and compliance perspective, that simply isn’t the right approach.

Was this reply helpful? Yes No