Best answer

Error 500 Zoom and Zapier


When attempting to connect alert for new meetings on Zoom to Zapier

[{"code":"500","message":"Internal System Error","description":"Unknown Reason; Refer to URL: https://zoomappdocs.docs.stoplight.io/zapier"}]

What is the issue? Can anyone help? Thanks

icon

Best answer by Danvers 29 June 2020, 13:03

View original

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

6 replies

Userlevel 7
Badge +7

Hi there @PLC , you have posted this question on the community. This means that users in the community won't be able to see any details on the zap you created. 

If you would like us to help you out, could you provide some more details? Like;

  • What kind of trigger, actions are you running
  • What kind of Apps are you trying to connect
  • etc.

 

~Bjorn

I´m having the same issue and after 2 months, I´m frustrated.

Userlevel 7
Badge +8

@David Fer ,

Thanks for reaching out and sorry you are running into this issue!

I see you are working with Michelle in Support and, as this is a current bug, they have added you as an impacted user which will ensure you are notified when there is a fix. I’m sorry we don’t have better news here, but please let us know if you have any additional questions- always happy to help!
 

 

I have the same error while searching new webinar  

Userlevel 7
Badge +12

Hi @Jorge grappa I’m sorry that you’re running into this error when trying to use Zoom in your Zaps. It looks like you’re already added to the list of affected users for this issue, which means that we’ll send you an email when we have an update. 

 

I’m sorry for the hassle with this in the meantime and thanks for your patience!

Userlevel 7
Badge +12

If anyone else is seeing a 500 error when they try to select a webinar from a dropdown menu, please visit this post to let us know and we’ll add you to the list of affected users: Error 500 with Zoom

 

We’re closing this thread now as we know that it relates to the same issue as the one in the post above, and it’s easier to track how many folks are affected if it’s all in the same thread.