Bitrix24 Auxiliary

Overview

This node interacts with Bitrix24 CRM to manage sales funnel statuses ("Статус воронки"). Specifically, the Delete operation for the "Статус воронки" resource allows users to delete a status element from a sales funnel category in Bitrix24.

Typical use cases include automating cleanup or maintenance of sales funnel stages by removing obsolete or incorrect statuses programmatically. For example, if a sales process changes and certain deal stages are no longer relevant, this node can be used to delete those statuses automatically based on their ID.

Properties

Output

The output JSON array contains objects representing the result of each deletion attempt. For the Delete operation on a status, each successful item includes:

• success: A boolean indicating if the deletion was successful (true).
• id: The ID of the deleted status.

If an error occurs during deletion, the output may contain an object with an error property describing the issue.

No binary data is output by this node.

Example output for a successful deletion:

[
  {
    "success": true,
    "id": "12345"
  }
]

Dependencies

• Requires a valid Bitrix24 API webhook URL credential configured in n8n.
• The node uses HTTP POST requests to Bitrix24's webhook endpoints to perform operations.
• The webhook URL must have permissions to delete statuses in the specified sales funnel.

Troubleshooting

• Common issues:

  • Missing or invalid webhook URL credential will cause the node to fail with an error about missing credentials or webhook URL.
  • Providing an incorrect or non-existent status ID will likely result in an API error from Bitrix24.
  • Network or permission issues on the Bitrix24 side can cause API errors.

• Error messages:

  • "No credentials got returned!" — Ensure the Bitrix24 API credential is properly set up and selected.
  • "Webhook URL is required!" — Verify that the webhook URL is correctly configured in the credentials.
  • "Bitrix24 API error: <message>" — Indicates an error response from Bitrix24 API; check the message for details such as invalid ID or insufficient permissions.

• To handle errors gracefully, enable the node’s "Continue On Fail" option to allow processing multiple items even if some deletions fail.

Links and References

• Bitrix24 REST API Documentation
• Bitrix24 CRM Statuses API
• n8n documentation on Using Credentials