Resources · Claude connector

Claude AppFolio Realm-X connectorWhat Claude can do in your AppFolio Realm-X account.

The Claude AppFolio Realm-X connector exposes 1 tool. 0 only read, 1 can change data, 0 are left undocumented. That single tool hands your request to Realm-X, AppFolio's own assistant. Below: what it reaches, the confirmation card, and the admin switch.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes once Claude can talk to Realm-X

You ask Claude a question about your portfolio, and Claude passes it to Realm-X, the assistant built into AppFolio, which works agent to agent and can carry a multi-step job through. You get answers from live data, reports, and drafted changes that wait for your click. AppFolio's own advice: daily work inside one AppFolio screen still belongs in AppFolio.

Go past a single screen. AppFolio's description promises data analysis, reports and presentations built from your portfolio, and multi-step processes that Realm-X carries from prompt to completion. Claude reaches all of it through chat.

Run a report from the chat. The permission screen AppFolio describes covers running reports and looking up records on your behalf, so a question about one portfolio gets its answer without a trip to the AppFolio menus.

Prepare an action and approve it. Ask for a maintenance work order for a leaking water heater: Claude drafts it, and AppFolio shows a confirmation card before anything is submitted.

What it will not do: reach a property, resident or ledger outside your own AppFolio rights, switch company databases mid-session, or act on its own when a lease or ticket changes. Claude works only while it answers you. The Integrations hub lists the other apps we cover.

Vocabulary

Five words to know first

The vocabulary you will meet around this connector.

Connector
The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
Tool
One named thing a connector lets Claude do. Claude picks what it needs by itself, and the directory lists each tool by name.
Authorization
The AppFolio sign-in and permission screen where you hand Claude its access. Given once per person, and you can withdraw it.
Approval
The confirmation Claude waits for before changing your account. With AppFolio, it shows up as a card in the conversation.
MCP
The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as AppFolio.
Connect

Connect AppFolio Realm-X to Claude in three steps

  1. 01

    Find AppFolio in Claude

    Open Claude's settings, go to Customize then Connectors, and look for AppFolio Realm-X. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it before members can each sign in.

  2. 02

    Sign in on AppFolio's side

    Click Connect, then sign in through the window AppFolio opens. AppFolio asks you to pick the company database Claude will use; reconnect later to switch. If the link breaks, Disconnect and connect again.

  3. 03

    Read the permission screen

    AppFolio lists what Claude may do on your behalf: chatting with Realm-X, running reports, looking up records, drafting actions for you to confirm. That screen belongs to AppFolio, not Claude. Accept only if it matches what you expect.

Tools

The one tool, and what goes through it

AppFolio Realm-X gives Claude 1 tool: 0 that read your account, 1 that change something in it.

A single tool carries everything, reading and writing alike, so the directory files it with tools that change data. AppFolio documents what it does, and the name stays exactly as Claude shows it.

  • 1 write

What Claude can change (1)

1 tool

One tool that questions your AppFolio data and runs Realm-X tasks, including changes you confirm.

chat

Asks you first

Opens a conversation with Realm-X so Claude can question your AppFolio data, pull reports, look up records and run tasks, all inside your chat. Changes such as a work order or a notice come back to you as drafts first.

What Claude asks for
AppFolio shows a confirmation card for any action that changes data, and nothing is submitted until you approve it.
When it helps
you need last month's delinquency report for one portfolio.
Watch out
Claude sees only what your AppFolio role allows.

Sourceknowledge.appfolio.com · October 1, 2026 ↗

Approvals

What Claude checks with you first

By default, Claude asks before each action it takes on an account for someone. AppFolio documents its own layer on top: a confirmation card for every drafted change, plus an Allow prompt when the skill starts.

On Team and Enterprise workspaces, owners decide whether a member may let some actions through without a prompt each time. They can also cap what a connector does for the whole organization, for example keeping lookups open and closing changes, and nobody gets around that from a personal account. Claude works with the identity and rights of the person who connected. Claude inherits your AppFolio permissions, and AppFolio logs all connector activity for audit.

Plans

Which plans include it

None of the 819 sheets in the official directory shows which Claude plans carry a connector. Per connector, that answer is published nowhere.

The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization first. Check the AppFolio Realm-X sheet in the official directory for its live state. Only AppFolio documents this connector; no Claude help page covers it.

Limits

Where this connector stops

A connector is not an automation. Claude calls the tool while it answers you, so nothing runs when a lease ends or a work order comes in.

On the AppFolio side, the publisher asks for an active Property Manager account, and your AppFolio subscription tier decides how far Claude goes: AppFolio says customers on its Core plan get read access only, while the two other tiers its guide names allow read and write. The directory's partner badge is not a security audit, and Anthropic states on every sheet that it neither picks a publisher's tools nor guarantees how they behave. Connect what comes from a publisher you know. For a connector built on several separate tools, compare with the Claude adobe-workfront connector page.

Need help

Need help connecting AppFolio Realm-X to Claude?

A person reads every message.

FAQ

Questions about the Claude AppFolio Realm-X connector

01What can Claude do with the AppFolio Realm-X connector?
Claude can question your AppFolio data and run Realm-X tasks from the conversation. Its one tool, chat, passes your request to Realm-X, which can run reports, look up records and prepare actions across leasing, maintenance, accounting and communications. AppFolio's description also mentions data analysis, reports and presentations, while its guide keeps day-to-day work inside one AppFolio workflow in AppFolio itself. Anything that changes data comes back as a confirmation card before it is submitted.
02Can Claude create work orders or send notices in AppFolio?
Drafting them is part of what it does. AppFolio's own examples include creating a work order and sending a notice. Before anything is submitted, AppFolio shows a confirmation card in the conversation, and nothing goes out until you approve it. Write access itself also depends on your AppFolio subscription: the publisher says customers on its Core plan get read access only. Your AppFolio role sets the rest of the limits.
03Does Claude ask before it changes anything?
By default, every change waits for you. Claude's rule is to ask before each action it takes on an account for someone, and AppFolio adds a confirmation card for every drafted change. When you start the skill by typing /chat, you also choose between allowing it for this task only or for all tasks. On Team and Enterprise workspaces, owners decide whether members may let some actions pass without being asked each time.
04Which Claude plans is the AppFolio connector available on?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. The general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner enabling them first on Team and Enterprise. AppFolio's guide names no Claude plan. Its own subscription tiers matter separately, and the directory sheet shows the connector's live state.
05Does Claude see our whole AppFolio portfolio?
No, only what you can already see. AppFolio states that Claude inherits the permissions of the user who connected: a report you cannot see in AppFolio stays out of Claude's reach too. Claude is also tied to the one company database you picked when connecting, and AppFolio logs all connector activity for audit. If your organization restricts third-party connectors, AppFolio adds that you also need your administrator's permission before connecting.
06How do I switch Claude to another AppFolio company?
You reconnect. AppFolio has you choose one company database during sign-in, and that is the one Claude works with. If the wrong company appears, its guide says to disconnect the connector from Claude's connector settings, connect again, and pick the right company on the selection screen. If you have access to several AppFolio companies, pick the one this Claude session should use at that prompt. Reconnecting is the only route the guide describes.
07Claude or an automation tool for AppFolio?
They do different jobs, so this is not a ranking. Claude with this connector is for questions, analysis and one-off actions you confirm in a conversation, such as a delinquency report or a retention memo. An automation tool runs a scenario by itself when something happens. The AppFolio tool never fires on its own when a lease ends or a ticket arrives, so a recurring routine belongs to an automation platform.