Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node integrates with the Bitrix24 platform, allowing users to interact with various Bitrix24 resources such as CRM entities and business processes. Specifically, for the Lists resource and the Get Iblock Type ID operation, it retrieves the identifier of an information block type (Iblock Type ID) within Bitrix24.

Common scenarios where this node is beneficial include:

  • Automating workflows that require fetching metadata about lists or information blocks in Bitrix24.
  • Integrating Bitrix24 list data into other systems by first identifying the correct Iblock Type ID.
  • Dynamically querying or filtering Bitrix24 lists based on their type identifiers.

Practical example:

  • A user wants to synchronize a specific Bitrix24 list with an external database. They use this node to get the Iblock Type ID to ensure they are referencing the correct list type before performing further operations like fetching or updating list items.

Properties

Name Meaning
Authentication Method to authenticate with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key authentication.
Options Additional parameters to customize the request:
  Access Token Use a specific access token instead of the one from credentials.
  Filter JSON-formatted filter criteria to narrow down results.
  Order JSON-formatted sort order specification.
  Select Comma-separated list of fields to select from the response.

Output

The node outputs an array of items, each containing a json object with the data returned from Bitrix24 corresponding to the requested Iblock Type ID. The exact structure depends on the Bitrix24 API response but typically includes identifiers and metadata related to the information block type.

If an error occurs and "Continue On Fail" is enabled, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.

The node does not output binary data.

Dependencies

  • Requires valid authentication with Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
  • Uses Bitrix24 API endpoints internally to fetch data.
  • No additional external dependencies beyond standard n8n environment and Bitrix24 credentials.

Troubleshooting

  • Authentication errors: Ensure the selected authentication method is correctly configured with valid credentials or tokens.
  • API call failures: May occur due to incorrect filters, invalid access tokens, or network issues. Check the error message returned in the output for details.
  • Empty or missing results: Verify that the filter and select options are correctly specified and that the targeted Iblock Type exists in Bitrix24.
  • Rate limits or timeouts: Bitrix24 API may impose rate limits; consider adding delays or handling retries if necessary.

Links and References

Discussion