[GH-ISSUE #1117] Random HTTP/401 with webhook integration to Google Chat #777

New issue

Closed

opened 2026-02-25 23:43:33 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 23:43:33 +03:00

Owner

Originally created by @vrcdx64 on GitHub (Jan 23, 2025).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/1117

Hello,

I use the webhook integration to get notified when a check is down. The provider, behind it, is Google Chat. The configuration is simple, the webhook URL contains the chat ID, key and the token like: https://chat.googleapis.com/v1/spaces/<id1>/messages?key=<key>&token=<token>.

Randomly, the integration get a HTTP/401 unauthorized. But if I click on « Test » I have no problem, even if I spam the action.

The webhook URL is used by others app without problems. Do you have any idea

Do you have any idea? Thank you!

Originally created by @vrcdx64 on GitHub (Jan 23, 2025). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/1117 Hello, I use the webhook integration to get notified when a check is down. The provider, behind it, is Google Chat. The configuration is simple, the webhook URL contains the chat ID, key and the token like: `https://chat.googleapis.com/v1/spaces/<id1>/messages?key=<key>&token=<token>`. **Randomly**, the integration get a HTTP/401 unauthorized. But if I click on « Test » I have no problem, even if I spam the action. The webhook URL is used by others app without problems. Do you have any idea Do you have any idea? Thank you! <img width="589" alt="Image" src="https://github.com/user-attachments/assets/64cf0282-5d4b-4c30-88bf-af6c1104f2a9" />

kerem closed this issue

2026-02-25 23:43:33 +03:00

kerem commented

2026-02-25 23:43:33 +03:00

Author

Owner

@cuu508 commented on GitHub (Jan 23, 2025):

It would be good to see the precise JSON payload that gets posted – perhaps there are special characters in $NAME or $TAGS that lead to an invalid JSON syntax.

An easy way to see the payload would be to set up another webhook integration which posts to a request catcher service (requestbin, httpbin, that sort of service) and see what gets sent.

@cuu508 commented on GitHub (Jan 23, 2025): It would be good to see the precise JSON payload that gets posted – perhaps there are special characters in $NAME or $TAGS that lead to an invalid JSON syntax. An easy way to see the payload would be to set up another webhook integration which posts to a request catcher service (requestbin, httpbin, that sort of service) and see what gets sent.