PROBLEM
The same checklist is replayed by hand, with a different result, no log and no owner when it fails at night.
PODEJŚCIE
Document the manual step, then a small readable script or webhook (PowerShell, bash, API, n8n) with input, output, log and rollback.
SCOPE
- inventory of repeats and failure points
- PowerShell / bash / API scripts
- wire to an existing n8n or webhook
- run instructions and limits
DELIVERABLE
- script or workflow in an agreed repo / file
- short runbook
- recorded limits and owner
PROCESS
- manual procedure and success condition
- automation in a lab / on a copy
- documentation and hand-off
IT automation without a procedure repeats the error faster. Before writing a loop: what is the manual step, what counts as success, what is the rollback, and who gets the alert when it fails.
I build small, readable automations: PowerShell, bash, API calls, webhooks or an existing n8n — with a log and a scoped boundary. The goal: less hand checklist work for onboarding, backups, reports or repeatable config changes, more repeatable results you can audit.
Not: “AI will run the company”. Not: an unreadable one-liner on production with no owner and no test on a copy.