Actions25
Overview
This node integrates with the Bitrix24 CRM system via its API, allowing users to perform various operations on CRM records such as Leads, Deals, Contacts, and Companies. Specifically, the "Delete" operation enables users to remove a record from the selected resource by specifying its ID.
Common scenarios for using this node include automating CRM data management tasks like cleaning up outdated or incorrect records, synchronizing external databases by removing deleted entries, or implementing business workflows that require conditional deletion of CRM entities.
For example, you might use this node to delete a Lead record after it has been converted into a Deal, ensuring your CRM stays organized without redundant data.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the record to delete. This is required to specify which record in the chosen resource should be removed. |
Output
The node outputs an array of JSON objects representing the response from the Bitrix24 API for each processed input item. For the Delete operation, the output typically contains confirmation of the deletion status or any error messages returned by the API.
No binary data is produced by this node.
Example output JSON snippet for a successful deletion:
{
"result": true
}
If an error occurs, the output may contain an error message describing the issue.
Dependencies
- Requires an active Bitrix24 API connection configured with a valid webhook URL credential.
- Uses HTTP POST requests to interact with Bitrix24's REST API endpoints.
- The webhook URL must have sufficient permissions to perform delete operations on the specified resource.
Troubleshooting
- Missing Credentials: If the node throws an error about missing credentials or webhook URL, ensure that the Bitrix24 API credential is properly set up and includes a valid webhook URL.
- Invalid ID: Providing an incorrect or non-existent record ID will result in an API error. Verify the ID before attempting deletion.
- Permission Issues: Insufficient permissions on the webhook or API user can cause failures. Confirm that the API token has rights to delete records.
- API Errors: Network issues or Bitrix24 service downtime can cause request failures. Check connectivity and Bitrix24 status.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output.
Links and References
- Bitrix24 REST API Documentation
- Bitrix24 CRM API Methods
- n8n documentation on creating custom nodes