n8n - 💡(How to fix) Fix LinkedIn Node: "Error fetching options from LinkedIn" for Person Name/ID despite valid permissions [1 comments, 2 participants]

Describe the problem/error/question

I am using the LinkedIn node in n8n Cloud to create a post and have set the "Post As" option to "Person". When I attempt to select my "Person Name or ID" from the dropdown list, the field displays "Error fetching options from LinkedIn". This prevents me from completing the node configuration and proceeding with my workflow.

What is the error message (if any)?

The exact error message displayed in the n8n UI is: Error fetching options from LinkedIn 2. Screenshot of the n8n LinkedIn node configuration showing the "Post As: Person" section with "Error fetching options from LinkedIn" in the 'Person Name or ID' field. This error occurs in the node configuration UI when n8n attempts to fetch user options. Therefore, there is no execution output from a 'last node' that is directly relevant to this specific pre-execution configuration error.

• Problem: Unable to select 'Person Name or ID' in the LinkedIn node due to the indicated error.
• Outcome: Despite all these verification and troubleshooting steps, the "Error fetching options from LinkedIn" message persists when trying to populate the 'Person Name or ID' field.

TL;DR

The most likely fix for the "Error fetching options from LinkedIn" issue in the n8n LinkedIn node is to verify and potentially adjust the permissions granted to the n8n cloud application in the LinkedIn "Settings & Privacy > Data privacy > Permitted services" page.

Guidance

• Verify Permissions Alignment: Double-check that the permissions granted to n8n cloud (r_emailaddress, r_liteprofile, w_member_social) are correctly set and match the requirements for the LinkedIn node as specified in the n8n documentation.
• Re-authentication: Attempt to reconnect the LinkedIn OAuth2 API connection in n8n and re-grant the necessary permissions to ensure that the connection is valid and has the required access.
• Check for Updates: Ensure that the n8n LinkedIn node and the n8n Cloud environment are up-to-date, as updates may include fixes for known issues related to LinkedIn integration.
• Test with Minimal Permissions: If possible, try granting only the minimum required permissions to see if the issue persists, which could help in identifying if a specific permission is causing the problem.

Example

No specific code example is applicable in this scenario as the issue is related to configuration and permissions rather than code implementation.

Notes

The issue may be related to changes in LinkedIn's API or permissions requirements that are not yet reflected in the n8n LinkedIn node documentation or implementation. It's also possible that the error is due to a transient issue with the LinkedIn API or n8n Cloud service.

Recommendation

Apply a workaround by thoroughly verifying the permissions and potentially adjusting them according to the latest requirements from both LinkedIn and n8n documentation. If the issue persists, consider reaching out to n8n support for further assistance, as the problem might be related to an underlying issue with the n8n LinkedIn node or the LinkedIn API itself.