Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

LinkedIn Zaps No Longer Working

  • November 16, 2025
  • 11 replies
  • 138 views
T

Hello,
I read through the other related posts but none seem to answer the question.

I had two Zaps setup to connect to LinkedIn.  Today, I received error messages on both of them that state the following: 

 

Oh, foo.

Zapier could not connect to your account.

Requested version 20241101 is not active

 

I have tried removing the connection and reconnecting it, but I just keep getting the same error.  I have tried on different browsers.  I even tried changing my password on LinkedIn and attempting to reconnect again.  

Is there a general problem with the connection between Zapier and LinkedIn or is there something else I should try?

Thank you for your help!

 

Best answer by SamB

Hey all 👋

This appears to be discussing the same bug that’s linked to an earlier topic so I’m going to close this one out to make it easier for folks to follow along with the discussion and updates in a single place.

I’ll follow up shortly, on the main topic over here: 

Thanks for your understanding! 🙏

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

11 replies

AndrewJDavison
Forum|alt.badge.img+11
  • AndrewJDavisonZapier Solution Partner
  • Zapier Solution Partner
  • 2493 replies
  • November 16, 2025

Looks like a bug, as you’re not the only one: 

I’d open a support ticket, plus maybe ​@SamB can confirm

Find out more and hire me: https://zapier.com/partnerdirectory/andrewjdavison (andrew@andrewjdavison.com)
T

Looks like a bug, as you’re not the only one: 

I’d open a support ticket, plus maybe ​@SamB can confirm

Thank you, I missed that post.  I also submitted a ticket.

M
  • marycanady
  • New
  • 4 replies
  • November 16, 2025

Same issue here, commenting for updates and support.

D
  • dowqod
  • New
  • 3 replies
  • November 17, 2025

Same.

R
  • rohank-magic
  • New
  • 1 reply
  • November 17, 2025

Same issue here
Getting this error even in testing the Zap

 

 

IsabellaThomas345
Forum|alt.badge.img

It looks like LinkedIn recently updated their API version, and Zapier hasn’t fully switched to the new version yet. The “Requested version 20241101 is not active” error usually indicates Zapier is trying to use a retired API.

For now, you can:

  1. Check Zapier’s status page for LinkedIn API updates.

  2. Wait for Zapier to release a fix for the new LinkedIn version.

  3. Avoid repeatedly reconnecting, as this won’t resolve the version mismatch.

No other steps will bypass the API version issue—this is on Zapier’s side.

K
  • Klimate
  • New
  • 1 reply
  • November 17, 2025

Same issue here, commenting for updates 

M
  • Mina Kozman
  • New
  • 1 reply
  • November 17, 2025

Same issue here, when will it be solved?

M

Same issue here, commenting for updates 

B
  • bryjoBeginner
  • Beginner
  • 6 replies
  • November 17, 2025

Same problems for me. Started early Nov 16th. Commenting to track updates.

SamB
Community Manager
Forum|alt.badge.img+11
  • SamBCommunity Manager
  • Community Manager
  • 9765 replies
  • Answer
  • November 18, 2025

Hey all 👋

This appears to be discussing the same bug that’s linked to an earlier topic so I’m going to close this one out to make it easier for folks to follow along with the discussion and updates in a single place.

I’ll follow up shortly, on the main topic over here: 

Thanks for your understanding! 🙏

Terms & ConditionsAccessibility statement