Event for Adding a New Workgroup onSonetGroupAdd
Scope:
sonetWho can subscribe: any user
The onSonetGroupAdd event is triggered when a new workgroup/project is added. This allows a third-party application to respond to the creation of new groups and perform necessary actions—such as data synchronization or sending notifications.
Events will not be sent to the application until the installation is complete. Check the application installation
What the Handler Receives
Data is transmitted as a POST request
{
"event": "ONSONETGROUPADD",
"event_handler_id": "655",
"data": {
"FIELDS": {
"ID": "6675"
}
},
"ts": "1736424182",
"auth": {
"access_token": "s6p6eclrvim6da22ft9ch94ekreb52lv",
"expires_in": "3600",
"scope": "sonet",
"domain": "some-domain.bitrix24.com",
"server_endpoint": "https://oauth.bitrix.info/rest/",
"status": "L",
"client_endpoint": "https://some-domain.bitrix24.com/rest/",
"member_id": "a223c6b3710f85df22e9377d6c4f7553",
"refresh_token": "4s386p3q0tr8dy89xvmt96234v3dljg8",
"application_token": "51856fefc120afa4b628cc82d3935cce"
}
}
|
Parameter |
Description |
|
event |
Symbolic event code. In this case— |
|
event_handler_id |
Event handler identifier |
|
data |
Object containing information about the addition of the new workgroup. Contains a single key |
|
data.FIELDS |
Object containing information about the fields of the new workgroup. The structure is described below |
|
ts |
Date and time the event was sent from the event queue |
|
auth |
Object containing authorization parameters and information about the account where the event occurred. The structure is described below |
Parameter FIELDS
|
Parameter |
Description |
|
ID |
Identifier of the new workgroup |
Parameter auth
Required parameters are marked with *
|
Name |
Description |
|
access_token |
Authorization token OAuth 2.0 |
|
expires_in |
Time in seconds until the token expires |
|
scope* |
Scope under which the event occurred |
|
domain* |
Address of Bitrix24 where the event occurred |
|
server_endpoint* |
Address of the Bitrix24 authorization server needed to refresh OAuth 2.0 tokens |
|
status* |
Status of the application that subscribed to this event:
|
|
client_endpoint* |
Common path for REST API method calls for Bitrix24 where the event occurred |
|
member_id* |
Identifier of Bitrix24 where the event occurred |
|
refresh_token |
Token for extending authorization OAuth 2.0 |
|
application_token* |
Token for secure event handling |
Authorization tokens are not always passed to the event handler. If the hit that initiated the event could not be linked to a specific Bitrix24 user, the tokens are not passed. Always check the contents of the auth key in the code.
It is recommended to store tokens obtained earlier during the application installation. Use them when working with the application interface in the form of embeds, widgets, and so on.