Bitrix icon

Bitrix

Consume Bitrix24 REST API

Overview

This node integrates with the Bitrix24 REST API to perform operations on CRM resources. Specifically, for the Lead resource and the Delete operation, it deletes a lead record identified by its ID from the Bitrix24 CRM system.

Common scenarios where this node is useful include:

  • Automating cleanup of outdated or invalid leads in your CRM.
  • Integrating with other systems to remove leads after certain conditions are met (e.g., after conversion or disqualification).
  • Managing CRM data programmatically without manual intervention.

Example: Automatically delete a lead when it is marked as "Lost" in another system, keeping your Bitrix24 CRM clean and up-to-date.

Properties

Name Meaning
Authentication Method used to authenticate with Bitrix24 API. Options: OAuth2, Webhook
ID The unique identifier of the lead record to delete. Example: "12345"

Output

The node outputs JSON data representing the response from the Bitrix24 API after attempting to delete the lead. This typically includes confirmation of deletion or error details if the operation failed.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to Bitrix24 via either OAuth2 authentication or a webhook-based API key.
  • Proper credentials must be configured in n8n to authorize API requests.
  • Network access to Bitrix24 REST API endpoints.

Troubleshooting

  • Invalid ID Error: If the provided lead ID does not exist or is incorrect, the API will return an error. Verify the ID before running the node.
  • Authentication Failures: Ensure that the selected authentication method is correctly set up and the credentials are valid.
  • Permission Issues: The API user must have sufficient permissions to delete leads in Bitrix24.
  • API Rate Limits: Excessive requests may trigger rate limiting; implement retries or delays if needed.

Links and References

Discussion