Automation Prompts

Prompts for mapping processes, designing workflows and writing automation specs. They make the AI ask about triggers, edge cases and failure handling before suggesting tools.

• Business Automation Workflow: Design automation workflows for repetitive business tasks.
• No-Code Workflow Design: Design a no-code automation that handles failure sensibly.
• Process Mapping: Map a process as it actually runs before changing it.
• Email Automation Rules: Automate email triage with rules that do not hide important messages.
• Data Sync Integration Plan: Keep two systems in sync without corrupting either.
• Notification Strategy: Decide what warrants interrupting a person and what does not.
• Report Automation Spec: Automate a recurring report, or establish it is not worth producing.
• Approval Workflow Design: Design approvals that control risk without becoming a queue.
• Employee Onboarding Automation: Automate the administrative half of onboarding so the human half can happen.
• Social Posting Automation: Schedule social content without losing the ability to respond.
• Backup and Recovery Plan: Automate backups and prove they can actually be restored.
• Customer Support Macros: Write support templates that speed replies without sounding canned.
• Workflow Documentation: Document an automation so someone else can maintain it.

Best automation prompts, in full

The top 3 by score on the free Verbito Prompt Scorer.

Data Sync Integration Plan (score 100/100)

You are an integration engineer who has fixed several corrupted syncs. Plan a sync between [INSERT SYSTEM A] and [INSERT SYSTEM B] for [INSERT DATA].

Produce:

1. Direction: one-way or bidirectional, and why bidirectional is riskier
2. The system of record for each field, decided explicitly
3. Field mapping including type and format differences
4. Matching key used to identify the same record in both systems
5. Conflict resolution when both sides changed since the last sync
6. Sync frequency and whether real-time is genuinely needed
7. Initial load strategy and how to avoid creating duplicates
8. Deletion handling, which is where most syncs cause damage
9. Error handling, retries and idempotency
10. Monitoring: how a partial failure is detected before someone notices bad data
11. A rollback plan

Never sync deletions bidirectionally without an explicit review step. A deletion loop can empty both systems, and restoring from backup rarely recovers the relationships.

Tone: careful and specific about failure modes.

Audience: the engineers building the sync and the operations owner who handles failures. Context: the goal is no duplicate or lost records across [INSERT DAILY VOLUME] daily changes.
Keep the plan under 800 words. Example rule: "Conflict on the same field: the most recent update wins; log both values for review."

Employee Onboarding Automation (score 90/100)

You are an HR operations lead who automates the paperwork rather than the welcome. Design onboarding automation for [INSERT COMPANY] hiring [INSERT ROLE TYPE].

Produce:

1. The full checklist from offer acceptance to day 30
2. Which items are administrative and automatable, and which must stay human
3. Trigger points: offer signed, start date confirmed, day one, week one
4. System provisioning: accounts, access, equipment, with the lead time each needs
5. Document collection and compliance steps
6. Automated communications, with the content of each
7. Manager prompts, since manager preparation is the most common failure point
8. Buddy assignment and introduction
9. Check-in scheduling at day 1, 7, 30 and 90
10. Offboarding of access if the hire does not start, which is frequently forgotten
11. Exception handling for contractors and remote hires

Automate provisioning and paperwork. Never automate the welcome message from a manager — a templated personal greeting is worse than none.

Tone: operational and humane.

Audience: the HR team who will run it and the IT admin who sets it up. Context: the goal is a new hire with every account working before 10am on day one.
Keep it to one page. Example step: "Offer signed: create Google account, add to Slack #new-joiners, send laptop order."

Workflow Documentation (score 88/100)

You are an automation engineer documenting for the person who inherits this. Document [INSERT AUTOMATION OR WORKFLOW].

Produce:

1. Purpose: what it does and what would happen without it
2. Owner and escalation contact
3. Trigger and schedule
4. Step-by-step logic, in plain language before any technical detail
5. Systems touched, with the credentials or connections used and where they are stored
6. Data flow: what comes in, what is written, and where
7. Configuration values and their meaning, particularly any magic numbers
8. Known limitations and deliberate design decisions, with the reasoning
9. Failure modes: what breaks it, what the symptom looks like, and the fix
10. How to test safely without affecting production data
11. How to disable it in an emergency
12. Dependencies on upstream systems and who to notify if they change

The most valuable section is failure modes. Whoever reads this is most likely reading it because something has already broken.

Tone: clear and practical. Written for a stranger at short notice.

How to use these prompts

1. Copy the prompt that matches your task.
2. Replace every [INSERT ...] part with your own details: the more specific, the better the answer.
3. Paste it into ChatGPT, Claude or Gemini. To tailor it to your exact situation, describe your goal in the Verbito prompt generator instead.

Build a automation prompt for your task · The 100 best prompts in one kit

Create a prompt or contact Verbito.