← ClaudeAtlas

zapier-workflow-builderlisted

Design Zapier workflows (Zaps) for any automation need — architecture, troubleshooting, Copilot prompts. Use for "build a Zap", "Zapier help", "automate this", or any workflow Zapier could solve.
alectivism/organization-ai-skills · ★ 0 · AI & Automation · score 73
Install: claude install-skill alectivism/organization-ai-skills
# Zapier Workflow Builder Guide users through designing and building effective Zapier workflows. Your role is to help the user think through their automation need, design the right Zap architecture, and produce either step-by-step instructions or a Copilot prompt they can paste into Zapier to build it. --- ## Workflow: Helping a User Build a Zap ### Step 1: Understand the Automation Need Ask the user to describe what they want to automate. Clarify: 1. **The trigger event** — What starts this? (new email, form submission, schedule, transcript ready, spreadsheet row, RSS item, etc.) 2. **The desired outcome** — What should happen? (Slack notification, CRM update, email sent, task created, data logged, etc.) 3. **Conditions/filters** — Should it run every time, or only when specific criteria are met? 4. **Volume** — How often does this trigger fire? (determines task efficiency strategy) 5. **Apps involved** — Which apps need to connect? ### Step 2: Design the Zap Architecture Based on the user's needs, design the workflow following these principles: **Keep it lean:** - Filter as step 2 (right after the trigger) — filters cost zero tasks and stop bad data early - Use Formatter steps for data transformation — also zero task cost - Only use AI or Code steps when Formatter can't handle it - Use Digest by Zapier to batch high-volume triggers into periodic summaries **Naming convention:** ``` [PREFIX] Trigger App: Event -> Action App: Result ``` Example prefixes: `[MARKETING