Actions25
Overview
This node integrates with the Bitrix24 CRM system, allowing users to manage various CRM resources such as Leads, Deals, Contacts, and Companies. Specifically, for the Company resource with the Delete operation, the node deletes a company record identified by its ID from the Bitrix24 CRM.
Common scenarios where this node is beneficial include automating cleanup of outdated or incorrect company records, integrating with other systems to synchronize data deletions, or managing CRM data lifecycle programmatically.
For example, if a company is no longer a client or was entered erroneously, this node can be used in an automation workflow to remove that company's record from Bitrix24 automatically by specifying its unique ID.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the company record to delete. This is required to specify which company should be removed from Bitrix24. |
Output
The node outputs a JSON array where each element corresponds to the result of the delete operation for each input item. The structure of each output object typically includes:
- A success indicator or status returned by the Bitrix24 API.
- Any error messages if the deletion failed.
No binary data is output by this node.
Example output JSON snippet:
[
{
"result": true
}
]
Here, "result": true indicates successful deletion.
Dependencies
- Requires an active Bitrix24 API connection configured via an API key credential or webhook URL.
- The node uses the Bitrix24 webhook URL to send HTTP POST requests to perform operations.
- The user must have appropriate permissions in Bitrix24 to delete company records.
Troubleshooting
- Missing Credentials or Webhook URL: The node will throw errors if the Bitrix24 credentials or webhook URL are not set or invalid. Ensure these are correctly configured in n8n.
- Invalid or Missing ID: If the provided company ID does not exist or is empty, the API call will fail. Verify the ID before running the node.
- API Errors: Network issues or permission problems may cause API request failures. Check connectivity and user permissions in Bitrix24.
- Continue On Fail: If enabled, the node will continue processing remaining items even if some deletions fail, returning error details per item.