Carry out controlled tasks.
Botster can use approved tools for defined tasks – process documents, produce records, trigger maintenance flows, schedule recurring work. Roles and risk classes determine what runs automatically and when a person has to approve.
The autonomy ladder
The higher the risk, the stronger the approval – configured per tenant and role.
What runs under control today
Bexio & mail
Create and issue quotes and invoices in Bexio – sending and financial actions require approval; mail drafts are only sent after approval.
Curated playbooks
Curated Ansible playbooks (health check, disk cleanup, service restart, update check) – bound to roles, with mandatory confirmation and limited to the curated catalogue.
Briefings & checks
Briefings, nightly checks and reminders set up through chat – as a cron job, an interval or a one-off.
Multi-step flows
Start multi-step flows from templates, work through them step by step, pause them, track their status.
Limits, clearly stated
Botster only executes what is registered as an approved tool or a reviewed flow – creative workarounds are ruled out by design.
The catalogues are deliberately curated (four base playbooks for maintenance, for example); extensions are built per customer and take the same route: define, review, authorise.
Mandatory approval for risky actions is by design, not a stopgap.
Common questions about controlled automation
Can Botster act on its own?+
Botster can carry out permitted tasks within configured limits. Depending on the tool, the risk and the autonomy level, a function stays blocked, is only proposed, needs human approval before execution, or may run automatically as a low-risk routine. That produces controlled autonomy rather than an agent with blanket access to company systems.
What happens if a flow goes wrong?+
Every step is logged: the request, the preview, the approval decision, the tool calls and the result are in the exportable audit trail. Risky actions only run after human confirmation; blocked tools stay blocked, however the request is phrased. That keeps even the failure case traceable and bounded.
See a controlled flow on your own case?
We walk through the flow on your use case – the “carry out a task” case is preselected in the form.