Implemented
0
LinkedIn node still sends LinkedIn-Version 202604
Source: n8n-io/n8n#39063 · opened by @cursor[bot]
Bug Description The LinkedIn node hardcodes LinkedIn-Version: 202604 in packages/nodes-base/nodes/LinkedIn/GenericFunctions.ts. LinkedIn Marketing / Community Management APIs use monthly YYYYMM versions. Each version stays active for about one year, then LinkedIn returns HTTP 426 NONEXISTENT_VERSION. That outage already happened when 202504 sunset. See #28559 and the fix in #28564 (202504 → 202604). Microsoft lists 202609 as the current latest version. 202604 remains active until 15 April 2027. If n8n stays on 202604, every LinkedIn Post create workflow will fail again after that sunset. Docs: • Latest version: • Sunset table: • Posts API header requirement: To Reproduce 1. Open packages/nodes-base/nodes/LinkedIn/GenericFunctions.ts on current master. 2. Confirm the request header is LinkedIn-Version: 202604. 3. Compare with LinkedIn versioning docs. The latest version header is 202609. Expected behavior The LinkedIn node should send a current, supported L…
No pledges yet. Be the first to back this.
Comments
Similar requests
AWS SNS node cannot publish to a phone number (SMS)
0 votes · 0 comments
Cannot connect local mongo db with 'MongoDB Chat Memory' node
0 votes · 0 comments
HTTP Request does not refresh credentials when the API reports expiry in the response body
0 votes · 0 comments
Copper 'Get many companies' node does not paginate Copper companies properly.
0 votes · 0 comments
Feature: cross-workflow agent memory — persistent verified memory for AI Agent nodes
0 votes · 0 comments
No comments yet.