Bitrix24Install

Overview

This node integrates with the Bitrix24 platform, specifically allowing users to save notes on the Timeline resource. It supports multiple authentication methods including OAuth2, webhook URLs, and API keys, making it flexible for different security and deployment scenarios.

Typical use cases include:

• Automatically adding notes or comments to a Bitrix24 timeline entry as part of a CRM workflow.
• Logging interactions or updates related to deals, contacts, or other CRM entities.
• Enhancing automation by programmatically saving structured note data in Bitrix24 timelines.

For example, a sales automation workflow could use this node to append meeting notes or call summaries directly into the Bitrix24 timeline associated with a lead or deal.

Properties

Output

The node outputs an array of items where each item contains a json field representing the response from Bitrix24 after attempting to save the note. The exact structure depends on the Bitrix24 API response but generally includes confirmation details about the saved note.

If an error occurs and the node is configured to continue on failure, the output will contain an item with an error message, the resource name, and a timestamp.

No binary data output is indicated.

Dependencies

• Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2 token, webhook URL, or API key).
• Relies on Bitrix24's REST API endpoints to perform operations.
• No additional external libraries beyond those bundled are required.
• Proper configuration of credentials within n8n is necessary for successful operation.

Troubleshooting

• Authentication errors: Ensure that the selected authentication method is correctly configured and the credentials are valid. OAuth2 tokens may expire and require refresh.
• Invalid Note Data: The noteData property must be valid JSON matching Bitrix24's expected format for timeline notes. Malformed JSON or missing required fields can cause API errors.
• API rate limits or connectivity issues: Network problems or Bitrix24 API rate limiting can cause failures. Retrying or checking network access may help.
• Error messages in output: If the node returns an error object in the output, inspect the error message for clues. Common messages relate to permission issues, invalid parameters, or authentication failures.
• Continue On Fail behavior: When enabled, errors do not stop the workflow but are returned as part of the output for handling downstream.

Links and References

• Bitrix24 REST API Documentation
• Bitrix24 Timeline API Reference
• n8n Documentation on Credentials