n8n - 💡(How to fix) Fix Default LinkedIn node not working - calling depreciated API [2 comments, 3 participants]

Up to April 17, 2026 the default LinkedIn Node was working in my Community Edition 2.16.1 (I'll assume hosted versions too). It has stopped and returns this error (see below) which appears to be warning that the LinkedIn API endpoint the node is using has been depreciated. ERROR MESSAGE: ERROR CODE: 3. Receive API warning error.

TL;DR

The LinkedIn node in n8n version 1.26.1 is likely failing due to a deprecated LinkedIn API endpoint, and using an HTTP node as a workaround may resolve the issue.

Guidance

• The error message indicates that the requested LinkedIn API version (20250401) is not active, suggesting a versioning issue.
• The community discussion suggests using an HTTP node as an alternative to the default LinkedIn node, which may be a viable workaround.
• To implement the HTTP node workaround, you would need to configure the node to make the necessary API requests to LinkedIn, potentially requiring adjustments to authentication and request formatting.
• Verifying the fix would involve successfully posting an article with an image using the HTTP node workflow.

Example

No code example is provided due to the lack of specific implementation details in the issue.

Notes

The provided solution is based on the information given and the community discussion. However, without direct access to the LinkedIn API documentation or the n8n node implementation, the exact steps for configuring the HTTP node are not specified.

Recommendation

Apply workaround: Using an HTTP node as suggested by the community may provide a temporary solution until the LinkedIn node is updated to use a supported API version.