# Webhook documentation incorrect?

**URL:** <https://community.sendbird.com/t/webhook-documentation-incorrect/4008>\
**Category:** API\
**Tags:** webhook\
**Created:** [February 22, 2022, 11:56pm UTC](https://community.sendbird.com/t/webhook-documentation-incorrect/4008 "2022-02-22T23:56:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![david](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/david/32/1901_2.png) [@david](https://community.sendbird.com/u/david)\
**Post date:** [February 22, 2022, 11:56pm UTC](https://community.sendbird.com/t/webhook-documentation-incorrect/4008/1 "2022-02-22T23:56:57Z")

</div>

Hi, we’re trying to display custom messages in group channels for various actions. One of which is “{this user} changed the group name to {new group name}”.

The webhook [documentation](https://sendbird.com/docs/chat/v3/platform-api/guides/webhooks#2-group_channel-changed) for the `group_channel:changed` seems to be incorrect. It claims there is an `inviter` user field. I figured this was a typo for the user who made the change, but upon inspection of the request I don’t see any data that links the change to a user under that field or any other.

Please tell me if I’m incorrect here! I’d appreciate any help. If the docs are indeed wrong, I’d like to make a feature request for a `changer` field to include the user who made the change.

---

<div class="post-metadata">

**Author:** ![ScottKim](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/scottkim/32/3330_2.png) [@ScottKim](https://community.sendbird.com/u/ScottKim)\
**Post date:** [February 23, 2022, 3:43am UTC](https://community.sendbird.com/t/webhook-documentation-incorrect/4008/3 "2022-02-23T03:43:23Z")

</div>

It’s odd that group\_channel:changed has an “inviter” field, and there seems to be an error in the documentation. Even when I did a real webhook test, the “Invite” field didn’t show up.

The webhook data you receive is ok.

Feature requests can be made from the dashboard, but if a request is received, the ETA will not know if it is a non-critical feature.

Dashboard \> Contact us
