In a discussion titled ‘Weird bugs/issues with webhooks’, jordan-violet reports inconsistencies in webhook data, specifically noting that the group_updated_event is triggered when updating a group field, but the corresponding data (like automatic_membership_email_domains) is missing from the webhook payload. They also question the meaning of the automatic field in the response, which appears unrelated to the updated field. simon clarifies that the automatic field indicates whether a group is system-generated (like trust level or staff groups) versus user-created, and confirms that automatic_membership_email_domains is not included in the webhook serializer — despite being relevant to the trigger. Simon suggests this field should be added to the webhook payload and that such mappings should be documented publicly, rather than requiring users to inspect source code. jordan-violet agrees, expressing surprise that an event is triggered without including the data that caused it, and appreciates the clarification while reinforcing the need for better documentation.
There are a lot of webhooks that do not seem to be up-to-date with the database objects that they intend to serve up. While quite a few examples, here is the latest.
The group_updated_event event is triggered, but this information is nowhere to be found. To add to this, there is a field called “automatic” in the webhook response object that is set to true/false, but it doesn’t seem to be related to this field.
Is there any documentation that clearly defines what the response objects are mapped to when the webhook is triggered?
The “Automatic” field is the group’s automatic_membership_email_domains property. As you can see, it’s not in the attributes list.
The “Automatic” field that you’re seeing in the payload indicates whether or not the group is an “automatic” group. Essentially, the built in trust level and staff groups are automatic. Custom groups that you create are not automatic.
It seems like it would be easy to add the automatic_membership_email_domains field to the group webhook serializer. Also, this information should be available without having to look at the source code.
Yes! Thanks for finding this for me, at least I know that it’s not there. Quite odd that it triggers the event, only for…the event to not have the data it was triggered by.
