What I built
- A dashboard with active robots, robots in error and hours saved, with an automatic return calculation.
- Manual or scheduled triggering of each automation, with history and logs.
- A purpose-built SDK to standardize how each automation talks to the platform.
Under the hood
Each robot with its own key
When a robot is registered it receives an exclusive token, shown only once. The database stores only the hash, and the token is valid only for that robot.
Who can do what, by department
Each user only sees and triggers the robots of their own department. A robot that is inactive, or already running, cannot be triggered again.
Return measured for real
The estimated manual time goes into each robot’s record. On every run, the dashboard calculates the hours saved compared with the manual process.
Reports that arrive on their own
Parameterized reports with scheduling and e-mail delivery through an authenticated link, instead of one-off requests to IT.
The result
- A single view of what each automation does, where it fails and how much it saves.
- More than 80% of the routines IT used to run by hand in the database are now done by the business areas themselves.
- New automations registered through the database, with no code change.