Actions89
- Direct API Actions
- CRM Actions
- Task Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Chat Actions
Overview
This node integrates with the Bitrix24 platform, specifically allowing users to delete a Task resource. It is useful in scenarios where automated workflows need to remove tasks from Bitrix24 based on certain triggers or conditions, such as cleaning up completed or obsolete tasks.
For example, you might use this node to automatically delete a task when a related deal is closed or canceled, helping keep your task list clean and relevant without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended for production), Webhook (simpler but less secure), or API Key authentication. |
| Task ID | The unique identifier of the task to be deleted. |
| Options | Additional optional parameters that can be provided as JSON objects: |
| - Filter | JSON object specifying filter criteria (not typically used for delete operation). |
| - Order | JSON object specifying sort order (not typically used for delete operation). |
| - Select | JSON array specifying which fields to select (not typically used for delete operation). |
| - Group | JSON object specifying group criteria (not typically used for delete operation). |
| - Custom Parameters | JSON object for any additional custom parameters to include in the request. |
| - Access Token | Optional access token string for authentication override. |
Output
The node outputs an array of items corresponding to the result of the delete operation. Each item contains a json field with the response data from Bitrix24.
- On success, the output typically includes confirmation of deletion or an empty result depending on Bitrix24's API response.
- On failure, if "Continue On Fail" is enabled, the output will contain an error object with:
error: The error message.resource: The resource name ("task").timestamp: The ISO timestamp when the error occurred.
The node does not output binary data.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication (recommended for production).
- Webhook URL authentication.
- API key authentication.
- Requires appropriate credentials configured in n8n for the chosen authentication method.
- Uses Bitrix24 REST API endpoints internally to perform operations.
Troubleshooting
Common Issues:
- Invalid or missing Task ID: Ensure the Task ID provided exists and is correct.
- Authentication failures: Verify that the selected authentication method is properly configured and valid.
- Insufficient permissions: The authenticated user must have rights to delete tasks in Bitrix24.
- Network or API errors: Check connectivity and Bitrix24 service status.
Error Messages:
- Errors returned by Bitrix24 API will be surfaced in the node output if "Continue On Fail" is enabled.
- Common error messages may include "Task not found", "Access denied", or "Invalid authentication".
Resolution:
- Double-check Task ID and authentication credentials.
- Confirm user permissions in Bitrix24.
- Review API limits or restrictions imposed by Bitrix24.
- Enable "Continue On Fail" to handle errors gracefully in workflows.