[GH-ISSUE #771] improvement of Zulip integration docs #539

New issue

Closed

opened 2026-02-25 23:42:48 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 23:42:48 +03:00

Owner

Originally created by @tiltX on GitHub (Dec 28, 2022).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/771

I've had issues setting up a Zulip integration. Sending a notification to a stream worked fine but sending it to a private user didn't work:

Could not send a test notification. Received status code 400 with a message: "Invalid email '...'".

The problem was a setting in Zulip's permission settings: "Who can access user email addresses" was set to "Administrators and Moderators" which excluded regular members from accessing a user's email address. However, the HC bot is set up to be a regular member. Because of that, the integration couldn't send the notification to the given user.

It might be helpful to add this to the the page where you set up the Zulip integration.

Originally created by @tiltX on GitHub (Dec 28, 2022). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/771 I've had issues setting up a Zulip integration. Sending a notification to a stream worked fine but sending it to a private user didn't work: Could not send a test notification. Received status code 400 with a message: "Invalid email '...'". The problem was a setting in Zulip's permission settings: "Who can access user email addresses" was set to "Administrators and Moderators" which excluded regular members from accessing a user's email address. However, the HC bot is set up to be a regular member. Because of that, the integration couldn't send the notification to the given user. It might be helpful to add this to the the page where you set up the Zulip integration.

kerem closed this issue

2026-02-25 23:42:48 +03:00

kerem commented

2026-02-25 23:42:49 +03:00

Author

Owner

@cuu508 commented on GitHub (Jan 12, 2023):

Thanks for the suggestion.

Did you resolve the issue by changing the "Who can access user email addresses" setting?

Looks like there's a possible workaround that would require only a small code change on the Healthchecks side: specify the user by User ID, not by their email.

In Zulip, you can look up user's id in their profile (when you click on an user, or on a three dots button next to an user, there's usually a "View Profile" option):

Zulip REST API accepts user ids for sending private messages, and they work even when "Who can access user email addresses" is set to "Administrators and Moderators".

Healthchecks would require a small code change to support user ids. And docs would indeed need to be updated to explain when to use user emails, and when to use user ids, and how to look the user ids up.

@cuu508 commented on GitHub (Jan 12, 2023): Thanks for the suggestion. Did you resolve the issue by changing the "Who can access user email addresses" setting? Looks like there's a possible workaround that would require only a small code change on the Healthchecks side: specify the user by User ID, not by their email. In Zulip, you can look up user's id in their profile (when you click on an user, or on a three dots button next to an user, there's usually a "View Profile" option): ![image](https://user-images.githubusercontent.com/661859/212041049-b4416ee1-8cb2-49c7-869c-e43423cefd96.png) Zulip REST API accepts user ids for sending private messages, and they work even when "Who can access user email addresses" is set to "Administrators and Moderators". Healthchecks would require a small code change to support user ids. And docs would indeed need to be updated to explain when to use user emails, and when to use user ids, and how to look the user ids up.