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 "Update Section" operation allows users to update a section within a Bitrix24 list. This is useful for managing categorized data or segments within lists, such as updating metadata or custom fields of a particular section.

Common scenarios include:

  • Modifying properties of a section in a Bitrix24 list to reflect changes in categorization.
  • Automating updates to sections based on external triggers or workflows.
  • Synchronizing section data between Bitrix24 and other systems.

Example: Automatically update the name or custom attributes of a project phase (section) in a task list when triggered by an external event.

Properties

Name Meaning
Authentication Method to authenticate with Bitrix24: OAuth2, Webhook URL, or API Key.
List ID The identifier of the Bitrix24 list containing the section to update.
Section ID The identifier of the specific section within the list to update.
Fields One or more fields to set on the section. Each field has:
- Field Name: The name/key of the field to update.
- Field Value: The new value to assign to that field.
Options Additional optional parameters:
- Access Token Override the default credential token with a specific access token string.
- Filter JSON object specifying filter criteria (not typically used for update section but available).
- Order JSON object specifying sort order (not typically used for update section but available).
- Select Comma-separated list of fields to select (not typically used for update section but available).

Output

The node outputs an array of items where each item contains a json property representing the response from Bitrix24 after attempting to update the section. The structure of this JSON depends on the Bitrix24 API response but generally includes confirmation of updated fields or error details if the update failed.

If the node encounters an error and "Continue On Fail" is enabled, it outputs an item with an error field describing the issue, along with the resource name and a timestamp.

No binary data output is indicated for this operation.

Dependencies

  • Requires valid authentication with Bitrix24 via one of the supported methods: OAuth2, Webhook URL, or API Key.
  • The node internally uses Bitrix24 API calls to perform operations; thus, network connectivity and correct API permissions are necessary.
  • No additional external dependencies beyond Bitrix24 credentials and API access.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication tokens leading to authorization errors.
    • Incorrect List ID or Section ID causing "not found" errors.
    • Insufficient permissions to update sections in the specified list.
    • Malformed field names or values resulting in API validation errors.

  • Error Messages:

    • Errors returned from Bitrix24 API will be included in the output JSON under an error key if "Continue On Fail" is enabled.
    • Common error messages may include "Access Denied", "Section Not Found", or "Invalid Field".

  • Resolutions:

    • Verify and refresh authentication credentials.
    • Double-check List ID and Section ID values.
    • Ensure the user or API key has appropriate permissions.
    • Validate field names and values against Bitrix24 documentation.

Links and References

Discussion