Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Overview

This node integrates with the Bitrix24 platform to add a new Smart Process Automation (SPA) type. It allows users to define custom SPA types within Bitrix24, configuring various features and fields that tailor the SPA to specific business needs. This is useful for organizations that want to automate and customize their workflows beyond standard CRM entities by creating specialized process types.

Typical use cases include:

  • Creating a new SPA type to track custom business processes.
  • Enabling or disabling specific SPA features such as client binding, document printing, automation rules, and more.
  • Defining relations to other CRM entities and customizing user field visibility.

For example, a company might create an SPA type called "Project Management" with enabled automation rules and linked products to streamline project tracking and invoicing.

Properties

Name Meaning
Authentication Method of authenticating API requests: OAuth2, Webhook URL, or API Key.
Type Name (title) The name of the Smart Process type to be created.
Enable Client Field Whether to enable a Client field that binds to Contacts and Companies.
Enable Document Printing Whether to enable the ability to print documents related to this SPA type.
Enable Use in User Field Whether to allow this SPA type to be used in user-defined fields.
Enable Product Binding Whether to enable linking catalog products to this SPA type.
Enable Company Details Field Whether to enable a field showing details of "Your Company".
Enable Observers Field Whether to enable an Observers field for this SPA type.
Enable Recycle Bin Whether to enable recycle bin functionality for deleted SPA elements.
Enable Automation Rules & Triggers Whether to enable automation rules and triggers for this SPA type.
Enable Start Date & End Date Fields Whether to enable Start Date and End Date fields for this SPA type.
Enable Business Process Designer Whether to enable integration with the business process designer tool.
Enable Custom Sales Funnels Whether to enable custom sales funnels and tunnels for this SPA type.
Enable Source Field Whether to enable a Source field to track origin information.
Enable Set Open Permissions for New Elements Whether new SPA elements should have open permissions set by default.
Enable Payment Stage Field Whether to enable a Payment Stage field for this SPA type.
Enable REST API Whether to enable external access to this SPA type via REST API.
Options A collection of additional optional settings:
- Access Token An explicit access token to use for API requests instead of credentials.
- Entity Type ID Numeric identifier for the SPA type (must be ≥ 1030 or between 128-192).
- Entity Type Code Code identifier for the entity type (lowercase, no spaces).
- Description Text description of the SPA type.
- Relations JSON object defining links to other CRM entities, specifying parent/child relationships.
- Linked User Fields JSON object specifying user fields where this SPA should be displayed if enabled.

Output

The node outputs an array of items representing the result of the SPA type creation operation. Each item contains a json property with the response data from Bitrix24's API about the newly created SPA type or error information if the operation failed.

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

No binary data output is produced by this node.

Dependencies

  • Requires valid authentication to Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
  • Uses Bitrix24 REST API endpoints to perform operations.
  • No additional external services are required.
  • Proper configuration of credentials in n8n is necessary for successful API calls.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication tokens can cause authorization failures.
    • Providing an invalid or out-of-range Entity Type ID may result in API errors.
    • Malformed JSON in the Relations or Linked User Fields properties can cause request failures.
    • Insufficient permissions in Bitrix24 account to create or modify SPA types.
  • Error Messages:

    • Errors returned from Bitrix24 API will be included in the output JSON under an error field.
    • If the node fails and is not set to continue on fail, it will throw an error stopping workflow execution.
    • To resolve, verify credentials, check input property values, and ensure correct JSON formatting.

Links and References

Discussion