Bitrix24Install

Overview

This node integrates with the Bitrix24 platform, specifically allowing users to update an entity section within Bitrix24's CRM or business data storage. The "Update Entity Section" operation modifies properties of a specified section such as its name, code, active status, sort order, and description.

Typical use cases include:

• Renaming or re-coding sections in a CRM entity to reflect organizational changes.
• Activating or deactivating sections without deleting them.
• Adjusting the display order of sections for better UI arrangement.
• Updating descriptive information to clarify the purpose of a section.

For example, a user might automate updating a customer segment section's name and description after a marketing campaign restructure.

Properties

Output

The node outputs an array of items where each item contains a json object representing the result of the update operation on the entity section. The exact structure depends on the Bitrix24 API response but typically includes confirmation of the updated fields or error details if the update failed.

If the node encounters an error and is configured to continue on failure, it outputs an item with an error field describing the issue, along with the resource name and a timestamp.

No binary data output is involved in this operation.

Dependencies

• Requires valid authentication credentials for Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
• The node relies on Bitrix24's REST API endpoints to perform the update operation.
• Proper configuration of credentials in n8n is necessary to authorize API calls.

Troubleshooting

• Common Issues:

  • Invalid or expired authentication tokens can cause authorization failures.
  • Incorrect Section ID will result in errors indicating the section was not found.
  • Insufficient permissions in Bitrix24 may prevent updates.
  • Network connectivity issues can cause request timeouts or failures.

• Error Messages:

  • Errors returned from Bitrix24 API are passed through; typical messages include "Section not found", "Access denied", or "Invalid parameters".
  • If the node is set to continue on fail, errors are included in the output JSON under the error property.

• Resolutions:

  • Verify that the authentication credentials are correct and have not expired.
  • Confirm the Section ID exists and is accessible by the authenticated user.
  • Check Bitrix24 user permissions for modifying entity sections.
  • Ensure stable network connection and Bitrix24 service availability.

Links and References

• Bitrix24 REST API Documentation
• Bitrix24 CRM Entity Sections
• n8n Documentation on Credentials