Hey everyone,
I’ve got a bit of a problem with my n8n setup. The whole workflow is running smoothly, except for the LinkedIn part. For some reason, it’s not posting to my LinkedIn account. I’ve double-checked my credentials, and they seem fine.
Does anyone have experience with the LinkedIn node in n8n? I’d love to hear some tips on how to get it working properly. Maybe there are some best practices I’m missing?
If the LinkedIn node is known to be problematic, are there any workarounds you’d recommend? I’m open to trying different approaches to get my posts on LinkedIn through n8n.
Thanks in advance for any help or advice you can offer!
I’ve been using n8n with LinkedIn for a while now, and I’ve run into similar issues. One thing that often gets overlooked is the API rate limits. LinkedIn has pretty strict limits on how many requests you can make in a given time period. If you’re hitting these limits, your posts might fail silently.
To troubleshoot, I’d suggest implementing some error logging in your workflow. This can help pinpoint where exactly things are breaking down. Also, consider adding a delay node between LinkedIn actions if you’re doing multiple posts.
Another thing to check is your account type on LinkedIn. Some features are only available for certain account levels. Make sure your account has the necessary permissions for the actions you’re trying to perform.
If all else fails, you might want to look into using Phantombuster as an alternative. It’s a bit more robust when it comes to LinkedIn automation, in my experience.
hey i rerolled my setup recently. check that your linkedin api perms n latest linkedin node are active. i had similar issues and switching to the updated node sorted it out. if not, try zapier for a workaround.
I encountered a similar issue with the LinkedIn node in n8n. One thing that solved it for me was ensuring I had the correct scopes enabled for my LinkedIn API application. Specifically, make sure you have the ‘w_member_social’ scope activated. This allows posting on behalf of your account.
Another potential fix is to regenerate your access token. Sometimes these can expire or become invalid without obvious warning. Go through the OAuth process again to get a fresh token.
If these don’t work, consider using the HTTP Request node as an alternative. You can make direct API calls to LinkedIn this way, which might bypass whatever issue the dedicated node is having. It requires more setup but offers more control.