You are helping me build the following AI agent workflow.

## Goal
Two-Way Property Repair Management System: Tenants submit repairs via form; system assigns a unique ID, emails managers.

## Specification
- What it does: Centralize tenant repair communication into a single spreadsheet so you can track every request from submission to completion. Automatically generate unique unit IDs for each issue and notify building managers with full details and links to submit updates. Save uploaded photos directly to organized folders while maintaining a complete history of all repairs in one place.
- Trigger: Triggered by an event (Event · on new repair request form submission)
- Autonomy: Fully hands-off
- Expected setup effort: about an afternoon
- Tools/services involved:
  - Google Sheets: centralize tenant communication and track repair history
  - Gmail: notify building managers of new requests and provide update links
  - Google Drive: store uploaded repair photos with consistent naming
  - Code: generate unique unit identifiers and merge data rows

## Known pitfalls, handle each one explicitly in your implementation
1. Unique Unit IDs might collide if multiple buildings share codes, add a timestamp suffix to ensure global uniqueness across all units.
2. Gmail attachments have size limits that could block high-res photos, compress images automatically before sending them via email.
3. Row deletion in Sheets can orphan linked Drive files, so maintain an audit log of deleted rows to prevent broken references.

## Reference implementation
https://n8n.io/workflows/10004 (workflow template)
Fetch and inspect this before building. If it matches my stack, adapt it;
if not, rebuild the pattern with my tools.

## Process requirements
1. Before building: ask me which of the listed tools I actually use and
   what my platform is (n8n / Make / code / other). Do not assume.
2. Adapt the pattern to my answers; do not force the reference stack.
3. Address every pitfall above; tell me how you handled each.
4. Provide a test plan I can run before letting this touch real data.
5. Ask before any step that sends messages, modifies data, or spends money.

Source: https://usecasesforagents.com/use-case/two-way-property-repair-management-system/ via usecasesforagents.com