Bitrix24Install

Overview

This node integrates with the Bitrix24 platform, specifically allowing users to interact with various Bitrix24 resources such as CRM entities and business platform features. The "Activity" resource with the "Get All" operation enables retrieving multiple activity records from Bitrix24.

Typical use cases include:

• Fetching a list of activities (calls, meetings, tasks, etc.) related to CRM entities for reporting or automation.
• Synchronizing Bitrix24 activities with other systems.
• Filtering and sorting activities based on custom criteria.

For example, a user might retrieve all activities created after a certain date or only those assigned to a specific user, then process or analyze them further in an n8n workflow.

Properties

Output

The node outputs an array of items where each item contains a json property representing an individual activity record retrieved from Bitrix24. The structure of each activity object depends on the selected fields and filters but generally includes standard activity properties such as IDs, timestamps, user assignments, and custom fields.

No binary data output is indicated by the source code.

Example output snippet (conceptual):

[
  {
    "json": {
      "ID": "123",
      "SUBJECT": "Call with client",
      "DATE_CREATE": "2024-01-01T12:00:00Z",
      "ASSIGNED_BY_ID": "45",
      ...
    }
  },
  ...
]

Dependencies

• Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
• Needs appropriate credentials configured in n8n for the chosen authentication method.
• Relies on Bitrix24 API endpoints to fetch activity data.
• No additional external libraries beyond those bundled with the node are required.

Troubleshooting

• Authentication errors: Ensure that the correct authentication method is selected and credentials are valid. For OAuth2, verify token validity and refresh if expired.
• Invalid filter/select/order JSON: The node expects valid JSON strings for these options. Malformed JSON will cause errors. Use JSON validators before input.
• API rate limits or connectivity issues: Bitrix24 may throttle requests or be temporarily unavailable. Retry later or check network connectivity.
• Empty results: Confirm that filter criteria match existing activities; otherwise, no data will be returned.
• Error messages: If the node throws errors during execution, they typically include the Bitrix24 API error message. Review the message for clues (e.g., permission denied, invalid parameters).

Links and References

• Bitrix24 REST API Documentation
• Bitrix24 Activities API Reference
• n8n Documentation on Creating Nodes