July¶
In July 2026, BotCity Orchestrator launches the Integration Hub: a native webhook with 15 operational events distributed across four categories (Task, Runner, Alert, and Datapool), removing the need for API polling or helper automations to integrate with Slack, Teams, Datadog, Power BI, and other tools.
Insights now accepts seconds in the processing time per item field, along with readability improvements to the numbers and calculations shown on screen.
The platform's main listing pages: Datapool, Alerts, Schedules, Automations, Execution Log, Result Files, Runners, Robots, and Credentials now display summary cards at the top, with operation totals visible as soon as the screen opens.
Native webhook¶
The Integration Hub arrives at BotCity Orchestrator with its first delivery: a native webhook that fires automatically to the endpoint you configure whenever an operational event occurs on the platform.
This unlocks integration with tools like Slack, Teams, Datadog, Power BI, Google Chat, and any other system that can receive events via HTTP, without needing to maintain constant polling on the Orchestrator API or build a helper bot just to watch automation status.
Events¶
You can select which events each webhook should listen to, across the four categories below:
Task
| Event |
|---|
| Task started execution |
| Task finished successfully |
| Task failed |
| Task partially finished |
| Task timed out |
| Task cancelled |
Runner
| Event |
|---|
| Runner went offline |
| Runner came online |
Alert
| Event |
|---|
| Error alert issued |
| Warning alert issued |
Datapool
| Event |
|---|
Item finished with SYSTEM error |
Item finished with BUSINESS error |
| Item timed out |
| Item finished successfully |
| Datapool with high error volume |
Configuration¶
Go to Integration Hub > Webhooks in the side menu, create a new webhook providing name, endpoint URL, and the desired events, and track each delivery in the Deliveries table.
For the full step-by-step, signature security, permissions, and limits, see the Webhooks documentation.
Insights¶
Processing time in seconds¶
The processing time per item field, which previously only accepted minutes (with a minimum of 1 minute), now also accepts values in seconds, shown in an additional field next to the existing minutes field. This allows the actual time of fast automations to be correctly recorded, such as sending a Teams message, which can take only 5 to 10 seconds.
Hours Saved, FTE, and ROI calculations are automatically adjusted to reflect the new unit.
Historical data
Automations already registered in minutes are automatically migrated to seconds in the backend (for example, 35 min becomes 2,100 sec). Previous calculation history is not recalculated — only new data from the update onward uses the new logic.
Readability of numbers and calculations¶
Numbers shown in Insights become easier to read and interpret:
- Hours displayed without decimal places — just the integer value (e.g.,
3,413 hinstead of3,413.33 h). - Thousands separator applied to all numeric values, respecting the configured language.
- Information icon next to each field, with a tooltip showing the calculation formula.
- Documentation link repositioned to the start of the component, more visible.
Visual summaries¶
The platform's main listing pages now display summary cards at the top, showing the relevant totals as soon as the screen opens, without needing to scroll the table or apply filters.
| Page | Cards |
|---|---|
| Datapool | Total, Active, Inactive |
| Alerts | Total, Error, Info, Warning |
| Schedules | Total, Active, Inactive |
| Automations | Total, Complete, Incomplete |
| Execution Log, Result Files, Robots, Credentials | Total |
| Runners | Total, Online, Offline |
Cards respond to the filters applied on the page: when filtering by a specific status (for example, only error alerts), only the corresponding card is shown.