Stage entry date
The "Stage entry date" robot returns, inside a Bitrix24 (Alaio) workflow, the date a deal, lead or smart process item entered a given stage, along with how many times it entered it. The stage is given by code or by name, and you choose the first or the last entry.
The robot returns the date an item reached a given stage inside the Bitrix24 (Alaio) workflow itself, reading the history at run time. The stage can be given by code or by name, with the code taking priority, so renaming a stage in the funnel breaks nothing — unlike tools that key off the name alone. If the item came back to the stage more than once, you choose the first or the last entry, and the number of entries is returned separately, which shows how often the item slipped back down the funnel. Deals, leads and smart process items are supported; by default the robot uses the item the workflow runs on. A stage that does not exist on the portal is treated as a configuration error and reported explicitly, while a stage the item simply never reached is an ordinary "not found" answer. Funnels the item moved between are taken into account.
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 | — | |
| Stage — code or name | string | yes | |
| Which entry | select | — | last |
What does the robot return?
| Parameter | Type |
|---|---|
| Stage entry date | string |
| Stage code | string |
| Stage name | string |
| Number of entries into the stage | int |
| Stage entry found (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.
- Stage "{stage}" was not found on the portal. Provide the stage code or its exact name.
- 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: watching stalled deals
- A recurring workflow runs the robot on a deal
- It takes the date of the last entry into the Invoice sent stage
- If more than seven days have passed, a task is created for the manager, and the entry count shows how often the deal has already slipped back