Bitrix24Install

Overview

This node integrates with the Bitrix24 platform, allowing users to interact with various Bitrix24 resources such as CRM entities and business data. Specifically, for the Data Storage resource and the Delete Entity Section operation, it enables deleting a specified section (or segment) of an entity within Bitrix24.

Typical use cases include:

• Automating cleanup or removal of obsolete or unwanted sections in CRM entities.
• Managing entity structures dynamically based on workflow conditions.
• Integrating Bitrix24 entity management into broader automation pipelines.

For example, a user might delete a custom section from a CRM contact record when that section is no longer relevant, triggered by some external event or condition.

Properties

Output

The node outputs JSON data representing the result of the deletion operation. On success, this typically includes confirmation details from Bitrix24 about the deleted section. If an error occurs, the output JSON contains an error field with the error message, along with the resource name and a timestamp.

No binary data output is produced by this operation.

Example successful output snippet:

{
  "result": {
    "success": true,
    "deletedSectionId": "12345"
  }
}

Example error output snippet (when continuing on failure):

{
  "error": "Section not found",
  "resource": "entity",
  "timestamp": "2024-06-01T12:00:00.000Z"
}

Dependencies

• Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
• Relies on Bitrix24 API endpoints to perform operations; thus, network connectivity and proper API permissions are necessary.
• No additional external libraries beyond those bundled with the node are required.

Troubleshooting

• Common Issues:

  • Invalid or missing Section ID: Ensure the Section ID provided exists and is correct.
  • Authentication failures: Verify that the chosen authentication method is correctly configured and authorized.
  • API permission errors: The authenticated user must have rights to delete entity sections.
  • Network or connectivity problems: Confirm that the node can reach Bitrix24 API endpoints.

• Error Messages:

  • "Section not found": The specified Section ID does not exist or is inaccessible. Check the ID and permissions.
  • "Authentication failed": Credentials are invalid or expired. Re-authenticate or update credentials.
  • "Insufficient permissions": The user lacks rights to delete sections. Adjust user roles or permissions in Bitrix24.
  • Other API errors will be passed through in the error field; consult Bitrix24 API documentation for details.

• When the node is set to continue on fail, errors are returned in the output JSON instead of stopping execution.

Links and References

• Bitrix24 Official API Documentation
• Bitrix24 CRM Entity Management
• n8n Documentation on Creating Custom Nodes