Automate the boring stuff: 7 recipes anyone can set up

Automation has a reputation problem. It sounds like a project — a weekend of scripting, a tool to learn, a system to maintain. In practice the recipes worth having take about ten minutes each and never need attention again.

The rule for choosing what to automate is simple: it should be something you do at least weekly, it should have no judgement in it, and it should be dull enough that you resent doing it. Anything with a decision in the middle is a bad candidate, because you will end up checking the automation, which costs more than the task did.

Seven that pay for themselves

• Attachments to cloud storage. Any email from a known sender with a PDF attached lands in a dated folder automatically. Invoices and statements file themselves.
• Screenshot housekeeping. New screenshots move out of the desktop into a folder, renamed with the date. The desktop stays a workspace instead of a dumping ground.
• Form submission to spreadsheet to notification. A new enquiry appends a row and pings the right channel. This one replaces a person checking an inbox.
• Recurring task creation. The monthly reporting checklist generates itself on the first working day, fully populated, rather than being remembered.
• Calendar to focus mode. When an event starts, notifications go quiet and the right app opens. When it ends, everything comes back.
• Saved-article roundup. Everything you saved this week arrives as a single digest, so reading has a slot instead of interrupting.
• Backup verification. A weekly message confirming the backup ran. Trivial to set up, and the only reason anyone ever finds out a backup has been silently failing.

Where automations go wrong

Three failure modes account for almost everything. Silent failure is the worst: the automation stops and nothing tells you, so you carry on assuming files are being filed. Every automation that matters needs a visible output — a notification, a log, a folder you glance at — so its absence is noticeable.

Over-triggering is next. A rule matched too broadly fires on things you did not intend, and cleaning up after it costs more than the manual task. Start with the narrowest possible condition and widen it only when it demonstrably misses things.

Undocumented magic is the slow one. Six months later a file appears somewhere and nobody knows why. Keep a single note listing what each automation does, what triggers it, and where it lives. Ten lines of documentation is the difference between a system and a haunting.

Which tool

Use whatever is already on the machine before subscribing to anything. Built-in shortcut and workflow tools on both major desktop platforms handle the file and folder recipes without an account. Mail rules handle the email ones. Reach for a hosted automation platform only when you genuinely need to connect two web services that cannot see each other — which is roughly two of the seven above.