Roboteka
Roboteka · Robots · Complete activities

Complete activities

The Complete activities robot closes every open activity of an item in a Bitrix24 (Alaio) workflow: calls, meetings and to-dos of the current lead, deal, contact or company, or of any item by ID. Activity kinds are picked with checkboxes; an overdue-only mode is available.

The robot completes the open activities of an item in one action right inside a Bitrix24 (Alaio) workflow or automation rule. The stock "Change document" robot cannot reach activities, so when a deal moves to a final stage or a manager leaves, overdue calls and meetings keep sitting in the counters. The robot reads the item activity list and closes the kinds ticked in its settings: to-dos, calls and meetings are on by default, e-mails, tasks and other kinds are opt-in because completing a task activity closes the task itself. The "Overdue only" flag leaves activities whose deadline has not come yet untouched. By default the item the process runs on is used; any lead, deal, contact or company can be given by ID. The robot returns the number of completed, skipped and failed activities.

What input parameters does the robot accept?

Parameter Type Required? Default
Item select Current item, Lead by ID, Deal by ID, Contact by ID, Company by ID — current
Item ID (for the "by ID" modes) string —
Complete to-dos bool — Y
Complete calls bool — Y
Complete meetings bool — Y
Complete e-mails bool — N
Complete tasks (closes the task itself too) bool — N
Complete other activity kinds bool — N
Overdue only bool — N

What does the robot return?

Parameter Type
Activities completed int
Activities skipped (kind not selected) int
Failed to complete int
Success bool
Error string

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.

  • Could not resolve the item. In a "by ID" mode enter a valid ID; the current item must be a lead, deal, contact, company or smart process element.
  • API error while reading the item activities.

Scenario: a closed deal must not keep open activities

  1. The robot is placed on the final stage of the pipeline
  2. When the deal enters the stage it completes all its open calls, meetings and to-dos
  3. The manager's activity counter clears and the completed count goes into a timeline comment

Related robots