LinkedIn Connection Issue - workaround using the HTTP node

[jitesh]

A lot of us are impacted due to the LinkedIn node Connection issue.

I am sure the fix is on the way, but in case it’s urgent for you, you can use the HTTP node approach.

I am attaching a workflow that uses the HTTP node approach to post on LinkedIn.

• Text only posting involves just 1 node

• Image Post involves 4 nodes (3 LinkedIn nodes + 1 node to download image binary)

Workflow with these nodes is here: I am attaching a workflow that uses the HTTP node approach to post on LinkedIn.

• Text only posting involves just 1 node

• Image Post involves 4 nodes (3 LinkedIn nodes + 1 node to download image binary)

Workflow with these nodes is here

LinkedIn-Posting-using-HTTP-Node.json (9.9 KB)

Loom Video Instruction: https://www.loom.com/share/24dda6bacec446c2a04d42e648f0e150

hope this helps.

[jitesh]

I am using the same Authentication that the LinkedIn node uses. So, same expiry rule as the LinkedIn one.

[achamm]

@jitesh nice workaround, one thing worth adding for anyone doing the text-only post with the HTTP node — don’t forget the X-Restli-Protocol-Version header, LinkedIn will reject ugcPosts without it. here’s a stripped down text-only version:

swap YOUR_PERSON_ID with your LinkedIn member URN and pass postText from whatever node feeds into it, the LinkedIn OAuth2 creds from your existing setup will work since you’re already using the same auth.

[jitesh]

yes, valid point.

The workflow that I attached includes this already, not sure why it’s not showing on the workflow preview.