# Zap blueprint: Draft support replies from your help docs

**This is a blueprint, not an import file.** Zapier has no public format for importing Zaps, so you rebuild these steps by hand in the Zap editor. It takes about 10–20 minutes (our estimate).
Create a new Zap: https://zapier.com/app/editor
Full recipe: https://recipeagents.usestarbase.com/recipes/support-reply-draft

## Steps
1. **Trigger:** Gmail: New Email Matching Search
   - Recipe input: Support email, your help-doc text
2. **Filter by Zapier** (optional): only continue if the input is the kind you want (see the recipe's failure modes).
3. **Action:** ChatGPT (OpenAI): Conversation, or AI by Zapier
   - Paste this prompt and map the trigger fields into the {{...}} placeholders:

```
Answer this customer using ONLY the docs below. If the docs don't cover it, reply 'NEEDS_HUMAN' and say what's missing. Under 120 words, friendly, link the doc section used. Docs: {{docs}} Email: {{email}}
```
4. **Action:** Formatter by Zapier → Utilities → Import JSON / or Code by Zapier, to split the JSON fields (if the prompt returns JSON).
5. **Action:** Gmail: Create Draft
6. **Test each step** with a real example, then turn the Zap on. Keep a human approval on anything customer-facing.

## Recipe steps (from the page)
- Trigger: new conversation.
- AI step with the prompt below plus the relevant doc sections.
- Save as a draft or internal note, never auto-send.
- Tag 'ai-draft' so you can review quality weekly.

## Where it breaks
- Confident wrong answers: Keep NEEDS_HUMAN, and never let it auto-send.
- Out-of-date docs: The draft is only as good as the docs, so fix the doc rather than the prompt.

App and step names follow Zapier's current app directory as of 2026-10-16. Names change, so search the app in the editor if a step looks different.