Automation
Setting AI up to handle a repeatable job on its own, triggered by a time or an event like a new form entry, so the work happens without you starting it each time.
Also called: workflows · AI workflows · Zaps · flows · no-code automation · agentic workflows
Connections
Understand first
Ideas this one builds on.
Leads on to
Ideas that build on this one.
Related
Often used together or easily confused.
Skills that use it
Resources that teach it
- AI Fluency: Framework & Foundations (garden)
- AI Fluency for Nonprofits (garden)
- Introduction to Claude Cowork (garden)
- OpenAI Academy: Apply AI at Work track (garden)
- How I AI (podcast) (garden)
- How I AI workflow guides (garden)
- ChatGPT for Knowledge Work (garden)
- The Eight Levels of AI Adoption (garden)
- Not all AI agents are created equal (garden)
- This week on How I AI: Claude Cowork tutorial for non-engineers + Build your own Slack inbox (for $0) (garden)
- Making AI Work: Leadership, Lab, and Crowd (garden)
- Introducing My New AI Learning Path and Co-Pilot (garden)
- Behind the Craft (YouTube channel) (garden)
- n8n Tutorial: Build an AI Workflow to Extract Top Insights From All Your Newsletter Emails (garden)
- Perplexity at Work Guide (garden)
Competency
Find automation on the commons map ↗
You may know it from
- manufacturing an assembly line Break a job into fixed steps, and put inspection points where errors would be costly.
- office work mail merge
In products
The same idea, under different names in different tools.
| Provider | What they call it |
|---|---|
| Zapier | Zapier AI steps and agents |
| Make | Make AI scenarios |
| N8n | n8n AI workflows |
| Microsoft | Power Automate with Copilot |
In plain words
Automation means a task runs without you pressing go. Something triggers it (a new form submission, an email arriving, a date) and a chain of steps follows, some done by AI. A new volunteer signs up, AI drafts a welcome email in your voice, and it lands in your drafts folder for a quick look.
Workflow automation has been around for decades. AI adds steps that need judgment: summarising, sorting by meaning, drafting replies, pulling details out of messy text. Those steps can also get things wrong, so plan for mistakes. Put a person at the points where a mistake would be costly, and send the AI’s output somewhere you will see it before it goes out.
A good rule is to automate something only after you’ve done it by hand with AI several times and know what good looks like.
Example
A nonprofit’s intake form feeds into a workflow: AI reads each request, tags it as housing, food or legal, and drafts a reply. A caseworker approves the replies each afternoon. Misfiled requests drop from common to rare after one prompt fix.
How it connects
- Needs tools and connectors to reach the apps involved.
- Scheduled tasks are the simplest version; agents handle the messier ones.
- Human in the loop checkpoints and evals keep it trustworthy.
Try it
Write down a task you’ve done with AI at least three times, then mark the step where a mistake would hurt most. When you automate the task, put your approval step there.
Read this card as plain Markdown: /concepts/con-automation.md. Know a parallel from your own field, or a product that implements this? Add it.