AI condition inspection for MagicDoor

Overview

In MagicDoor, photos belong to a job. RapidEye makes them belong to a unit. Every tenant report becomes a structured request with a category, an urgency and attached photos; converted to a work order, it carries scope, vendor, urgency, photos, chat and invoice on one record, and the vendor uploads more from the field. That record is excellent at answering what happened on this job. It was never built to answer what this unit looked like in March, or what changed between one tenancy and the next. RapidEye reads those same photos alongside the unit and the lease dates and returns a running condition record: what is new, what the scope said would be fixed and is not visible, what is missing from the room. Nothing in MagicDoor is written to or changed.

How it works with MagicDoor

MagicDoor already routes a photo through several hands before a job closes. The integration reads at each of those points rather than adding one of its own.

• The tenant's photos on the request. Requests arrive from the portal, SMS, chat or email and land with a category, an urgency and images attached. RapidEye reads them for what the tenant did not report: the ceiling stain under the leak they did report, the second burner that is also dead, the mould running past the edge of the crop. A finding here means a second work order goes out on the same visit instead of two weeks later.
• The vendor's photos during and after the work. The vendor portal takes status, photos and notes from the property, and photo uploads happen both during and after. RapidEye reads the closing images against the room's own history, so a patch painted the wrong colour, a blind still hanging crooked or a filter that was never actually swapped comes back named and located.
• Group work orders. Building-wide pest, paint or similar, with individual unit work orders under a group and a roll-up status. This is where sampling normally happens, because nobody opens forty sets of photos. RapidEye opens all forty and tells you which three units the crew did badly.
• Move-in and move-out. MagicDoor has no inspection record, so this is the one place the photos do not exist yet. A RapidEye capture link goes to whoever walks the unit, opens in a phone browser with nothing to install, and asks for a fixed set of angles per room. Those become the unit's baseline, and every later request photo is read against it.

Each finding names the property and unit, the room, the spot, the kind of problem, how serious, the pair of photos and the dates between them, plus a suggested next step. Each one arrives in the RapidEye dashboard, and can be mirrored to Slack or email. Whether it becomes a work order in MagicDoor is yours to decide. And photos are not the only input: teams that film walkthroughs, hold Matterport scans, or want findings scored against their own condition report get that set up with us on the first call.

How to connect MagicDoor to RapidEye

1. Your units and leases, already in MagicDoor. RapidEye keys its record to the unit, so a unit that exists in MagicDoor is a unit it can hold a baseline for. Portfolios, properties and units all carry through.
2. Where the photos come from. Images already on requests and work orders are read as they are, and nobody changes how they work. For move-in and move-out a capture link fills the gap, since there is no inspection object to attach to.
3. Add RapidEye as a property manager. Users, then Property Managers, then Add property manager. The modal has the name, the email and the two access settings MagicDoor makes you set separately.

Your tenants keep messaging the way they message, your vendors keep working in their own portal, and the first findings arrive with the first photos.

Where photos live in MagicDoor, and what they are attached to

Checked against MagicDoor's help centre and feature pages, September 2026.

MagicDoor is an AI-native residential property management platform, and its maintenance side is built as two linked objects rather than one. According to MagicDoor's help centre documentation (magicdoor.com), a maintenance request is created from Maintenance, then Maintenance Requests, then Add Maintenance Request, and the form asks for a description, any relevant photos or documents, a Priority, and a Category, with the note that categories are what let the AI set a score and determine urgency. When that request becomes a work order, the two stay linked, the work order runs its own vendor or group chat context, and you can navigate back to the original request to read its conversation and history. The practical consequence is that a unit's photographic history is scattered across two record types and however many jobs it has had.

From there the vendor drives the work order through four statuses in their own portal.

Statuses as documented by MagicDoor. The last line of each is where RapidEye reads.

What each part of a work order can tell you on its own

MagicDoor puts scope, vendor, urgency, photos, chat and invoice on one record. They answer different questions, and only one of them is a record of the property itself.

Does MagicDoor have move-in and move-out inspections?

No inspection object exists. MagicDoor's own sitemap and help centre run to leases, tenants, vendors, work orders, bills, banking, reports, AI runbooks and permissions, and none of them describe an inspection, an inspection template or a condition report. The word appears once in the product pages as an example of a group work order, which is a job you dispatch, not a record of what a unit looked like. So the condition history exists in MagicDoor only as a by-product: the photos are there, spread across requests and work orders, tied to whichever job happened to produce them.

The platform does compare images in one place. When AI is on for a work order, the documented steps include photo comparison at completion, before against after, so a routine job can close itself without a coordinator opening it, and when a tenant disputes completion the chat history and that comparison are delivered to the PM. That is a good check on one job, and it is bounded by one job: two images, one visit, one scope. RapidEye works the other axis. It holds every photo of that unit as one running record against the room's own last known state, which is what a move-out deduction, an owner report and a claim against a vendor all actually need. The two are complementary, and neither one is doing the other's job.

MagicDoor integration FAQ