Any chance the user_badge webhooks could include username along with user_id? Currently the payload for a user_badge event looks like this: { "user_badge": { "id": 123456, "granted_at": "2026-09-25T14:54:42.073Z", "created_at": "2026-09-26T05:34:12.965Z", "post_id": 234567, "p…

FWIW, my workaround for non-standard webhooks or when I need additional data is to do it via Workflows and then send that to n8n.

[imagen] burke: I’m creating an external service that I was hoping to trigger when specific badge(s) are granted; however, it needs the username and badge webhooks only returns user IDs. Fwiw, fetching username from user id is just one API call away, unless you’re manually granting thousands …

[imagen] putty: FWIW, my workaround for non-standard webhooks or when I need additional data is to do it via Workflows and then send that to n8n. Thanks! I’ll look into Workflows.

[imagen] itsbhanusharma: Fwiw, fetching username from user id is just one API call away, unless you’re manually granting thousands of badges in an instant, you should be fine with the default API limits. That’s great to hear! Could you please provide details about that one API call that isn’t…

What’s the issue with an admin API key? This is supposed to be a background job ig?

[imagen] itsbhanusharma: What’s the issue with an admin API key? This is supposed to be a background job ig? Principal of Least Privilege. This external service will be running on another server and only needs read access to Discourse to do it’s job. The fewer master keys floating around acro…

This brings up the interesting point of why isn’t there a public-facing endpoint to get a user by id that shows only public fields, if login_required is not selected. It would be useful, no? I wonder why it was not made. Or maybe only logged in users could get such a privilege, but either way, there…

This is because for all matters and purposes user IDs are essentially an internal convention in discourse and we are expected to rely on usernames that are much more prominent across the board.

Which brings us back to the original request. The webhook should adhere to that concept and send the username, not the user ID.

[imagen] RGJ: Which brings us back to the original request. The webhook should adhere to that concept and send the username, not the user ID. Agreed! This seems like the best solution. Adding username and granted_by_username and deprecating user_id and granted_by_id could allow for a non-brea…

¿Se podrían incluir los nombres de usuario en el payload del webhook user_badge?

Soporte del producto

RGJ (Richard - Communiteq) 30 Septiembre, 2026 07:13 10

Lo que nos lleva de vuelta a la solicitud original. El webhook debe seguir ese concepto y enviar el nombre de usuario, no el ID de usuario.

Tema		Respuestas	Vistas
Webhooks feedback Development	33	11400	21 Marzo 2017
Grant a custom badge through the API Integrations rest-api , how-to	9	8064	18 Noviembre 2023
Improved badge granting workflow Feature badges , completed	29	5254	23 Enero 2018
Wishlist: visual cue for "user got a badge for this post" Feature badges	36	2200	5 Diciembre 2024
Bulk Award a badge to a set of users Announcements badges , new-feature	28	6534	31 Marzo 2025

¿Se podrían incluir los nombres de usuario en el payload del webhook user_badge?

Temas relacionados