Bitrix24 icon

Bitrix24

Работа с Bitrix24 API

Actions25

Overview

This node integrates with the Bitrix24 CRM system to manage "Deal" records. Specifically, the Create operation allows users to create new Deal entries by specifying custom fields and their values. This is useful in automating sales pipelines, where new deals need to be added programmatically based on external triggers or workflows.

Typical use cases include:

  • Automatically creating a deal when a new lead is qualified.
  • Adding deals from external e-commerce platforms or marketing tools.
  • Populating deals with dynamic data collected from forms or other systems.

Properties

Name Meaning
Fields A collection of fields to set on the new Deal record. Each field consists of:
- Field Name: The name of the Deal field to set (loaded dynamically from Bitrix24).
- Field Value: The value to assign to that field.

The "Fields" property supports multiple entries, allowing you to specify many fields for the new Deal.

Output

The node outputs an array of JSON objects representing the responses from Bitrix24 API for each created Deal. Each object typically contains information about the newly created Deal, such as its ID and any additional metadata returned by Bitrix24.

No binary data output is produced by this operation.

Example output structure (simplified):

[
  {
    "result": {
      "ID": "12345"
    }
  }
]

Dependencies

  • Requires an active Bitrix24 account with API access enabled.
  • Needs an API authentication token or webhook URL configured in the node credentials.
  • The node uses the Bitrix24 REST API endpoints via HTTP POST requests to perform operations.
  • The webhook URL must be correctly set and accessible for the node to communicate with Bitrix24.

Troubleshooting

  • Missing Credentials: If no credentials or webhook URL are provided, the node will throw errors indicating these are required.
  • Invalid Field Names: Specifying incorrect or unsupported field names may cause API errors. Use the dynamic field loader to select valid fields.
  • API Errors: Network issues or permission problems can result in failed API calls. Check connectivity and API permissions.
  • Continue On Fail: If enabled, the node will continue processing remaining items even if some fail, returning error messages per item.

Common error messages:

  • "No credentials got returned!" — Ensure the API key or webhook URL credential is properly configured.
  • "Webhook URL is required!" — The webhook URL must be set in the credentials.
  • "Failed to execute node: <message>" — General failure; check the detailed message for specifics.

Links and References

Discussion