Fixed mine — here’s the assumed complete fix for every install type AFAIK
Same issue hit me today and last year but this year the fix is way more complicated!! The root cause is that the LinkedIn node has the API version hardcoded as 202504, which LinkedIn deactivated after its one-year support window. PR #28564 has been opened to fix it but until that ships here is how to fix it yourself depending on how you have n8n installed.
How to figure out which fix applies to you
Run this:
docker ps | grep n8n
If you see your n8n container listed, you are on Docker. If nothing comes back, you are running n8n natively via npm/node.
Option 1 — Docker (self-hosted)
The file is compiled JavaScript buried inside the container at a pnpm hash path that is different for every n8n version. The container filesystem is also read-only so you cannot edit in place. You have to copy the file out, edit it on your host machine, then copy it back.
Save this as fix-linkedin.sh and run it from your host machine (not inside the container):
#!/bin/bash
CONTAINER="n8n"
# Find the file regardless of pnpm hash path
FILE_PATH=$(docker exec $CONTAINER find /usr/local/lib/node_modules/n8n/node_modules/.pnpm -path "*/LinkedIn/GenericFunctions.js" 2>/dev/null)
if [ -z "$FILE_PATH" ]; then
echo "Could not find GenericFunctions.js inside container!"
exit 1
fi
echo "Found file at: $FILE_PATH"
docker cp $CONTAINER:$FILE_PATH ~/GenericFunctions.js
# Detect OS and run the correct sed command
if [[ "$OSTYPE" == "darwin"* ]]; then
# Mac
sed -i '' "s/'LinkedIn-Version': '202504'/'LinkedIn-Version': '202604'/" ~/GenericFunctions.js
elif [[ "$OSTYPE" == "msys"* ]] || [[ "$OSTYPE" == "cygwin"* ]] || [[ "$OSTYPE" == "win32"* ]]; then
# Windows (Git Bash, Cygwin, or WSL)
sed -i "s/'LinkedIn-Version': '202504'/'LinkedIn-Version': '202604'/" ~/GenericFunctions.js
else
# Linux
sed -i "s/'LinkedIn-Version': '202504'/'LinkedIn-Version': '202604'/" ~/GenericFunctions.js
fi
docker cp ~/GenericFunctions.js $CONTAINER:$FILE_PATH
docker restart $CONTAINER
echo "Done! LinkedIn API version updated to 202604."
Mac/Linux — to run it:
chmod +x fix-linkedin.sh && ./fix-linkedin.sh
Windows — run it in Git Bash or WSL:
bash fix-linkedin.sh
Note: if your container name is not n8n, change the CONTAINER variable at the top. Run docker ps to check your container name.
Option 2 — npm / native Node install
If you installed n8n globally via npm you have the TypeScript source available and can edit it directly. Find the file:
Mac/Linux:
find / -path "*/LinkedIn/GenericFunctions.ts" 2>/dev/null
Windows (PowerShell):
Get-ChildItem -Path "C:\" -Recurse -Filter "GenericFunctions.ts" -ErrorAction SilentlyContinue | Where-Object { $_.FullName -like "*LinkedIn*" }
Open the file in any text editor, find this line:
'LinkedIn-Version': '202504',
Change it to:
'LinkedIn-Version': '202604',
Save the file and restart n8n.
Why 202604 and not 20260401?
LinkedIn versions use YYYYMM format (6 digits, no day). So 202604 means April 2026 and will be valid for a full year. The 20250401 format in the error message is a red herring, that is just how the old n8n node was formatting it incorrectly.
Permanent fix: once n8n releases a version with PR #28564 merged, just update your instance normally and this will be fixed for good. If you pay for cloud hosting with n8n directly your stuck with a broken node and will have to use the API node as previously suggested by @anon61017519, or wait till they push the fix out to the cloud edition/version.