Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node interacts with the Bitrix24 platform, specifically allowing users to update configurations of user fields within Bitrix24. The "User Field Config" resource's "Update" operation enables modifying properties of a specific user field configuration by its ID. This is useful for automating updates to custom fields in Bitrix24 CRM or business processes, such as changing labels, visibility, mandatory status, or other settings programmatically.

Practical examples include:

  • Automatically updating form labels or filter options for user fields based on external data changes.
  • Enabling or disabling certain fields dynamically depending on workflow conditions.
  • Adjusting sorting or searchability of fields without manual intervention in the Bitrix24 UI.

Properties

Name Meaning
Authentication Method of authenticating API requests: OAuth2 (recommended), Webhook URL (simpler but less secure), or API Key authentication.
ID The unique identifier of the user field configuration to update.
Update Fields Collection of fields to update, each specifying:
- Field Name The name/key of the field property to update.
- Value The new value to assign to the field.
- Is Boolean Whether the field value is boolean type.
- Boolean Value The boolean value to set if the field is boolean.
Options Additional options collection, including:
- Access Token An access token string used for authentication (optional override).

Output

The node outputs an array of items where each item contains a json object representing the response from Bitrix24 after processing the update request. If an error occurs and the node is configured to continue on failure, the output will contain an error message along with the resource name and a timestamp.

The output JSON structure typically includes the updated user field configuration details returned by Bitrix24, reflecting the changes made.

No binary data output is indicated in the source code.

Dependencies

  • Requires valid authentication credentials for Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
  • Uses Bitrix24 API endpoints internally through a generic call function.
  • No additional external services beyond Bitrix24 are required.
  • Proper configuration of credentials in n8n is necessary for successful API communication.

Troubleshooting

  • Common issues:
    • Invalid or expired authentication tokens leading to authorization errors.
    • Incorrect or missing user field configuration ID causing "not found" errors.
    • Attempting to update fields with invalid names or unsupported values.
  • Error messages:
    • Errors thrown by the Bitrix24 API will be surfaced in the node output if "Continue On Fail" is enabled.
    • Typical error messages may include authentication failures, permission denied, or invalid parameter errors.
  • Resolutions:
    • Verify that the authentication method and credentials are correctly set up and valid.
    • Confirm the user field configuration ID exists and is correct.
    • Ensure field names and values conform to Bitrix24 API specifications.

Links and References

Discussion