Stage history as a list
The "Stage history as a list" robot returns, inside a Bitrix24 (Alaio) workflow, the full path a deal, lead or smart process item took through the stages: arrays of codes, names and entry dates, plus a ready-made line for a comment.
The robot returns the whole stage history inside the Bitrix24 (Alaio) workflow itself, reading it at run time. Three strictly parallel arrays come back — stage codes, stage names and entry dates: the i-th element of each array describes the same transition, so the lists can be fed into array robots and assembled into any report. A ready-made line such as "New — 01.09.2026 10:00; Invoice sent — 03.09.2026 11:00" is returned separately, to be pasted straight into a deal comment or an email to the manager, along with the number of transitions. The order is chronological, from the first stage to the last. Dates come in the portal timezone, so they match what the card shows. Deals, leads and smart process items are supported; by default the robot uses the item the workflow runs on. Moving between funnels counts as an ordinary transition.
What input parameters does the robot accept?
| Parameter | Type | Required? | Default |
|---|---|---|---|
| Item | select | — | auto |
| Item ID (for the "by ID" modes) | string | — | |
| Smart process type ID (for the smart process mode only) | string | — |
What does the robot return?
| Parameter | Type |
|---|---|
| Stage codes (array) | string |
| Stage names (array) | string |
| Entry dates (array) | string |
| History as one line | string |
| Number of transitions | int |
| History is not empty (Y/N) | bool |
| Success | bool |
What errors can the robot return?
The robot writes these messages to the business process log when it cannot complete a step. The text tells you what to fix in the settings or the data.
- This item type has no stages. The robot works with deals, leads and smart processes; for the "by ID" modes provide a valid ID.
- API error while reading the stage history.
Scenario: the deal's path posted as a comment on close
- The deal moves to a won stage
- The robot retrieves the stage history as one line
- The line is posted to the timeline, and the whole team sees the path the deal took and how many transitions it had