Group channel changed
The group_channel:changed event fires when a group's built-in profile, extended group profile, or permission settings are updated. Use this event to keep group metadata in sync on your app server.
For the complete webhook setup and signature verification guide, see Webhooks overview.
Event type
group_channel:changed
Payload
Envelope
| Field | Type | Required | Description |
|---|---|---|---|
type | String | Yes | "group_channel:changed" |
id | String | Yes | Unique event ID. |
time | Long | Yes | Event generation time (Unix ms). |
data | Array | Yes | Array containing one group change object. See Data fields. |
Data fields
| Field | Type | Required | Description |
|---|---|---|---|
profiles | Array | Yes | List of group update records. Each element describes one group that was updated. See profiles[i] fields. |
profiles[i] fields
| Field | Type | Required | Description |
|---|---|---|---|
channelId | String | Yes | The group ID. |
channelName | String | Yes | The group name at the time of the update. |
time | Long | Yes | Time the update was made (Unix ms). |
userId | String | No | The user ID of the person who made the change. |
groupProfile | Object | No | Updated built-in group information (e.g., bulletin). |
groupExtProfile | Object | No | Updated custom (application-defined) group information. |
permissions | Object | No | Updated group permission configuration. |
About groupProfile
groupProfile contains Nexconn-defined group fields rather than app-defined extension data. Use this object for updates to the group's built-in attributes, such as the group bulletin.
Use groupExtProfile for your own application-specific group fields.
Example
JSON
{
"type": "group_channel:changed",
"id": "550e8400-e29b-41d4-a716-446655440009",
"time": 1730192400000,
"data": [
{
"profiles": [
{
"channelId": "group_001",
"channelName": "Dev Group",
"time": 1730192400000,
"userId": "user_001",
"groupProfile": {"bulletin": "Welcome"},
"groupExtProfile": {"tags": "dev"},
"permissions": {}
}
]
}
]
}