Actions25
Overview
This node integrates with the Bitrix24 CRM system to manage Deal records. Specifically, the Delete operation allows users to remove a Deal record from Bitrix24 by specifying its unique ID. This is useful in scenarios where deals are no longer relevant or were created in error and need to be cleaned up automatically as part of a workflow.
Practical examples include:
- Automatically deleting deals that have been marked as lost or cancelled in another system.
- Cleaning up test or temporary deal records after certain conditions are met.
- Removing duplicate deals based on external validation.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Deal record to delete. This is required to specify which deal should be removed. |
Output
The output JSON contains the response from the Bitrix24 API after attempting to delete the deal. Typically, it includes a success confirmation or an error message if the deletion failed.
Example output structure:
{
"result": true
}
or in case of failure:
{
"error": "Error message describing why deletion failed"
}
No binary data is output 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 for performing operations.
- The webhook URL must be correctly set in the credentials to form API request URLs.
Troubleshooting
- Missing Credentials or Webhook URL: The node will throw errors if the Bitrix24 API credentials or webhook URL are not provided or invalid. Ensure these are configured properly in n8n.
- Invalid or Nonexistent ID: If the specified Deal ID does not exist, the API may return an error or indicate the record was not found. Verify the ID before attempting deletion.
- API Errors: Network issues or permission problems can cause API calls to fail. Check connectivity and user permissions in Bitrix24.
- Continue On Fail: If enabled, the node will continue processing other items even if one deletion fails, returning error details in the output.
Common error messages:
- "No credentials got returned!" — Credentials are missing or misconfigured.
- "Webhook URL is required!" — The webhook URL is not set in the credentials.
- API error messages returned from Bitrix24 indicating issues like invalid ID or insufficient permissions.