Retrieve an Array of Process Elements rpa.item.list

Choose a tool for developing with an AI agent:

  • use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
  • use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation

Scope: rpa

Who can execute the method: any user

DEPRECATED

The development of this method has been halted. Please use Smart Processes as an alternative to this functionality.

This method retrieves a list of process elements with the identifier typeId.

Method Parameters

Name
type

Description

typeId
integer

Identifier of the process

order
object

List for sorting, where the key is the field and the value is ASC or DESC

filter
object

List for filtering.

Keys for filtering by custom fields should be in UPPER_CASE, while others should be in camelCase. Examples of filters are provided below

start
integer

Offset for pagination.

Response Handling

HTTP Status: 200

The response will contain only the main fields of the elements, without data about tasks and users of the elements:

{
            "items": [
                {},
                {}
            ]
        }

Filter Examples

  1. Find elements that have uncompleted tasks for the current user

    {
            "filter": {
                "tasks": "has_tasks"
            }
        }

    To find elements that do not have tasks assigned to the user, pass the value no_tasks.

  2. Find elements updated by the user with the identifier 4

    {
            "filter": {
                "=updatedBy": "4"
            }
        }

  3. Find elements updated or moved by the user with the identifier 4

    {
            "filter": {
                "logic": "or",
                "0": {
                    "=updatedBy": "4"
                },
                "1": {
                    "=movedBy": "4"
                }
            }
        }

  4. Find elements where the custom field with the code UF_RPA_1_STRING is filled

    {
            "filter": {
                "!=UF_RPA_1_STRING": ""
            }
        }

  5. Find elements that were created, modified, and moved between March 19 and March 22

    {
            "filter": {
                ">createdTime":"2020-03-19T02:00:00+02:00",
                ">movedTime":"2020-03-19T02:00:00+02:00",
                ">updatedTime":"2020-03-19T02:00:00+02:00",
                "<createdTime":"2020-03-22T02:00:00+02:00",
                "<movedTime":"2020-03-22T02:00:00+02:00",
                "<updatedTime":"2020-03-22T02:00:00+02:00"
            }
        }

  6. Find elements that were either created, modified, or moved between March 19 and March 22

    {
            "filter": {
                "logic":"OR",
                "0":{
                    ">createdTime":"2020-03-19T02:00:00+02:00",
                    "<createdTime":"2020-03-22T02:00:00+02:00"
                },
                "1":{
                    ">movedTime":"2020-03-19T02:00:00+02:00",
                    "<movedTime":"2020-03-22T02:00:00+02:00"
                },
                "2":{
                    ">updatedTime":"2020-03-19T02:00:00+02:00",
                    "<updatedTime":"2020-03-22T02:00:00+02:00"
                }
            }
        }

Continue Learning

Previous
Retrieve information about the element
Next
Get data on current tasks of the element