Previous stage
The "Previous stage" robot returns, inside a workflow, the stage a deal, lead or smart process item came from: the code for conditions, the name for text, plus the funnel, the moment it left that stage and how long it stayed there.
The robot returns the previous stage inside the workflow itself — no custom fields, no waiting: the history is read at run time in a single request. Deals, leads and smart process items are supported; by default the robot uses the item the workflow runs on, so the common case needs no configuration, while the "by ID" modes cover workflows running on a different item. It returns the stage code (for conditions), the stage name (for an email or a comment), the P/S/F semantics, the funnel ID, the moment the item left the stage, and the time spent there in seconds. A separate "found" flag tells "the item has never moved" apart from a real error, so the happy path does not need error handling. Moving an item between funnels counts as a stage change.
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 |
|---|---|
| Previous stage code | string |
| Previous stage name | string |
| Stage semantics: P — in progress, S — success, F — failure | string |
| Funnel ID of the previous stage | string |
| When the item left the previous stage | string |
| Time spent in the previous stage, seconds | int |
| Previous stage found (Y/N) | bool |
| Success | bool |
Scenario: a deal slipping back down the funnel
- The robot runs on the Negotiation stage
- If the previous stage is Invoice sent, the deal has moved backwards
- A task is created for the manager, and the comment records how long the deal sat in the previous stage