AI Prompts for Automation Builders

Practical prompts for planning, designing, documenting, and improving automation workflows in Make, Zapier, n8n, and Gumloop.

Who These Prompts Are For

Automation builders, freelancers, operators, and small business owners who build repeatable workflows. These prompts help you find what’s worth automating, map the steps, pick triggers and actions, plan for errors, and document the workflow so it’s maintainable.

How to Use These Prompts

Copy any prompt into ChatGPT, Claude, Gemini, or another AI tool. Replace bracketed placeholders like [tool], [process], and [trigger]. Tell the AI which automation platform you use (Make, Zapier, n8n, Gumloop) so the output matches it.

Workflow Discovery Prompts

Find automation opportunities:

Act as an automation consultant. Here's how I (or my client) spend a typical week: [describe tasks, tools, and roughly how often each happens].

Identify the top 5 tasks worth automating. For each, give:
- Why it's a good candidate (repetitive, rule-based, frequent)
- Rough time saved per week
- Risk level if it occasionally fails
- The tools it would connect

Rank them by value-to-effort and recommend where to start.

Map a manual process:

Help me map this manual process step by step so I can automate it.

The process: [describe what happens from start to finish]
Tools involved: [list]

Output a numbered map with: trigger, each step, the data passed between steps, decision points, and the final result. Flag any step that needs a human decision.

Rank tasks by automation value:

Here are tasks I'm considering automating: [list them].

Score each from 1-5 on: frequency, time saved, how rule-based it is, and risk if it fails. Put them in a table, calculate a simple priority score, and tell me which 3 to automate first and why.

Trigger and Action Prompts

Choose triggers and actions:

I want to automate this in [Make / Zapier / n8n / Gumloop]: [describe the workflow].

Recommend:
1. The trigger (what starts it) and why
2. The sequence of actions
3. Any filters or conditions needed
4. The data fields that pass between steps

Use the module/action names from [the tool] where you can.

Design a multi-step workflow:

Design a multi-step automation for: [describe the outcome].

Inputs available: [data/sources]
Tools: [list]

Give me the full flow as: Trigger → Step → Step → Output. For each step include what it does, the input it needs, and the output it produces. Mark steps that should run only if a condition is met.

Add branching logic:

My automation needs to handle different cases. Here's the situation: [describe the workflow and the variations].

Design the branching logic. For each branch, give: the condition that triggers it, the steps it runs, and what happens if none of the conditions match. Keep the branches as few as possible.

Error Handling Prompts

Test failure cases:

Here's my automation: [describe the flow and the tools].

List the ways it could fail: missing data, rate limits, bad formatting, duplicate records, API errors, and edge cases. For each, suggest how to detect it and what the automation should do instead of breaking.

Add error notifications:

Help me add error handling to this automation: [describe it].

Design: where to add error catches, what message to send me when something fails (include which step, the input, and the error), and which failures should retry vs. stop and alert. Keep notifications useful, not noisy.

Plan for bad or missing data:

My automation processes [type of data] from [source]. The data is sometimes messy.

List the data problems to expect (empty fields, wrong formats, duplicates, unexpected values). For each, give a rule for how the automation should clean it, skip it, or flag it for review.

Client Automation Prompts

Run a client automation audit:

Act as an automation consultant preparing for a client call. The client does: [describe their business and main manual tasks].

Write 12 discovery questions that uncover repetitive work, tools they use, where errors happen, and what they wish was automated. Group the questions by theme and keep them plain-spoken.

Create an automation checklist for a client:

Create a pre-build checklist for a client automation project.

Workflow: [describe]
Tools: [list]

Cover: access and credentials needed, data to confirm, edge cases to clarify, approval points, and how we'll test before going live. Format as a checklist the client and I can both sign off on.

Write client handoff notes:

Write handoff documentation for an automation I built for a client.

What it does: [describe]
Trigger: [describe]
Steps: [list]
Tools: [list]

Include: a plain-language summary, what to do if it breaks, what NOT to change, and who to contact. Write it so a non-technical person can follow it.

Documentation Prompts

Document workflow logic:

Document this automation clearly: [describe the trigger, steps, tools, and conditions].

Output: a short overview, a step-by-step breakdown, the data passed between steps, the conditions/branches, and known limitations. Use plain language and a format I can paste into a wiki or Notion.

Write a workflow changelog entry:

I just changed an automation. Here's what I changed: [describe the change and why].

Write a short changelog entry with: date, what changed, why, and any impact on how it runs. Keep it to a few lines so the log stays readable over time.

Create a maintenance checklist:

Create a maintenance checklist for an automation that [does X] using [tools].

List what to check weekly and monthly: error rates, data quality, expired credentials, rate limits, and whether the workflow still matches the real process. Keep each item to a quick yes/no check.