Bitrix24 icon

Bitrix24

袪邪斜芯褌邪 褋 Bitrix24 API

Actions30

袥懈写 → 小芯蟹写邪褌褜

AI-generated

Overview

This node interacts with the Bitrix24 API to perform operations on the 'Smart Process' resource. It supports creating, updating, retrieving, listing, and deleting records within a specified smart process entity type. Users can input data either as form fields or JSON, apply filters when listing or retrieving records, and select specific fields to return. This node is useful for automating CRM workflows, managing custom data entities, and integrating Bitrix24 smart processes with other systems.

Use Case Examples

  1. Create a new record in a Bitrix24 smart process by specifying the entity type and fields in JSON format.
  2. Update an existing smart process record by ID with form data input.
  3. Retrieve a single smart process record by ID or by applying filters to find matching records.
  4. List all records in a smart process with optional filtering and field selection, supporting pagination or limiting results for efficient data handling.

Properties

Name Meaning
inputFormat Specifies the format of the input data for create or update operations, either as form fields or JSON.
fieldsJson The JSON string representing the fields and their values when inputFormat is set to JSON.
fields A collection of fields and their values when inputFormat is set to form, allowing multiple fields to be specified with their names and values.

Output

JSON

  • id - The unique identifier of the created, updated, or deleted smart process record.
  • success - Indicates successful deletion of a record (true if deletion succeeded).
  • error - Error message returned when a requested record is not found or an operation fails.
  • item - The smart process record data returned from create, update, or get operations.
  • items - An array of smart process records returned from list operations.

Dependencies

  • Bitrix24 API
  • API authentication token or API key credential

Troubleshooting

  • Ensure the entityTypeId parameter is correctly set for smart process operations, as it is required to identify the specific smart process type.
  • When using JSON input format, ensure the JSON string is valid and correctly formatted to avoid parsing errors.
  • If a record is not found during get or update operations, check the ID or filter criteria for accuracy.
  • API rate limits or network issues may cause request failures; implement retry logic or handle errors gracefully.
  • Use the 'continue on fail' option to allow processing of multiple items even if some fail, capturing errors in the output.

Links

Discussion