I pulled these 22 automation prompts out of my big AI prompt examples guide because they work differently from normal chat prompts. You're not asking for a paragraph of text. You're describing a job a tool should run on its own.
Most of them are written for n8n workflows. The coding ones are for Claude Code and Codex, and a couple are plain chat prompts for Gemini or Claude Projects. I tag the platform under each one.
If you want simpler, everyday prompts first, start with my AI prompt examples guide.
How I Write Automation Prompts
Automation prompts need one more layer than a chat prompt. In n8n's AI Agent node, the system prompt sets the role and rules, and the incoming trigger data is the actual request.
Claude Code and Codex work more like a junior developer. They plan, edit files, run tests and try again until the job is done.
I built every automation prompt below around five parts: the trigger or goal that starts the work, the specific inputs available, the step-by-step logic to follow, the expected output format, and what to do if something fails or data is missing.
Sources: n8n Docs, AI Agent node, n8n Docs, build an AI workflow, Anthropic, how Claude Code is used in practice, OpenAI, introducing Codex
Workflow Automation
1. Auto-Route And Reply To Inbound Support Emails
I use this to stop simple, repetitive support emails from sitting in a queue for hours.
Build a workflow that triggers when a new email arrives in [enter your support inbox here]. Classify the email's intent into one of these categories: [list your common categories here, for example billing question, how-to question, bug report]. If the intent matches a category with a known template, draft a reply using that template and send it automatically. If the intent does not clearly match, route the email to [enter your team's ticket queue or Slack channel here] for a human to handle. Log every classification decision to [enter your logging destination here].
Platform: n8n, for the trigger, classification, and routing logic in one workflow.
2. CRM Contact Sync To Email Tool And Slack
I use this so a new contact never sits in one system without showing up in the others.
Build a workflow that triggers when a new contact is created in [enter your CRM name here]. Pull the contact's name, email, and [list any other fields you need here]. Add this contact to [enter your email marketing tool name here] with the tag [enter your desired tag here], and post a notification to [enter your Slack channel here] with the contact's name and source. If the contact already exists in the email tool, skip the add step and only send the Slack notification.
Platform: n8n, for the multi-app sync and conditional logic.
3. Auto-Create Tasks From Form Submissions
I use this so nothing submitted through a form gets lost in an inbox.
Build a workflow that triggers when a new submission comes in from [enter your form tool name here]. Extract the fields [list the form fields here] and create a new task in [enter your project management tool name here] with a title based on [enter which field to use as the title here], the description populated from the remaining fields, and the assignee set to [enter default assignee or routing logic here].
Platform: n8n, for the form trigger and task creation across tools.
4. Draft-Reply Watcher For Shared Inbox FAQs
I use this to speed up response time without letting an AI send unreviewed replies to customers.
Build a workflow that monitors [enter your shared inbox name here] for new messages. When a message matches one of these frequently asked questions: [list your FAQ topics here], draft a reply using the appropriate answer and save it as a draft in the inbox rather than sending it automatically. Notify [enter your team member or channel here] that a draft is ready for review.
Platform: n8n, for the monitoring and draft-creation logic.
5. Scheduled Two-Way Spreadsheet Or Database Sync
I use this to stop manually copying data between a spreadsheet and a database every week.
Build a workflow that runs on a schedule every [enter your desired frequency here, for example day or hour]. Pull new or updated rows from [enter your source, for example a Google Sheet or database table] and sync them to [enter your destination system here]. Match records using [enter your unique identifier field here] to avoid creating duplicates. If a sync fails for any row, log the error with the row identifier to [enter your error log destination here] instead of stopping the whole workflow.
Platform: n8n, for the scheduled trigger and error-handled sync logic.
Workflow automation moves data. Content automation moves the actual words and posts I already write once into every place they need to live.
Content Automation
6. Auto-Repurpose Long-Form Content Into Multiple Social Posts
I use this so publishing one article automatically feeds my social calendar instead of creating extra work.
Build a workflow that triggers when a new blog post is published on [enter your CMS or blog platform here]. Pull the post title and body, then generate 3 social post variations for [list your platforms here] summarizing the key takeaway. Queue these posts in [enter your social scheduling tool here] spaced [enter your desired posting cadence here] apart, and flag them for my review before they go live rather than auto-publishing immediately.
Platform: n8n, connected to a text-generation step for the actual post writing.
7. Auto-Translate And Localize New Content On Publish
I use this so international versions of my site do not lag weeks behind the original.
Build a workflow that triggers when new content is published on [enter your CMS here]. Translate the content into [list your target languages here], adapting idioms and cultural references rather than translating word for word. Publish the translated versions to [enter your localized site sections or CMS destinations here], and notify [enter your team member here] to do a final human review before the translated pages go fully live.
Platform: n8n, for the trigger and multi-language publishing pipeline.
8. Auto-Draft Weekly Newsletter From Top Posts
I use this so my newsletter goes out consistently even during a busy week.
Build a workflow that runs every [enter your desired day and time here]. Pull the top [enter number here] performing posts from [enter your content source, for example a blog or content management system] based on [enter your performance metric here, for example views or engagement]. Draft a newsletter summarizing each post in 1-2 sentences with a link, and save the draft in [enter your email tool name here] for my review before sending.
Platform: n8n, for the scheduled pull and draft creation.
9. Auto-Summarize Meeting Transcripts And Route Action Items
I use this so meeting outcomes reach the right task tool automatically instead of staying trapped in a transcript.
Build a workflow that triggers when a new meeting recording or transcript is added to [enter your meeting tool here]. Summarize the transcript into key decisions and action items with an owner and deadline for each. Create a task in [enter your project management tool here] for every action item, assigned to the correct owner, and post the full summary to [enter your team channel here].
Platform: n8n, connected to a summarization step, for the end-to-end routing.
Content automation keeps publishing consistent. Reporting automation makes sure I actually know whether any of it is working.
Reporting Automation
10. Weekly Marketing Performance Report Compiler
I use this so Monday morning starts with numbers already waiting instead of an hour of manual exporting.
Build a workflow that runs every Monday morning. Pull data from [list your data sources here, for example Google Analytics, ad platforms, and email tool]. Compile the key metrics [list your key metrics here] into a single report comparing this week to last week. Highlight any metric that changed by more than [enter your threshold here] percent, and send the report to [enter your destination here, for example Slack or email].
Platform: n8n, for the multi-source pull and scheduled delivery.
11. Plain-English Analytics Exec Summary
I use this to translate a dense export into something a non-analyst will actually read.
Here is a raw analytics export: [paste your data export here]. Summarize this in plain English for a non-technical executive audience. Lead with the single most important trend, follow with 2-3 supporting data points, and end with one clear recommendation based on what the data shows.
Platform: Gemini, for working directly with data pulled from connected Google tools.
12. Monthly SEO Ranking Change Report
I use this to catch ranking movement before it shows up as a traffic problem three months later.
Build a workflow that runs on the first of every month. Pull current keyword rankings for [enter your tracked keyword list or source here] and compare them to last month's rankings. Flag any keyword that dropped more than [enter your threshold here] positions or gained more than [enter your threshold here] positions. Compile the results into a report and send it to [enter your destination here].
Platform: n8n, for the scheduled pull, comparison, and delivery.
13. Recurring Sales Pipeline Health Report
I use this so pipeline problems get caught in a weekly review instead of at quarter-end.
Here is my current CRM pipeline export: [paste your pipeline data here]. Build a pipeline health report covering: total pipeline value by stage, deals with no activity in the last [enter number here] days, deals with a close date in the past that have not been updated, and win rate compared to the prior period. Flag the top 3 risks I should address this week.
Platform: Claude Projects, so this month's report can be compared against prior reports already stored in context.
Reporting tells me what happened. The next category is where AI stops writing about the work and starts doing the work itself.
Coding And Agentic Automation
14. Full Unit Test Suite Writer For Undocumented Code
I use this on old code nobody wants to touch because nobody trusts it.
Here is an existing code module with no test coverage: [paste your code or reference the file path here]. Write a full unit test suite covering the main functions, including edge cases and expected failure scenarios. Run the tests after writing them, and fix any issues you find in either the tests or the underlying code until everything passes cleanly.
Platform: Claude Code, for reading the full module, writing tests, running them, and iterating until they pass.
15. Multi-File Refactor With Pull Request
I use this for refactors that touch too many files to do safely by hand.
Refactor [describe the function, module, or pattern to refactor here] across the codebase to [describe the desired change here, for example use a shared utility function instead of duplicated logic]. Update every file that references the old pattern, run the existing test suite to confirm nothing breaks, and open a pull request with a clear description of what changed and why.
Platform: Codex, for the sandboxed multi-file refactor and automatic pull request creation.
16. Internal CLI Tool Builder
I use this to stop doing a repetitive data task by hand every single week.
Build a small command-line tool that [describe the repetitive task here, for example reads a CSV of customer data and outputs a formatted summary report]. The tool should accept [describe the expected input here] and output [describe the expected output format here]. Include basic error handling for missing or malformed input, and write a short usage instruction at the top of the script.
Platform: Claude Code, for building, testing, and refining the tool interactively.
17. Scheduled GitHub Issue Triage And Labeling
I use this so issues get sorted before I even open my inbox in the morning.
Set up a recurring job that reviews new GitHub issues opened in [enter your repository name here]. For each issue, apply the appropriate label from this list: [list your label options here], based on the issue's content. If an issue is missing key information needed to reproduce it, such as steps to reproduce or environment details, comment asking the reporter for that information.
Platform: Codex, for the scheduled, sandboxed issue review and labeling.
18. CI Pipeline Debugger
I use this the moment a build fails so I am not the one staring at a wall of logs first.
Here is the failing CI pipeline log: [paste your CI log or error output here]. Identify the root cause of the failure, propose a fix, and explain in plain language why the pipeline broke. If the fix requires a code change, make the change and confirm the pipeline would pass by running the relevant tests locally.
Platform: Claude Code, for reading the log, diagnosing the issue, and fixing it directly in the codebase.
Coding automation fixes what is broken in the product. The last category makes sure no lead falls through the cracks while I am busy fixing it.
CRM And Lead Automation
19. Lead Scoring And Auto-Tagging
I use this so my sales team spends time on the leads most likely to actually close.
Build a workflow that triggers when a new lead enters [enter your CRM name here]. Score the lead based on these criteria: [list your scoring criteria here, for example company size, job title, or source]. Apply a tag of hot, warm, or cold based on the score, and notify [enter your sales team channel here] immediately if the lead scores as hot.
Platform: n8n, for the trigger, scoring logic, and notification.
20. Behavior-Based Follow-Up Sequence Trigger
I use this so follow-up timing matches what a lead actually does instead of a fixed calendar schedule.
Build a workflow that monitors lead behavior in [enter your tool here, for example email opens, website visits, or content downloads]. When a lead performs [describe the trigger behavior here, for example visits the pricing page twice in one week], automatically enroll them in [enter your follow-up sequence name here] and notify their assigned sales rep.
Platform: n8n, for the behavior monitoring and sequence enrollment.
21. New Signup To Onboarding Sequence Automation
I use this so every new customer gets the exact same strong first experience, automatically.
Build a workflow that triggers when a new customer signs up for [enter your product or service here]. Add them to [enter your onboarding email sequence tool here], create an internal task for [enter your customer success team here] to schedule a welcome call, and post a notification to [enter your team channel here] with the new customer's name and plan tier.
Platform: n8n, for the multi-step onboarding trigger sequence.
22. Auto-Alert On High-Intent Lead Activity
I use this so a sales rep never finds out about a hot lead a day too late.
Build a workflow that monitors [enter your tracked activity source here, for example website analytics or product usage data] for high-intent signals such as [list your high-intent signals here, for example requesting a demo or viewing the pricing page multiple times]. When a signal fires, immediately notify the assigned sales rep in [enter your notification channel here] with the lead's name and the specific action they took.
Platform: n8n, for the real-time monitoring and alerting.
Frequently Asked Questions (FAQs)
What is the difference between Claude Code and Codex for automation?
Claude Code runs an interactive loop where it plans, edits files, runs tests and iterates with you in real time, which I like for hands-on development work. Codex cloud tasks run in a sandbox where agent internet access is off by default, which suits well-defined jobs like issue triage or a scoped refactor that opens its own pull request.
Can I use these prompts in Zapier or Make instead of n8n?
I wrote and tagged the workflow prompts for n8n. Each one spells out the trigger, the steps, the output and what to do when something fails, so you can use that same plan to build the workflow in another automation tool, but I haven't tested them there.
Do I need a paid plan to run these automations?
It depends on the tool. n8n's Community Edition is free to self-host. Claude Code needs a paid Claude plan (Pro or higher) or an API account, and Codex cloud tasks are available on eligible paid ChatGPT plans.
Final Thoughts
Pick the one automation that would save you the most time this week and build just that. Once it runs on its own for a few days, add the next one.
Sources: n8n Docs, AI Agent node, n8n Docs, choose your n8n, OpenAI Codex docs, internet access, Claude Help Center, Claude Code with Pro or Max, OpenAI Help Center, Codex with your ChatGPT plan




