Typical system categories
A digital employee works where work starts and where results are documented today.
- Microsoft 365 or Google Workspace
- email, calendars and files
- CRM, ERP, DMS and ticket systems
- REST APIs, databases, n8n and custom interfaces
Plan read and write separately
Not every connected system needs write access. Many first roles start read-only or prepare drafts for human review.
- read-only research
- draft instead of direct sending
- write access only for defined fields
- logging for changes
Failure cases are part of the design
If data is missing, an API is unavailable or rules conflict, the employee must stop cleanly and hand over.
- timeouts
- incomplete master data
- missing permissions
- escalation to defined contacts