START WITH THE PRODUCT STEPS
Read START-HERE.txt first. It states the actual source acquisition, access/privacy limits, manual field mapping and exact next prompt. The original file templates and synthetic examples below are supporting review aids. Some paths need separately supplied documents or source text; a blank worksheet is not a native export or completed integration.

Give each new matter an email label

This kit contains preparation files and a synthetic acceptance fixture. The adapted workflow remains untested.

START HERE
1. Complete input-preparation.txt and the editable setup file. Keep examples separate from real inputs.
2. Use the recipe prompt in its stated destination: Zapier Copilot.
3. Compare a synthetic pilot with the expected result. Check the original sources and your actual export schema.
4. Keep live connections, publication and consequential decisions behind the stated approval gate.

PREREQUISITES
- Zapier and access to Copilot for the prompt route; current plan and app access must be checked
- Approved Clio and Gmail connections owned by the firm
- A synthetic matter and a privacy-safe naming convention using a permitted reference rather than client names

REVIEW BOUNDARY
An account owner approves connected accounts, a non-sensitive naming convention, and synthetic test output before the Zap is published.

WHAT THESE FILES DO
A draft two-app Zap and setup decisions to review. It does not automatically classify existing messages.

The original recipe does not specify a rigid vendor CSV schema. Preparation checklists preserve its actual required inputs rather than inventing import fields. No real client, visitor or confidential data is included.