Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node integrates with Bitrix24, a CRM and business platform, to perform various operations on its resources. Specifically, the "Lists" resource with the "Add Section" operation allows users to add a new section to a specified list within Bitrix24. This is useful for organizing list data into sections, which can help segment or categorize entries more effectively.

Practical scenarios include:

  • Adding a new category or grouping within a project management list.
  • Creating sections in a customer feedback list to separate different types of feedback.
  • Structuring inventory lists by adding sections for different product categories.

Properties

Name Meaning
Authentication Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication.
List ID The identifier of the Bitrix24 list where the new section will be added.
Fields A collection of fields to set for the new section. Each field has a name and a corresponding value.
Options Additional optional parameters:
- Access Token: Use a specific access token instead of credentials.
- Filter: JSON object to filter data.
- Order: JSON object defining sort order.
- Select: Comma-separated list of fields to select.

Output

The node outputs an array of items, each containing a json property with the response from Bitrix24 after attempting to add the section. The exact structure depends on Bitrix24's API response but typically includes details about the newly created section such as its ID and any metadata returned by the API.

If an error occurs and the node is configured to continue on failure, the output item will contain an error field describing the issue, along with the resource name and a timestamp.

No binary data output is indicated.

Dependencies

  • Requires valid authentication with Bitrix24 via one of the supported methods (OAuth2, Webhook URL, or API Key).
  • Uses Bitrix24 API endpoints internally to perform operations.
  • No additional external dependencies beyond standard n8n environment and Bitrix24 credentials.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication tokens leading to authorization errors.
    • Incorrect List ID causing the API to fail to find the target list.
    • Malformed field names or values that do not conform to Bitrix24's expected schema.

  • Error Messages:

    • Errors returned from Bitrix24 API are passed through; typical messages might include "Access Denied", "List Not Found", or validation errors on fields.
    • If the node is set to continue on failure, errors are included in the output JSON under the error key.

  • Resolutions:

    • Verify and refresh authentication credentials.
    • Double-check the List ID and ensure it exists in Bitrix24.
    • Validate field names and values against Bitrix24 documentation for list sections.

Links and References

Discussion