Give each new matter an email label Get the source data and prepare the review Documentation-verified component path; proposed adaptation, not tested WHAT WAS CHECKED Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Menus/features are vendor-documented; prompts, field maps and human gates are editorial adaptations. No actual client work, account login, installation, connection, external write or site edit occurred. BEFORE YOU START - Existing Zapier account and approved Clio/Gmail connections only if a later build is authorized; non-sensitive matter reference, label naming rule and account owner. - Zapier Copilot authoring is documented on Free/Professional/Team/Enterprise, but app eligibility, premium requirements, task limits and the actual connected-account access still need checking. No account is connected here. - Preserve original evidence unchanged in restricted storage. Use synthetic material first. Prepare a separate, explicitly approved minimized AI input; aliases alone do not anonymize narrative or attachments. Do not upload raw originals or an alias key merely because another tab/file is sanitized. DATA ACQUISITION LIMITS - The verified source is a Zapier Clio New Matter > Gmail Create Label template, not a Make integration. It creates a label; it does not read, classify, file or label messages. - A template does not prove which matter identifier fields arrive in a real trigger or what happens on duplicate names/replay. Missing observed field/duplicate behavior is an implementation blocker. - No account login, connection, live test or publication is authorized by this recipe verification. WHEN THIS CAN RUN Blocked until actual sources, permissions and required human approvals are supplied; no real inputs were available in this verification. STEP 1: Read the actual two-step template and naming rule Tool: Zapier template page and owner-approved plan Open: Published Create Gmail labels from new Clio matters template Access needed: See recipe prerequisites; exact account entitlement and permissions not observed. Verify that the intended trigger is Clio New Matter and action is Gmail Create Label with Name of label. Obtain an approved non-sensitive matter reference/naming rule; do not use client names or allegations. Record unknown trigger-field mapping, connected-account ownership and duplicate-label policy. Expected output: Two-step mapping proposal and explicit missing-field/access questions. Use it next: Use synthetic placeholders and the approved naming rule in Zapier Copilot; no CSV export is required. Check: Do not substitute Updated Matter or New Contact; do not treat an invented sample payload as actual source data. Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns. Source documentation: https://zapier.com/apps/clio/integrations/gmail/269/create-gmail-labels-from-new-clio-matters STEP 2: Request a draft without automatic configuration Tool: Zapier Copilot Open: New Zap editor > Copilot prompt box > dropdown > Ask as you build > Start Building Access needed: See recipe prerequisites; exact account entitlement and permissions not observed. Use Ask as you build rather than default Auto-build. Paste the prompt and review suggestions before any configuration action. This documented route is a proposal for a later authorized user session; no Zap is created in this verification. PASTE THIS PROMPT Propose a NEW UNPUBLISHED two-step Zap using Ask as you build: Clio New Matter then Gmail Create Label. Use synthetic matter reference [REFERENCE] and approved non-sensitive label rule [RULE]. Ask before configuring each step. Show the exact selected trigger/action and Name of label mapping; mark unavailable or unobserved source fields and duplicate/replay behavior unknown. Do not use client names, allegations or case descriptions. Do not add email reading, sending, classification, deletion or filing. Do not connect accounts, request credentials, run a test or publish. Return a synthetic test plan and missing decisions for [ACCOUNT OWNER]. Expected output: Suggested unpublished trigger/action outline and unresolved setup questions. Use it next: Owner reviews the exact connections and Name of label mapping; keep the Zap unpublished and avoid Test step until an authorized synthetic test exists. Check: Copilot may select existing connections in other modes. Do not permit unreviewed actions or any real matter trigger payload. Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns. Source documentation: https://help.zapier.com/hc/en-us/articles/15703650952077-Use-the-power-of-AI-to-generate-Zap-workflows https://zapier.com/apps/clio/integrations/gmail/269/create-gmail-labels-from-new-clio-matters STEP 3: Review the exact input handoff for a future test Tool: Zapier editor and Gmail label list, human operated Open: Unpublished trigger/action field mapping; Gmail left panel label list Access needed: See recipe prerequisites; exact account entitlement and permissions not observed. After separate authorization, a future operator must inspect an actual authorized synthetic Clio trigger record, map its permitted reference into Name of label, and confirm the expected final name before any Gmail test action. Test actions can create real labels even while unpublished. For a manual one-off alternative, Gmail left panel More > Create new label is native, but clicking Create is a separate write. Expected output: Verified or blocked field-mapping/test specification. Use it next: Record the synthetic test result, replay behavior and exact account before asking for publication approval. Check: Creating a label is not email filing and does not confer confidentiality. Unknown duplicates block rollout. Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns. Source documentation: https://zapier.com/apps/clio/integrations/gmail/269/create-gmail-labels-from-new-clio-matters https://help.zapier.com/hc/en-us/articles/15703650952077-Use-the-power-of-AI-to-generate-Zap-workflows https://support.google.com/mail/answer/118708?hl=en STEP 4: Human review and final handoff Tool: Responsible staff reviewer and lawyer/process owner Open: Local reviewed report beside the frozen source set Access needed: See recipe prerequisites; exact account entitlement and permissions not observed. Account owner approves the bounded naming/data-sharing behavior, connections and synthetic outcomes before any recurring publication. Expected output: Unpublished reviewed plan or explicit setup blockers. Use it next: No live Zap or Gmail label has been created. Check: All unresolved or unreadable evidence stays open. No inferred approval or external action follows from AI output. Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns. Source documentation: https://help.zapier.com/hc/en-us/articles/15703650952077-Use-the-power-of-AI-to-generate-Zap-workflows ACCOUNT AND SOURCE CHECKS STILL NEEDED - Actual account access, source versions/completeness, privacy approval and reviewer sign-off were not observed. USING THE FILES IN THIS KIT Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs. The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.