Bitrix24 icon

Bitrix24

Work with Bitrix24 API

Actions25

Overview

This node integrates with the Bitrix24 CRM API to perform various operations on CRM records such as leads, deals, contacts, and companies. Specifically, for the Delete operation under the Default resource, it deletes a record identified by its ID from the specified CRM entity.

Common scenarios where this node is useful include automating cleanup of outdated or incorrect CRM entries, removing duplicates, or integrating deletion workflows triggered by external events.

For example, you could use this node to automatically delete a contact record when a customer unsubscribes from your mailing list, or remove a deal that was canceled.

Properties

Name Meaning
ID The unique identifier of the 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 record. Typically, this 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 the failure"
  }
]

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.
  • The webhook URL must be correctly set in the credentials to allow API calls.
  • No additional environment variables are strictly required beyond those provided by the Bitrix24 credential setup.

Troubleshooting

  • Missing Credentials or Webhook URL: The node will throw errors if no credentials are found or if the webhook URL is missing. Ensure the Bitrix24 API credentials are properly configured with a valid webhook URL.
  • Invalid Record ID: If the provided ID does not exist or is invalid, the API may return an error or indicate the record was not found. Verify the ID before attempting deletion.
  • API Errors: Network issues, permission problems, or API limits can cause failures. Check the error messages returned in the output for clues.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if one deletion fails, returning error details in the output.

Links and References

Discussion