---
name: zapier-automation-workflow-planner
description: "A build-ready automation plan: trigger, every step with the exact app event and field mapping, branching and error handling where asked, a test checklist, and the hours it saves each month. Use when a repetitive manual process needs turning into an automation with a defined trigger, steps, and field mappings. Do not use for writing custom code or an API integration, or choosing a CRM. Related topics: automation, productivity, zapier."
---

# Zapier Automation Workflow Planner

A build-ready automation plan: trigger, every step with the exact app event and field mapping, branching and error handling where asked, a test checklist, and the hours it saves each month.

## When to use

Use this skill when a repetitive manual process needs turning into an automation with a defined trigger, steps, and field mappings. Do not use it for writing custom code or an API integration, or choosing a CRM.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Define the trigger as one precise app event and name the payload fields the later steps will use.
3. List every action step in execution order with app, event, field mapping, and any formatter or delay step.
4. Write branch conditions and both outcomes when conditional logic is on, and a named failure and fallback per step when error handling is on.
5. Estimate monthly task usage from the frequency and the hours saved against the current manual time.
6. Produce the test checklist with sample data and one case that must not fire, when requested, and flag any step touching personal or payment data.

## Inputs

- **Manual process today** (longer free text)
- **How often it happens** (choose one: Multiple times daily, Daily, Weekly, Monthly, On-demand/trigger-based)
- **Time spent manually** (free text, e.g. "30 minutes a day or 2 hours a week")
- **Trigger app (where the process starts)** (free text, e.g. "Gmail or Typeform or Shopify")
- **Action apps (where data goes or things happen)** (longer free text)
- **Automation platform** (choose one: Zapier, Make (Integromat), n8n, Power Automate, Pipedream, IFTTT, Other)
- **Include conditional logic (if/else)** (choose one: Yes, No)
- **Include error handling / fallback steps** (choose one: Yes, No)
- **Multi-step workflow (3+ actions)** (choose one: Yes, No)
- **Include a testing checklist** (choose one: Yes, No)

## Output

A plan with the trigger, a numbered step table (app, event, field mapping, notes), branch and fallback rules where enabled, a task-usage and time-saved estimate, and an optional test checklist.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Zapier Automation Workflow Planner

Plan an automation that removes a repetitive task, ready to build in Zapier, Make, n8n, or similar.

#### Task to automate
- Manual process today: {{Manual process today}}
- How often it happens: {{How often it happens}}
- Time spent manually: {{Time spent manually}}

#### Apps and tools
- Trigger app (where the process starts): {{Trigger app (where the process starts)}}
- Action apps (where data goes or things happen): {{Action apps (where data goes or things happen)}}
- Automation platform: {{Automation platform}}

#### Workflow design
- Include conditional logic (if/else): {{Include conditional logic (if/else)}}
- Include error handling / fallback steps: {{Include error handling / fallback steps}}
- Multi-step workflow (3+ actions): {{Multi-step workflow (3+ actions)}}
- Include a testing checklist: {{Include a testing checklist}}

Start by naming the single trigger event precisely (new row added, not spreadsheet updated), since a vague trigger is the usual cause of duplicate runs. Lay out the steps in execution order, one per line: app, event, and the field mapping from the trigger payload, with any formatter or delay step called out. Where conditional logic is on, write the branch conditions as the platform would evaluate them and say what happens on each branch, including the do-nothing path. Where error handling is on, name the failure most likely for each step (missing field, rate limit, duplicate record) and the fallback. Note which steps count as tasks on the chosen platform and estimate the monthly task usage from the frequency, then the hours saved per month against the time currently spent. If a testing checklist is on, list the test cases with sample data, including the edge case that should not fire. Flag any step that handles personal or payment data and the permission the connected account needs.

## Pitfalls

- Choosing a broad trigger like 'updated record', which fires on every edit and runs the automation repeatedly.
- Mapping fields by name without checking the trigger payload actually contains them.
- Skipping the dedupe step, so a retried trigger creates the same record twice.
- Forgetting that each filter and formatter step counts toward the task quota.
