Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node interacts with Bitrix24's Lists resource, specifically supporting the "Delete Field" operation. It allows users to delete a custom field from a specified list within Bitrix24. This is useful for maintaining and managing list schemas by removing obsolete or unwanted fields.

Common scenarios include:

  • Cleaning up lists by removing deprecated fields.
  • Automating list schema updates as part of larger workflows.
  • Managing dynamic data structures in Bitrix24 Lists programmatically.

Example: Automatically deleting a custom field from a project task list when it is no longer needed.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication.
List ID The identifier of the list from which the field will be deleted.
Field ID The identifier of the field to delete from the list.
Options Additional optional parameters:
- Access Token Use a specific access token instead of the one from credentials.
- Filter JSON-formatted filter criteria (not typically used for delete field but available).
- Order JSON-formatted sort order (not typically used for delete field but available).
- Select Comma-separated list of fields to select (not typically used for delete field but available).

Output

The node outputs an array of items where each item contains a json object representing the result of the delete operation. If successful, the output typically confirms the deletion or returns relevant status information from Bitrix24.

If an error occurs and the node is configured to continue on failure, the output includes an error field with the error message, the resource name, and a timestamp.

No binary data output is involved in this operation.

Dependencies

  • Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
  • Needs appropriate permissions in Bitrix24 to delete fields from lists.
  • No additional external services beyond Bitrix24 API are required.
  • Proper configuration of credentials in n8n is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing List ID or Field ID will cause the operation to fail.
    • Insufficient permissions in Bitrix24 to modify list fields.
    • Incorrect authentication method or expired tokens.

  • Error Messages:

    • Errors returned from Bitrix24 API will be propagated. Common messages might include "Field not found", "Access denied", or "Invalid list ID".
    • If the node is set to continue on failure, errors are included in the output JSON under the error property.

  • Resolution Tips:

    • Verify that the List ID and Field ID are correct and exist in Bitrix24.
    • Ensure the authentication credentials have sufficient rights.
    • Refresh or reconfigure authentication tokens if expired.
    • Check network connectivity to Bitrix24 API endpoints.

Links and References

Discussion