Bitrix24

Overview

The node integrates with the Bitrix24 CRM and business platform, enabling users to interact with various Bitrix24 resources. Specifically, for the Document Generator resource with the Get Providers operation, it fetches available document provider information from Bitrix24.

This node is useful in scenarios where automation workflows need to retrieve or manipulate CRM data, generate documents, or access Bitrix24 services programmatically. For example, a user might want to automatically pull document templates or providers before generating contracts or reports within an automated workflow.

Properties

Output

The node outputs JSON data representing the result of the requested operation on the selected resource. For the Get Providers operation under the Document Generator resource, the output JSON will contain details about the available document providers retrieved from Bitrix24.

If errors occur during execution, the output JSON will include an error field with the error message, along with the resource name and a timestamp.

The node does not explicitly output binary data.

Dependencies

• Requires connection to Bitrix24 via one of the supported authentication methods:

  • OAuth2 authentication (recommended)
  • Webhook URL
  • API Key authentication

• The node depends on Bitrix24's API endpoints to fetch data.

• No additional external libraries beyond those bundled are required.

• Proper credentials must be configured in n8n for the chosen authentication method.

Troubleshooting

• Common Issues:

  • Authentication failures due to incorrect or expired credentials.
  • API rate limits or permission issues on the Bitrix24 side.
  • Network connectivity problems preventing API calls.

• Error Messages:

  • Errors returned by Bitrix24 API calls will be surfaced in the node output under the error field.
  • If the node fails to process the request and "Continue On Fail" is disabled, the workflow will stop with the error.
  • If "Continue On Fail" is enabled, the node returns an error object in the output JSON instead of throwing.

• Resolutions:

  • Verify that the correct authentication method and valid credentials are used.
  • Check Bitrix24 API permissions and ensure the user has access to the requested resource.
  • Enable "Continue On Fail" to handle errors gracefully in workflows.

Links and References

• Bitrix24 Official API Documentation
• n8n Documentation on Credentials
• OAuth2 Authentication Overview