Your inbox has 67 unread messages. It's 9 AM. At least 40 of them are residents asking questions that are already answered in documents you've sent them three times.

"What are the pool hours?" "Can I paint my front door a different color?" "Who do I call about the broken sprinkler on Elm Court?" "My neighbor's truck is parked in a visitor spot for the third week. What do I do?"

If you're managing 10–20 HOAs, this is every morning. By the time you surface from the inbox, half the day is gone and none of the actual work — vendor coordination, board prep, financials — has started.

We built a workflow with n8n that handles 75–80% of these inquiries automatically. Not a chatbot. Not a portal nobody logs into. An automation that runs on email — exactly how residents already communicate — and closes the loop without the property manager touching it.

Here's exactly what we built and what it costs.

The Problem Is Structural, Not a People Problem

Property management firms run on email. Residents email. Vendors email. Boards email. And every message requires a human to read it, figure out what type of thing it is, and route it to the right action.

That routing decision — "is this a document question, a maintenance issue, a violation complaint, or something that actually needs me?" — takes 30 seconds to 2 minutes. Multiply by 150 incoming messages a month per association, across 15 associations, and you've got a 75-hour monthly routing tax. That's almost two full workweeks per month spent deciding what to do with messages instead of doing things.

The AppFolio 2026 Property Manager Benchmark Survey found that AI-adopting firms expect 31% portfolio growth versus 12% for non-adopters. The gap isn't tools — it's time. The firms growing are the ones who got that routing tax off their plate.

What We Built: The Intake Triage Workflow

The workflow has four lanes. Every incoming resident email goes through all four and gets routed to exactly one:

Lane 1: Document Questions (pool hours, architectural guidelines, CC&R rules, governing docs) These are 40–50% of all inbound. The workflow passes the email to Claude, which searches the association's governing documents (uploaded to the workflow once), drafts a direct answer with a citation to the relevant section, and sends the reply automatically. The property manager never sees it unless Claude flags uncertainty.

Lane 2: Maintenance Requests (broken fixtures, landscaping issues, common area problems) n8n creates a maintenance ticket in Notion (or Airtable — whichever you already use), routes the ticket to the relevant vendor based on category (plumbing, electrical, landscaping), sends the resident an auto-reply with their ticket number and expected response window, and pings the property manager in Slack with a summary. The PM reviews the vendor assignment, not the email.

Lane 3: Violation Reports (neighbor complaints, parking, noise, pets) The workflow creates a draft violation notice pre-populated with the resident's unit, the relevant CC&R section, and the complaint summary. It lands in the property manager's queue as a one-click approval, not a blank document to write from scratch. A notice that used to take 20 minutes to draft and send takes 90 seconds to review and approve.

Lane 4: Escalations (legal questions, disputes, anything requiring human judgment) Anything the classifier isn't confident about goes directly to the property manager with full context attached — the original email, the association it's from, and what category the AI estimated. No silent failures. No lost messages.

How to Build It

This runs on n8n — the automation platform we use daily at CloudBeast. Total setup time for a single association: 3–4 hours. You can replicate to additional associations in under an hour each once the template exists.

What You Need

• n8n (cloud or self-hosted; cloud is $20/month for this workload)
• Gmail or Outlook (wherever your HOA email lives)
• Claude Pro ($20/month) — you're using the API, not the chat interface
• The association's governing documents in PDF or text format
• A Notion database (or Airtable) for ticket tracking — the free tier handles this

Step 1: Gmail Webhook Trigger

In n8n, create a new workflow. The trigger is a Gmail node set to poll your property management inbox every 5 minutes. Filter to new messages. Route the sender, subject, and body to the next step.

One note: if you manage multiple HOAs from one inbox, add a label filter or subdomain catch-all so the workflow knows which association an email belongs to before classification.

Step 2: Claude Classifier Node

Pass the email body to Claude with this system prompt:

You are an HOA property management triage assistant. Classify this resident email into exactly one of these categories:
- DOCUMENT_QUESTION: Resident is asking about rules, policies, or information in governing documents
- MAINTENANCE_REQUEST: Resident is reporting a physical issue that needs repair or service
- VIOLATION_REPORT: Resident is reporting a neighbor for violating community rules
- ESCALATION: Anything involving legal threats, financial disputes, safety emergencies, or topics requiring property manager judgment

Return JSON: {"category": "CATEGORY", "confidence": 0.0-1.0, "summary": "one sentence"}

If confidence is below 0.75 on any category, route to ESCALATION regardless of the category guess.

Step 3: Route by Category

Add an n8n Switch node on the category field. Each branch handles one lane:

DOCUMENT_QUESTION branch: Pass the email to a second Claude call with this context:

You are the property manager for [Association Name]. Answer the resident's question using only the governing documents provided below. Include the exact section number your answer comes from.

Governing documents: [paste or file-read your CC&Rs, bylaws, rules]

Resident question: [email body]

Format your response as if you're the property manager replying to a resident email. Professional, direct, 3–5 sentences maximum.

Send the generated reply via Gmail. Log the exchange to a Notion database with the email, the response, and a "resolved automatically" status.

MAINTENANCE_REQUEST branch: Extract structured data from the email: issue description, location if mentioned, urgency indicators (words like "flooding," "no heat," "unsafe"). Create a Notion ticket with status "Open," category (mapped from keywords), and assigned vendor. Send the resident a Gmail reply:

Hi [First Name from email],

Your maintenance request has been received and logged as ticket #[ticket-id]. Our team will follow up within [24/48/72] hours.

Request summary: [one-sentence summary]

Thank you,
[Association Name] Property Management

Then send a Slack message to the PM channel: "New maintenance ticket: [summary]. Ticket #[id]. Vendor: [assigned vendor]. Review: [Notion link]."

VIOLATION_REPORT branch: Create a Google Doc or Notion page pre-populated with your standard violation notice template. Populate: resident's unit number (extracted from email or association records), relevant CC&R section (from a keyword lookup), and the complaint summary. Send to the PM queue as a Slack message: "Violation notice ready for review: [one-line summary]. Approve or edit: [link]."

ESCALATION branch: Forward the original email to the PM's direct inbox (not the shared HOA inbox) with a header: "⚠️ Escalation from [association name] — requires your review: [AI summary]."

Step 4: Error Handling

Add an n8n Error Trigger node. Any workflow failure sends a Slack message to the PM with the original email attached. Nothing disappears silently.

Step 5: Daily Digest

Add a scheduled trigger at 8 AM. It pulls the previous 24 hours of ticket data from Notion, counts by category, and posts a Slack message: "Yesterday: 12 inquiries. 9 auto-resolved (6 doc questions, 3 maintenance). 2 violations queued for your review. 1 escalation."

The PM knows what landed, what was handled, and what needs their attention — in one message, not 12 separate emails.

What This Changes

We deployed this for a property manager running 15 HOAs with about 2,200 total units. Before the workflow: 4+ hours daily in the inbox. After 60 days:

• Auto-resolution rate for document questions: 84%
• Maintenance tickets logged with zero manual entry: 100%
• Average PM time on inbox triage: 38 minutes per day
• Violation notices drafted versus written from scratch: 19 of 21 in the first month

The 38 minutes isn't zero. The PM still reviews the escalation queue, approves violation notices, and spot-checks auto-replies on complex doc questions. But 38 minutes versus 4 hours is the difference between a sustainable day and a buried one.

The Architecture Note

This workflow is the quick win. It works for a single-tool setup — you don't need anything else running to get value on day one.

But when you're ready to connect this to your AppFolio or Buildium database for resident verification, route tickets through your existing vendor management system, and build the monthly board report from your ticket data — that's where architecture matters. The workflow you built today becomes one component of a system instead of a standalone automation.

That's the conversation we have at the strategy tier. If you want to start there, we'll map your full stack and show you what connects before you build anything.

Book a discovery call at cloudbeast.io/schedule.