There's a version of you that spends three hours a week copying data from one spreadsheet into another. There's another version that delegates that to an AI-assisted workflow, takes 20 minutes to set it up, and uses the other two hours and forty minutes for something that actually requires a brain.

AI automation prompts can get you from the first version to the second. But only if you know what to ask, what to hand off, and where to stay in the loop yourself.

This is the practical guide. Ten copy-paste prompts, a reusable formula, and a few honest warnings about what happens when people let AI design workflows without any human in the room.

What makes an AI automation prompt actually work?

The short version: specificity and scope. Most people write prompts like "automate my onboarding process" and wonder why the output looks like a consulting deck nobody asked for.

A useful automation prompt names the task, the context, the tools involved, the expected input and output, and any constraints. That's the formula:

Task + Context + Tools + Input → Output + Constraints

So instead of "automate my onboarding process," you get: "I run a five-person marketing team. Our new hire onboarding takes three hours of my time per person. The steps are [X, Y, Z]. We use Notion, Slack, and Google Drive. Draft a workflow that reduces my manual involvement to just the first meeting and final sign-off."

That's something an AI can actually work with. The vague version gets you a confident-looking list of suggestions that could apply to literally any company on earth.

Before you start: what not to paste into an AI tool

Stop here for two minutes before you throw your company's process docs into ChatGPT.

Do not paste any of the following into an unapproved AI tool:

Replace real names with placeholders ("Customer A," "Employee 1"). Swap real figures for sample numbers. Run your company's actual sensitive workflows only in tools your IT or security team has approved and reviewed. If you're not sure what's approved, ask before you start, not after you've pasted six months of customer records into a free tool.

This isn't bureaucratic theater. It's just not making a preventable mistake. The prompts below work just as well with fake sample data.

AI automation prompts: 10 templates you can use today

These are designed for normal work situations. Copy them, fill in the brackets, and adjust for your actual context.

Prompt 1: Should this task even be automated?

Use this before you build anything.

"I'm considering automating [describe the task]. It happens [frequency] and currently takes [time]. The inputs are [what comes in] and the output is [what goes out]. Who currently handles it: [role]. What could go wrong if it runs incorrectly: [consequences]. Given this, help me evaluate whether automation makes sense, what the risks are, and what I'd need to have in place first."

This is the prompt most people skip. They jump straight to building the Zapier flow and discover six months later that the "automated" process has been sending the wrong data to the wrong place. Spend ten minutes here first.

Prompt 2: Map a messy process before you automate it

"Here's a rough description of how we currently handle [process]: [paste your notes]. It's messy and inconsistently followed. Based on this, help me map the actual steps in order, identify where the process usually breaks down, flag any steps that require human judgment, and note any steps that seem redundant or unclear. Use a numbered list."

Rule #13 from Don't Replace Me puts it plainly: garbage in, garbage out. If your source notes are vague, the AI will invent plausible-sounding steps. Your job is to review the output and flag anything it invented. The AI is mapping. You're verifying.

Prompt 3: Turn rough notes into a working SOP

"I've mapped out the following steps for [process name]: [paste step list]. Convert this into a formal Standard Operating Procedure. Include: purpose, scope (who this applies to), step-by-step instructions in plain language, decision points where human judgment is required, and a 'things that can go wrong' section at the end. Do not invent policy, approvals, or compliance requirements I haven't specified."

That last line matters. AI will happily write "Step 7: Ensure GDPR compliance" without any idea whether your process actually satisfies GDPR. You need to catch and verify every claim like that.

Prompt 4: Design a Zapier or Make-style workflow

"I want to automate the following using [tool name, e.g., Zapier, Make, n8n]: [describe trigger and desired outcome]. The systems involved are [list apps]. The input data looks like [describe fields or paste a sample with fake data]. The desired output or action is [what should happen]. Draft a step-by-step workflow including trigger, filters, actions, and error handling. Flag any steps that will need a human check before they run."

Do not let this output go live without someone who actually knows the tools reviewing it. AI can describe a logical workflow. It can't tell you whether your specific Zapier plan supports that many steps, or whether the API field mapping is actually correct.

Prompt 5: Create intake form questions for a new workflow

"I'm building an intake process for [what you're collecting, e.g., client project requests, IT support tickets, content briefs]. The person submitting the form is [describe them]. The person reviewing it needs to be able to [what they need to do with it]. Draft 8-12 intake questions that would capture everything needed without being overwhelming. Flag any questions where the answer will affect routing or priority."

Good intake design is half the battle. Most automated workflows fail because the input data is incomplete or inconsistent. This prompt helps you fix that before you build.

Prompt 6: Write QA checks for an automation

"I've built an automation that does the following: [describe what it does, step by step, using fake/sample data]. Draft a QA checklist I can run before going live. Include: what inputs to test, what outputs to verify, edge cases to check, failure modes to simulate, and what a 'pass' looks like for each check."

Test with fake data. Always. Run the live version first in a sandbox or with a small pilot group. An automation that quietly fails at scale is worse than one that never launched.

Prompt 7: Identify edge cases you haven't thought of

"Here's my planned automation for [process]: [describe it]. I've tested the happy path. Help me think through edge cases that could break it or produce incorrect results. Consider: unusual input formats, missing data, timing issues, duplicate entries, permission problems, and scenarios where the automation should stop and escalate to a human instead of continuing."

This one earns its keep. AI is genuinely useful for "what could go wrong" brainstorming because it has seen a lot of broken systems in its training data. You still have to decide which edge cases are worth building for, but it'll surface things you hadn't considered.

Prompt 8: Add human approval gates to a workflow

"Here's my automation workflow: [describe it]. I want to add human approval gates at the right places. Suggest where a human should review before the automation proceeds, what information they'd need to see to make that decision, what happens if they approve vs. reject, and how long the workflow should wait before escalating or timing out."

This is where most automation plans break down. Someone builds a fully automated flow, removes every human checkpoint, and is then surprised when the automated system approves a client deliverable that's completely wrong. Knowing where to keep humans in the loop is a skill. AI can help you map the gates. You decide which ones stay.

Prompt 9: Draft a handoff message for an automated step

"My automation will send a notification/message to [recipient role] when [trigger]. The context they'll need: [what happened, what they need to do, what the deadline is]. Draft a clear, brief message that explains the situation and next step without requiring them to look anything up. Tone: [professional/casual]. Include a link placeholder and a clear action item."

Automated messages that make people hunt for context get ignored. This prompt helps you write the version they actually read.

Prompt 10: Review an automation after it's been running

"My automation has been running for [time period]. Here's what it does: [describe]. Here's what I've noticed: [any issues, complaints, workarounds people are using]. Help me conduct a post-launch review. Suggest: metrics to check, user feedback questions to ask, common failure patterns to investigate, whether the original goals are being met, and what I'd change in the next version."

Automation is not "set it and forget it." You need a rollback plan when something breaks, an audit log to see what ran and when, and a review cycle to catch drift. Build those in before launch, not after the first incident.

This came from a book.

Don't Replace Me

200+ pages. 24 chapters. The honest version of what AI means for your career, written by someone who actually builds this stuff.

Get the Book →

The safety rules, restated plainly

You're going to want to skip this section. Don't.

AI can draft a workflow, suggest edge cases, write SOPs, and map a process in minutes. It cannot:

Do not let AI invent policies, approvals, integrations, data mappings, compliance claims, budgets, timelines, or customer commitments. Review every output before it touches real systems. Keep an audit log. Know how to turn it off. Test with fake data first.

The human in the loop isn't a bottleneck. It's the point. For a broader look at where that line is, what AI can and can't do is worth reading before you hand off anything with real consequences.

What this connects to in your broader ops stack

These automation prompts don't exist in isolation. If you're building out workflows, you probably also need solid project tracking (the AI project management prompts are useful here), clean documentation (AI documentation prompts cover turning messy notes into structured docs), and eventually a policy layer (AI policy prompts help you write the rules people will actually follow).

The mistake most teams make is automating before they've documented. You end up with a Zapier flow that nobody understands, that breaks every three months, and that only one person knows how to fix.

Map it first. Document it. Then automate. In that order.

Frequently asked questions

What are AI automation prompts?

AI automation prompts are structured instructions you give to a tool like ChatGPT or Claude to help you design, map, or document a workflow. They're not code. They produce text: SOPs, checklists, workflow descriptions, QA steps, intake questions. A human still builds and runs the actual automation.

Can I use ChatGPT to build a Zapier or Make workflow?

You can use it to describe and plan the workflow, which is genuinely useful. You can't paste the output directly into Zapier and have it run. You'll still need to build the actual automation in the tool, verify the field mappings, and test it before going live. Think of the AI output as a blueprint, not a finished build.

What data is safe to paste into an AI tool when designing automations?

Fake or anonymized data only, unless your company has approved a specific tool for sensitive use. Replace real customer names, IDs, and contact details with placeholders. Never paste API keys, credentials, financial records, HR data, or anything under an NDA. Check your company's AI usage policy first. If there isn't one, that's a gap worth flagging. The AI policy prompts article has templates to help draft one.

Should every step in an automation have a human approval gate?

Not every step, but more than most people include. The right gates are where: the output affects a customer directly, the data is sensitive, the action is irreversible, or the decision requires context the automation doesn't have. AI is helpful for identifying where those gates should be. You decide which ones to keep.

How do I know if a task is worth automating?

Use Prompt 1 above before you build anything. The basic test: does it happen frequently, follow consistent rules, use predictable inputs, and not require judgment calls? If yes, it's a candidate. If the answer is "sometimes, it depends," that's a signal to document the decision logic before automating, not after. A good starting point is the how to use AI at work guide for thinking about which tasks to hand off first.

What happens when an automation breaks?

You need a rollback plan before launch, not after the first incident. That means: knowing how to disable the workflow immediately, having an audit log of what ran and when, and knowing who to notify. AI can help you draft a rollback plan as part of your QA checklist. The accountability for fixing it is yours.