Event on Task Deletion OnTaskDelete
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
Scope:
taskWho can subscribe: any user
The event is triggered after a task is deleted.
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
array(
'event' => 'ONTASKDELETE',
'data' => array(
'FIELDS_BEFORE' => array('ID' => 123),
'FIELDS_AFTER' => 'undefined',
'IS_ACCESSIBLE_BEFORE' => 'undefined',
'IS_ACCESSIBLE_AFTER' => 'N',
),
'ts' => '1466439714',
'auth' => array(
'access_token' => 's6p6eclrvim6da22ft9ch94ekreb52lv',
'expires_in' => '3600',
'scope' => 'crm',
'domain' => 'some-domain.bitrix24.com',
'server_endpoint' => 'https://oauth.bitrix.info/rest/',
'status' => 'F',
'client_endpoint' => 'https://some-domain.bitrix24.com/rest/',
'member_id' => 'a223c6b3710f85df22e9377d6c4f7553',
'refresh_token' => '4s386p3q0tr8dy89xvmt96234v3dljg8',
'application_token' => '51856fefc120afa4b628cc82d3935cce',
),
)
Required parameters are marked with *
|
Parameter |
Description |
|
event* |
Symbolic event code, in this case |
|
data* |
Array with data of the deleted task |
|
ts* |
Date and time of the event sent from the event queue |
|
auth* |
Authorization parameters and information about the account where the event occurred |
Parameter data[]
Required parameters are marked with *
|
Name |
Description |
|
FIELDS_BEFORE* |
Fields of the task before the event (detailed description provided below). If there are no available task fields, this field will contain the value |
|
FIELDS_AFTER* |
Fields of the task after the event (detailed description provided below). If there are no available task fields, this field will contain the value |
|
IS_ACCESSIBLE_BEFORE* |
Whether the task was readable before the event (detailed description provided below) |
|
IS_ACCESSIBLE_AFTER* |
Whether the task became readable after the event (detailed description provided below) |
Field FIELDS_BEFORE
Required parameters are marked with *
|
Name |
Description |
|
ID* |
Identifier of the deleted task |
Required parameters are marked with *
Field FIELDS_AFTER
Required parameters are marked with *
|
Name |
Description |
|
ID* |
Identifier of the deleted task |
Field IS_ACCESSIBLE_BEFORE
Required parameters are marked with *
|
Name |
Description |
|
IS_ACCESSIBLE_BEFORE* |
Possible values:
|
Field IS_ACCESSIBLE_AFTER
Required parameters are marked with *
|
Name |
Description |
|
IS_ACCESSIBLE_AFTER* |
Possible values:
|
Code Examples
How to Use Examples in Documentation
try
{
const response = await $b24.callMethod(
'event.bind',
{
"event": "onTaskDelete",
"handler": "https://example.com/handler.php"
}
);
const result = response.getData().result;
console.info(result);
}
catch( error )
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'event.bind',
[
'event' => 'onTaskDelete',
'handler' => 'https://example.com/handler.php',
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
// Your logic for processing data
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error binding event: ' . $e->getMessage();
}
BX24.callMethod(
'event.bind',
{
"event": "onTaskDelete",
"handler": "https://example.com/handler.php"
},
function(result) {
if (result.error()) {
console.error(result.error());
} else {
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'event.bind',
[
'event' => 'onTaskDelete',
'handler' => 'https://example.com/handler.php'
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Continue Learning
- Overview of Events When Working with Tasks
- Event on Task Update OnTaskUpdate
- Event on Task Addition OnTaskAdd