Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions89

Overview

The Bitrix24 node allows users to interact with the Bitrix24 CRM and business platform. Specifically, for the Activity resource with the Get All operation, this node fetches a list of activities from Bitrix24 according to specified criteria such as filters, selected fields, sorting order, and pagination.

This node is beneficial in scenarios where you want to retrieve multiple activity records for reporting, synchronization, or automation purposes. For example, you might use it to pull all recent calls, meetings, or tasks logged in Bitrix24 to analyze team performance or trigger follow-up workflows.

Properties

Name Meaning
Authentication Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook URL (simpler but less secure), or API Key authentication.
Options Collection of optional parameters to customize the query:
- Filter JSON object specifying filter criteria to narrow down which activities to retrieve.
- Select JSON array listing specific fields to include in the response for each activity.
- Order JSON object defining the sort order of the returned activities.
- Start Number indicating the offset record number to start fetching from (for pagination).
- Access Token String token used for authentication if applicable (e.g., OAuth2 access token).

Output

The node outputs an array of JSON objects representing the retrieved activities. Each object contains the fields requested via the Select property or defaults provided by the Bitrix24 API. The structure corresponds to Bitrix24's activity entity schema, including identifiers, timestamps, user references, and other activity-specific data.

If binary data were involved (not indicated here), it would be summarized accordingly, but this operation deals solely with JSON data.

Dependencies

  • Requires valid authentication credentials for Bitrix24, configured in n8n:
    • OAuth2 credentials (recommended for production)
    • Or a webhook URL
    • Or an API key credential
  • The node internally uses Bitrix24 API endpoints to fetch data.
  • No additional external dependencies beyond standard HTTP requests to Bitrix24.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication tokens can cause authorization failures.
    • Incorrectly formatted JSON in Filter, Select, or Order options may lead to API errors.
    • Pagination issues if Start is set beyond available records.

  • Error Messages:

    • Errors returned from Bitrix24 API will be surfaced, often indicating invalid parameters or authentication problems.
    • If the node is set to continue on failure, error details are included in the output JSON under an error field with a timestamp.

  • Resolutions:

    • Verify and refresh authentication credentials.
    • Validate JSON syntax in filter/select/order inputs.
    • Adjust pagination parameters within valid ranges.

Links and References

This summary is based on static analysis of the node's source code and provided input properties, focusing on the Activity resource's Get All operation.

Discussion