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 smart process items within Bitrix24. Users can input data either as JSON or form fields, apply filters when listing or retrieving items, and select specific fields to return. This node is useful for automating CRM workflows, managing custom business processes, and integrating Bitrix24 smart process data with other systems.

Use Case Examples

  1. Create a new smart process item by providing field values in JSON format.
  2. Update an existing smart process item using form input fields.
  3. Retrieve a smart process item by its ID or by applying filters.
  4. List all smart process items with optional filtering and field selection, with support for pagination and limits.

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 object containing field values for create or update operations when inputFormat is set to JSON.
fields A collection of fields with their names, value types, and values for create or update operations when inputFormat is set to form.

Output

JSON

  • id - The unique identifier of the created, updated, retrieved, or deleted smart process item.
  • success - Indicates successful deletion of a smart process item.
  • error - Error message returned when an operation fails or a record is not found.
  • fields - The fields of the smart process item returned from create, update, get, or list operations.

Dependencies

  • Bitrix24 API with appropriate API key or OAuth credentials

Troubleshooting

  • Ensure the entityTypeId parameter is set correctly for smart process operations, as it is required.
  • When using JSON input format, ensure the JSON is valid and correctly structured to match Bitrix24 field requirements.
  • If a record is not found during get or list operations, the node returns an error message indicating the record was not found.
  • API rate limits or network issues may cause request failures; handle errors and consider retry logic or delays between requests.

Links

Discussion