Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node interacts with Bitrix24's Lists resource, specifically to retrieve an element from a section within a list. The "Get Section Element" operation fetches data about a particular element located in a specified section of a Bitrix24 list.

Common scenarios for this node include:

  • Retrieving detailed information about a specific item stored in a Bitrix24 list section.
  • Integrating Bitrix24 list data into workflows that require accessing structured list elements.
  • Automating processes that depend on fetching list elements by their section and list IDs.

Practical example:

  • A workflow that triggers when a new task is created and needs to pull related data from a Bitrix24 list section element to enrich the task details or perform conditional logic based on that data.

Properties

Name Meaning
Authentication Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication.
List ID The unique identifier of the Bitrix24 list from which to get the section element.
Section ID The unique identifier of the section within the list where the element resides.
Options Additional optional parameters:
  Access Token Use a specific access token instead of the one from credentials.
  Filter JSON object defining filter criteria to narrow down the elements retrieved.
  Order JSON object specifying the sort order of the results.
  Select Comma-separated string listing specific fields to select from the element.

Output

The node outputs JSON data representing the requested section element from the Bitrix24 list. This JSON contains the fields and values of the element as returned by the Bitrix24 API.

If binary data were involved (not indicated here), it would typically represent files or attachments related to the element, but this operation focuses on JSON data retrieval only.

Dependencies

  • Requires valid authentication with Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
  • Needs proper configuration of credentials in n8n corresponding to the chosen authentication method.
  • Relies on Bitrix24 API availability and permissions granted to the authenticated user or application.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication tokens leading to authorization errors.
    • Incorrect List ID or Section ID causing "not found" or empty responses.
    • Malformed JSON in the Filter or Order options causing API request failures.

  • Error messages:

    • Authorization errors: Check that the credentials are correctly set up and have sufficient permissions.
    • "Element not found": Verify that the List ID and Section ID are correct and that the element exists.
    • JSON parsing errors: Ensure that the Filter and Order inputs are valid JSON strings.

Resolving these usually involves verifying credentials, confirming IDs, and validating JSON syntax in options.

Links and References

Discussion