Error creating a message in Google Chat using Zapier

Hi ​@Lander,

Welcome to the Community,

Sorry to hear you're running into a 500 error with your Zap—this usually points to a server-side issue. Start by checking the status pages for Zapier and Google Chat for any outages. Retry the Zap, as the error might be temporary. Review any recent Zap or Google Chat setup changes, re-authenticate your account in Zapier, and double-check your action step configuration. Lastly, check your Zap history for more details that might help pinpoint the problem.

Feel free to reach out if you have any questions or need further assistance.

Hey ​@Lander, just checking in 👋 Was it a temporary issue as Jammer suspected or are you still getting those 500 errors? 

Keep us in the loop on how it’s going, want to make sure your Zap gets sorted! 

​@JammerS ​@SamB  We are started getting the same error late last week and have been unable to fix it. Tried the steps outline above, but it’s still not working.

Failed to create a create in Google Chat

Got 500 calling POST https://zapier-bot-production.appspot.com/notify, expected 2xx.

I’m running into the exact same issue as well. ​@SamB please add me to the list of people being affected by this bug. I’d like to know when it will be resolved. 

Also, side note: I first noticed this error a couple days before the paths update was announced. I wonder if there’s any connection there?

Thanks for letting us know ​@Backbone. I’ve added you to the list so you’ll get an email notification from us as soon as it’s resolved. 

I personally wouldn’t have thought that the two would be related since the code for both apps are run independently, but I’ll definitely let you know if the team discovers that to be the case.

I also am having the same issue. My zaps stopped working about 14 days ago and I have not been able to fix this error - 

Failed to create a create in Google Chat

Got 500 calling POST https://zapier-bot-production.appspot.com/notify, expected 2xx.

​@clover and ​@Backbone Last week Zapier support confirmed that this is a Google Chat team issue and they are waiting for them to fix it. Has anyone had any luck contacting their support to get an update?

is there an update here? we need to use this integration

Hi everyone! 👋

​@MedicareHub I’ve added you to the list of folks being impacted. ​@clover looks like our Support team has already added you to it. We’ll be in touch by email once it’s sorted.

I’m not able to give an update on when this will be resolved by. However, from what I can tell it appears there may have been a change made to Google’s API recently that’s related to appearance of these 500 errors. Our engineers are working with Google to ensure this gets resolved as quickly as possible. Thanks for everyone’s continued patience here in the meantime, it’s much appreciated! 🤗

Hi! I have the same problem… What should to fix that? 

Please let me know on that email as well!

​@SamB any updates at all or?

​@Lander ​@Jaden ​@KamilM ​@MedicareHub ​@clover ​@Backbone 

I emailed Zapier support and got this response back. They are still working on it - no fix available yet. 

I've been reviewing the bug report that is affecting your Create Message in Google Chat actions.
 
While we know issues like this have a major impact on your workflows, we currently don't have any updates to share with you and I’m not able to provide an estimated timeframe for this resolution. There are many factors at play, so it’s challenging to predict exactly when an issue will be fixed.

What I can share is that the bug has been logged, and the relevant teams are aware of the issue. I’ve also confirmed that you will be notified at this email address as soon as there is an update or the issue is resolved.

​@dh_78669 thanks man

I’m getting this same error as well. Any fix yet?

Please add me to the list to be updated when this issue is fixed. Thank you!

Failed to create a create in Google Chat

Got 500 calling POST https://zapier-bot-production.appspot.com/notify, expected 2xx.

I’m encountering the same issue. Is there any fix available yet?

Please add me to the notification list for updates once this issue is resolved. Thank you!

Getting this same error as well. Can I be added to the notify list?

I am getting this error as well and need a fix for it ASAP. Please add me to the list of folks dealing with this bug. 

Receiving same error for several months by now... Are you planning to fix this issue?

Hi all 👋

I’m so sorry for the delay in replying here. I’ve checked on the bug report and there’s still no fix in place yet. Unfortunately, I’m unable to provide any sort of timeline as to when the developers of the Google Chat app will be able to get this fixed. I’ve ensured that everyone who’s reached out here has been added to the list of affected users to make sure you’re notified as soon as it’s sorted.

If there’s any change in the status of this bug in the meantime I’ll be sure to post an update here to let you all know. Really appreciate everyone’s patience in the meantime. 🙏

Hello. I have the same issue 
I needed to change the Google Account that sends out the chats. 
Now I am unable to make it work. 

Google is sending us here: 
https://support.google.com/chat/thread/369162066/zappier-to-google-chat-integration-bug-got-500-calling-post?hl=en

Hello everyone,

I had the same issue and discovered what happens.

You are probably trying to send messages in a chat with a different account than the authorized one.

In google chat you need to allow the correct account to send zapiers, needs to be the same one you connected to Zapier (not just allow zapier in the chat).

A chat can have multiple accounts authorized to send zapiers messages, to allow a new account in Google Chat type /zapier_settings, this command will show the option to allow Zaps with your current account (user).

Here is a image to help:

Hi there 👋

​@Nicolas Calderon - I’m so sorry that changing the Google account caused you to run into these 500 errors, and for the delay in my reply here. I’ve added you to the bug report so that you’ll be notified as soon as it’s sorted.

​@Joao Cardoso - thanks so much for sharing details of how you were able to get it working. Really appreciate you sharing this with the community! 🧡

For everyone here still affected by this issue can you give ​Joao Cardoso’s suggestion above a try, and let us know whether that resolves things? 🤞