Actions25
Overview
This node integrates with the Bitrix24 CRM system to perform various operations on CRM resources such as Leads, Deals, Contacts, and Companies. Specifically for the Company resource with the Delete operation, it deletes a company record identified by its unique 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 deletions, or managing CRM data lifecycle programmatically.
Example: Automatically deleting a company record in Bitrix24 when it is removed from an external ERP system, ensuring data consistency across platforms.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the company record to delete. This is a required string input. |
Output
The output is a JSON array containing the response from the Bitrix24 API after attempting to delete the specified company record. Typically, this includes a success confirmation or error details if the deletion failed.
Example output structure:
[
{
"result": true
}
]
or in case of failure:
[
{
"error": "Error message describing the failure"
}
]
No binary data output is produced by this node.
Dependencies
- Requires an active Bitrix24 API connection configured with a valid webhook URL and authentication credentials.
- The node uses HTTP POST requests to Bitrix24's REST API endpoints.
- The webhook URL must be correctly set in the credentials to form API request URLs.
- No additional environment variables are strictly required beyond those provided by the Bitrix24 credential setup.
Troubleshooting
Missing Credentials or Webhook URL:
Error: "No credentials got returned!" or "Webhook URL is required!"
Resolution: Ensure that the Bitrix24 API credentials are properly configured in n8n, including a valid webhook URL.Invalid Record ID:
If the provided ID does not exist or is malformed, the API may return an error or no result.
Resolution: Verify the ID value corresponds to an existing company record in Bitrix24.API Request Failures:
Network issues or permission errors can cause the API call to fail.
Resolution: Check network connectivity, API permissions, and ensure the webhook URL has sufficient rights to delete company records.Unhandled Errors:
The node attempts to catch and report errors; however, unexpected errors might occur.
Resolution: Enable "Continue On Fail" option in the node settings to handle errors gracefully during batch processing.