Anyone using Claude Cowork with AppFolio's Realm-X connector?
Technology · Santa Cruz, CA · Member since 2025 · 17 posts · 1 vote
AppFolio's API has always been the wall for getting anything in or out. The reports API is read only, and writing anything back, like a work order status or a note, takes the Max plan or a paid add-on plus AppFolio's approval.
The Realm-X connector for Claude looks like a way around that. With it and Claude Cowork, Claude can sit between AppFolio and your other tools. You connect both to the same Claude account and ask it to do the work in between. For example, pull the open work orders from AppFolio, compare them to what your maintenance team logged, and close out the ones that are done. From what AppFolio published, Core plans can read, and Plus and Max can also write, with you approving each change.
I'm early in testing this, so I'd like to hear from anyone already doing it. What do you have Claude doing in AppFolio day to day? Does Realm-X make changes for you (work orders, notes, bills), or is it mostly reading and reporting? Do you have anything that runs on a schedule, or do you type each request? And where did it fall short?
Stephen, I run a small single-family PM shop in Scottsdale and use Jira for operations. One workflow I already run on a schedule is quarterly owner reporting. The AI pulls from the property records and drafts the reports. I review them before they go out.
Your work-order example is the one I’d try next. I’d want a scheduled run that shows me which jobs the maintenance team marked complete, what evidence it found for each, and which AppFolio work orders it proposes closing. Then I’d approve the batch and get back to work.
Have you been able to get Cowork to tee up that whole batch for one review, or are you still prompting it and approving changes one at a time? That’s the difference I’d feel running the shop solo.
AppFolio's API has always been the wall for getting anything in or out. The reports API is read only, and writing anything back, like a work order status or a note, takes the Max plan or a paid add-on plus AppFolio's approval.
The Realm-X connector for Claude looks like a way around that. With it and Claude Cowork, Claude can sit between AppFolio and your other tools. You connect both to the same Claude account and ask it to do the work in between. For example, pull the open work orders from AppFolio, compare them to what your maintenance team logged, and close out the ones that are done. From what AppFolio published, Core plans can read, and Plus and Max can also write, with you approving each change.
I'm early in testing this, so I'd like to hear from anyone already doing it. What do you have Claude doing in AppFolio day to day? Does Realm-X make changes for you (work orders, notes, bills), or is it mostly reading and reporting? Do you have anything that runs on a schedule, or do you type each request? And where did it fall short?
@Stephen Schroeder, I haven't used this particular setup, so I can't speak to how well it works. But I can see the value in using it to organize maintenance requests and reports. I'd be especially careful with automatically closing work orders and would want someone to confirm the repairs were actually completed first.
In my experience as a real estate attorney in Maryland, I've worked with landlords on rental and property related matters where keeping accurate maintenance records is important. For example, if a tenant later questions whether a repair was completed, having clear records of the work and when it was done can help resolve the issue.
I appreciate you sharing this, @Stephen Schroeder! It's interesting to see how technology is changing property management. This connects closely to the documentation and landlord responsibilities I deal with in my work. Happy to stay connected!
Stephen, I run a small single-family PM shop in Scottsdale and use Jira for operations. One workflow I already run on a schedule is quarterly owner reporting. The AI pulls from the property records and drafts the reports. I review them before they go out.
Your work-order example is the one I’d try next. I’d want a scheduled run that shows me which jobs the maintenance team marked complete, what evidence it found for each, and which AppFolio work orders it proposes closing. Then I’d approve the batch and get back to work.
Have you been able to get Cowork to tee up that whole batch for one review, or are you still prompting it and approving changes one at a time? That’s the difference I’d feel running the shop solo.
@Alik Levin are you using anything outside of AppFolio now for tracking work?
Hey @Stephen Schroeder,
I haven't used this exact setup, so I can't tell you how it behaves inside your property software. But having automated most of the daily work in our own businesses, I can share what's held up for us, and I think it touches a couple of your questions.
The jobs that run on a schedule are the ones that stuck. Typing each request is fine while you're testing, but the real time savings came once the work showed up on its own, ready for us to look over. For us that's a short daily brief of what needs a decision, waiting before anyone sits down.
On reading versus making changes, I'd let it do the reading and matching for a while before it writes anything back. Your work order example is a great one for that. Comparing what's open against what the maintenance team logged is slow, tedious work for a person, and a system is really good at spotting the job that was marked done with no photo or invoice behind it.
If I were in your shoes today, I'd set it up close to what Alik described: one scheduled run that lists every work order it thinks can be closed, with the evidence it found for each, so you can approve the whole batch in one sitting. I'd put anything with missing evidence on its own short list for a person to check, which also covers Diana's point about confirming the repair was actually done.
Best of luck with the testing,
Lee
Since the Realm-X addition for many of us is new, the only thing I'm currently using Claude with it for is pulling reports and double checking tasks - did all guest cards get followed up on and how quickly, did all of the extensions get sent out on time, etc. I'm looking forward to seeing what people can have it do though and am excited at the possibilities!
One practical detail if you schedule this in Cowork: a scheduled run can stall when it hits an approval prompt, since nobody is there to click it. So keep the scheduled part read-only. Have it pull open work orders, match them against the maintenance log, and write a proposed-closure list with the evidence for each (photo, invoice, tech note) into a sheet. Then do the write-back while you’re at the desk, only on the rows you marked approved.
Two things that help the matching: match on unit plus a date window plus vendor, not on description text, and keep a separate list of anything it couldn’t match. That unmatched list is usually where the real problems are, like jobs finished but never invoiced.
I own a 5-unit and a rental house, and I build workflows like this for small businesses.