Creating a topic or a post sends the user_updated webhook


(Simon Cossar) #1

If a User Event webhook is activated, creating a topic or a post sends the user_updated webhook. Tested on the latest Discourse.


(Sam Saffron) #2

Well I guess we are assuming that something like “last posted at” just changed and pushing that across.


(Jeff Atwood) #3

That is a very odd interpretation of the meaning, I would expect only a user preference was updated. Possibly by the user only.


(Allen - Watchman Monitoring) #4

I’d also expect a webhook when badge & group memberships are changed.


(Simon Cossar) #5

This is how it used to work.

This would be very useful.


(Jeff Atwood) #6

Hmm this is a regression then – who touched webhooks last @tgxworld?


(Alan Tan) #7

Not me, Rails 5 touched it :stuck_out_tongue:

I’ll have a look


(Simon Cossar) #9

A user webhook is also being sent when a user logs in or out. Creating a user through SSO is sending 3 user webhooks. First a user_created one for the new user. Then user_updated for the same user, then user_updated for the discobot. This is tested on a live version of Discourse.


(Alan Tan) #10

It looks like the behavior of the user_updated event was changed in

which triggers as long as a column on the user is changed. @zogstrip Do we need all the columns to trigger the event? If not I’ll add a a filter that checks the columns which have changed against the UserUpdated::OPTION_ATTR constant.


How to differentiate webhooks for created, approved or updated
(Régis Hanol) #11

I needed it for the group-tracker plugin

In that case I only need the primary_group_id so UserUpdater::OPTION_ATTR will have to be updated.


(Alan Tan) #12

Fixed in



How to differentiate webhooks for created, approved or updated
(Jeff Atwood) #13