Actions30
- 袥懈写 Actions
- 小写械谢泻邪 Actions
- 袣芯薪褌邪泻褌 Actions
- 袣芯屑锌邪薪懈褟 Actions
- 孝芯胁邪褉 Actions
- 小屑邪褉褌-锌褉芯褑械褋褋 Actions
小屑邪褉褌-锌褉芯褑械褋褋 → 小锌懈褋芯泻
AI-generatedOverview
This node interacts with the Bitrix24 API specifically for the Smart Process resource, allowing users to perform CRUD operations such as creating, retrieving, listing, updating, and deleting smart process records. It supports filtering, selecting specific fields, and handling pagination for listing records. This node is useful for automating workflows involving custom smart processes in Bitrix24, such as managing custom business data or automating data entry and retrieval.
Use Case Examples
- Create a new smart process record with specified fields in Bitrix24.
- Retrieve a specific smart process record by ID or by applying filters.
- List all smart process records with optional filters and field selection, supporting pagination or limiting results.
- Update an existing smart process record by ID with new field values provided in JSON or form format.
Properties
| Name | Meaning |
|---|---|
| entityTypeId | The ID of the smart process type to operate on, required for all operations on the smart process resource. |
| returnAll | Whether to return all records when listing smart process items, or limit the number of results. |
| limit | The maximum number of records to return when listing smart process items, used if returnAll is false. |
| useFilter | Whether to apply filters when listing smart process items. |
| filterFields | A collection of filter conditions to apply when listing or retrieving smart process items by filter. Each filter includes a field name, an operation (e.g., equals, not equals, greater than), and a value to filter by. |
| selectFields | Fields to select and return in the response when retrieving or listing smart process items. |
Output
JSON
id- The unique identifier of the smart process record.fields- The fields and their values of the smart process record.success- Indicates successful deletion of a smart process record.error- Error message if the requested record is not found or an operation fails.
Dependencies
- Bitrix24 API authentication token or API key credential
Troubleshooting
- Common issues include invalid entityTypeId or missing required fields causing API errors.
- Errors like 'Запись не найдена' (Record not found) occur when the specified ID does not exist.
- Ensure correct filter syntax and valid field names when using filters to avoid empty results or errors.
- API rate limits or network issues may cause request failures; retry or check credentials if errors persist.
Links
- Bitrix24 Smart Process API Documentation - Official Bitrix24 documentation for Smart Process API endpoints and usage.