Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Overview

The node integrates with the Bitrix24 platform, specifically supporting operations related to Smart Process Automation (SPA) settings. The "Get SPA Settings" operation allows users to retrieve configuration details about SPA types within their Bitrix24 environment. This is useful for automating workflows and managing custom business processes defined in Bitrix24.

Typical use cases include:

  • Fetching SPA type metadata to dynamically build forms or interfaces.
  • Retrieving SPA field definitions to map data between systems.
  • Automating process management by accessing SPA configurations programmatically.

For example, a user might use this node to get all SPA types available in their Bitrix24 account and then trigger further automation based on those types.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key

Output

The node outputs JSON data representing the result of the requested SPA settings operation. The structure depends on the specific SPA-related API call made internally but generally includes:

  • Lists of SPA types with their IDs and titles.
  • Field definitions for SPA entities, including field names, types, and attributes like required or read-only status.
  • Metadata such as categories or placement options related to SPA.

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

The node does not output binary data.

Dependencies

  • Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
  • Uses Bitrix24 REST API endpoints such as crm.type.list, crm.item.fields, and others to fetch SPA-related data.
  • Needs proper API credentials configured in n8n for authentication.

Troubleshooting

  • Common issues:

    • Authentication failures due to incorrect or expired credentials.
    • API rate limits or permission restrictions from Bitrix24.
    • Missing or invalid SPA type IDs when fetching fields.
  • Error messages:

    • Errors returned from Bitrix24 API calls are surfaced in the output's error field.
    • If the node fails to load SPA types or fields, it returns descriptive error messages indicating the failure reason.
  • Resolutions:

    • Verify that the selected authentication method is correctly configured and has sufficient permissions.
    • Ensure the SPA type ID parameter is provided when required.
    • Check Bitrix24 API limits and adjust usage accordingly.

Links and References

Discussion