Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

Overview

This node integrates with the Bitrix24 platform, specifically allowing users to delete a User Field within Bitrix24. It supports multiple authentication methods (OAuth2, webhook URL, or API key) to connect securely to the Bitrix24 API.

Typical use cases include automating the management of custom user fields in Bitrix24 CRM or business processes, such as cleaning up obsolete fields or dynamically adjusting field configurations based on workflow needs.

For example, a marketing automation workflow might remove outdated custom user fields after a campaign ends, ensuring the CRM stays clean and relevant.

Properties

Name Meaning
Authentication Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook, API Key.
Options Additional options for the operation.
- Access Token The access token string used for authentication when applicable (e.g., OAuth2).

Output

The node outputs an array of items where each item contains a json object representing the result of the delete operation. If the operation fails and "Continue On Fail" is enabled, the output will contain an error message with details:

  • error: The error message returned from the failure.
  • resource: The resource name involved ("userField").
  • timestamp: ISO timestamp of when the error occurred.

No binary data output is indicated by the source code.

Dependencies

  • Requires connection to Bitrix24 API via one of the supported authentication methods.
  • Needs proper configuration of credentials in n8n for OAuth2, webhook URL, or API key.
  • Relies on internal helper functions to make standard Bitrix24 API calls.

Troubleshooting

  • Common Issues:

    • Authentication failures due to invalid or expired tokens.
    • Insufficient permissions to delete user fields in Bitrix24.
    • Network connectivity issues preventing API calls.
    • Incorrect resource or operation parameters.
  • Error Messages:

    • Errors thrown during execution will be included in the output if "Continue On Fail" is enabled.
    • Typical error messages may relate to authorization errors, missing fields, or API call failures.
  • Resolutions:

    • Verify that the authentication credentials are valid and have necessary scopes/permissions.
    • Ensure the user field ID or parameters are correct and exist in Bitrix24.
    • Check network connectivity and Bitrix24 service status.
    • Enable "Continue On Fail" to capture error details for debugging.

Links and References

Discussion