← All guides

I Built an AI Property Manager with Claude — Here's the One Rule That Makes It Safe

Why would you let AI email your tenants? Because it never sends before you say yes.

We built one AI agent (Claude, orchestrated by our own self-hosted n8n) that does three jobs property managers put off most, straight from the data in Property Manager Cloud.

The one rule

Reads your PM software → drafts the email → a person approves → then it sends. Every agent below follows it.

Job 1 — the monthly owner report

The agent reads four pages — payment history, balances due, open work orders, active leases — and writes one clean HTML email: big numbers first (collected, overdue, units leased, open work orders), then the detail. When rent is late, one "needs attention" line goes at the top. Nothing goes to the owner until someone clicks approve.

Job 2 — late rent

It keeps only rent that is actually late (not deposits, not charges that aren't due yet), checks whether the tenant was already reminded, and drafts a friendly reminder. A week later, a firmer one. After two, it stops and hands the case to a person. It never sends a legal notice.

Job 3 — lease renewals

It sweeps the leases page for upcoming end dates, asks the owner first (with a recommendation that applies your own rent cap), sends the tenant offer only after the owner says yes, and once the tenant agrees, creates the new lease in the software.

What none of the agents ever do

  • Raise rent past your cap
  • Send a legal notice
  • Contact a tenant without a yes from a person

Free templates for all three: comment AGENT on the video, or go to upnexs.com/agent.

▶ Watch all three run: https://youtu.be/oHWTfoycM24

Get one automation a week

The AI Back Office: what each automation does, the screens it reads, and the template.

Subscribe free