This guide explains how to send Property Inspect actions to MRI Property Management X (PMX) as service requests.
When enabled, actions raised during an inspection can be synced to PMX when the inspection is completed or closed, depending on your selected settings.
You can also map actions to PMX work order types and sub types, helping service requests appear in PMX with the correct categorisation.
Looking for another MRI PMX guide?
This guide is part of our MRI PMX collection. You may also find these helpful:
Before You Start
Before sending actions to PMX as service requests, make sure:
Your PMX integration is connected.
Your PMX properties have been synced.
The relevant buildings, units, or suites have imported into Property Inspect.
The inspection is being carried out on a PMX-linked property record.
Your action settings have been reviewed.
You can find your PMX integration settings by going to:
Settings > Integrations > MRI Property Management X
⚠️ Important: Only actions added to inspections carried out on properties, buildings, units, or suites imported from PMX will sync to PMX.
How Actions Sync To PMX
When action syncing is enabled, actions added to an inspection in Property Inspect can be sent to PMX as service requests.
The action will sync when the inspection reaches the trigger selected in your PMX integration settings.
For example, you can choose to send actions when the inspection is:
Completed
Closed
This allows your team to control when service requests are created in PMX.
Configure Create Service Requests
The Create Service Requests setting controls whether actions should sync to PMX and when they should be sent.
To configure this setting:
Go to Settings.
Select Integrations.
Scroll to MRI Property Management X.
Find Inspection Update Settings.
Go to Create Service Requests.
Choose the trigger you want to use.
Save your changes.
The available options may include:
Option | What It Means |
Off | Actions will not be sent to PMX as service requests. |
On Complete | Actions will be sent when the inspection is completed. |
On Closed | Actions will be sent when the inspection is closed. |
💡 Tip: Choose the trigger that best matches your internal workflow. If your team reviews reports before closing them, you may prefer to send service requests only once the inspection is closed.
Configure Work Order Types And Sub Types
You can map Property Inspect actions to PMX work order types and sub types.
This helps categorise the service requests created in PMX.
In Property Inspect:
Request Source = PMX Work Order Type
Category = PMX Work Order Sub Type
These fields are optional, but they are useful if your PMX team needs service requests to be grouped by type or category.
To configure these:
Go to Settings.
Select Actions.
Open the action you want to configure.
Find the PMX work order fields.
Select the relevant Request Source and Category.
Save your changes.
ℹ️ If an action syncs without a work order type or sub type selected, Property Inspect will use a default fallback so that the service request can still be created.
Refresh Work Order Types
If the expected PMX work order types or sub types are not showing, you may need to refresh the list from your PMX integration settings.
To refresh work order types:
Go to Settings.
Select Integrations.
Scroll to MRI Property Management X.
Select Configure Work Order Types.
Click Refresh Work Order Types.
Return to Settings > Actions and check the available options again.
Where Service Requests Are Created In PMX
When actions are successfully synced, they will appear in PMX under Manage Service Requests.
Opening the service request in PMX will show more information about the action, such as:
Request details
Special instructions
Action notes
Category
Property, building, or unit information
Resident or contact details, where available
Residential Service Requests
For Residential Management records, the type of service request created depends on the level of the inspection.
Inspection Level | PMX Service Request Type |
Unit | Resident Request |
Building | Non-Resident Request |
Where possible, we recommend conducting inspections on imported units rather than buildings.
This is because unit-level service requests are more specific and make it easier to find the associated resident details in PMX.
📈 Recommended Approach: If the work relates to an individual resident or unit, carry out the inspection on the imported unit rather than the wider building.
Building-Level Fallback
If Property Inspect cannot create a residential service request at unit level, the service request may be created at building level instead.
This may happen if:
The inspection was carried out on a building instead of a unit.
A unit-level service request cannot be created.
There is an issue with the unit-level PMX link.
This fallback helps make sure the work is still logged in PMX, even if the more specific unit-level request cannot be created.
What Information Is Sent To PMX
When an action is sent to PMX as a service request, Property Inspect sends relevant action details to help the PMX user understand the issue.
This may include:
PMX Field | Information Sent From Property Inspect |
Request Title | The action name and location details. |
Special Instructions | Details such as location, responsibility, due date, or cost, where available. |
Action Notes | Action comments, notes, inspection details, and traceability information. |
Priority | The closest matching priority from the Property Inspect action. |
Status | Whether the action is scheduled or completed. |
Request Source | The selected PMX work order type. |
Category | The selected PMX work order sub type. |
ℹ️ This helps the service request created in PMX contain enough context for the next team to review and action it.
What To Check If Actions Do Not Sync To PMX
If actions are not syncing to PMX as service requests, check the following:
What To Check | Why It Matters |
PMX is connected | Service request syncing requires an active PMX connection. |
Properties have been synced | The inspection must be carried out on a PMX-linked property record. |
Create Service Requests is enabled | Actions will not sync if this setting is off. |
The correct trigger has been selected | Actions sync when the inspection reaches the selected trigger, such as completed or closed. |
The inspection has reached the trigger | If the inspection is still in progress, actions may not have synced yet. |
Actions were added to the inspection | Only actions raised on the inspection can be sent as service requests. |
The inspection is on an imported PMX record | Actions from non-PMX properties will not sync to PMX. |
Work order types have been refreshed | If categories are missing, refresh the PMX work order types. |
Recommended Setup Flow
For the best results, set up PMX service request syncing in this order:
Connect the PMX integration.
Configure property sync settings.
Sync PMX properties.
Confirm the relevant buildings, units, or suites exist in Property Inspect.
Configure Create Service Requests.
Refresh PMX work order types, if needed.
Configure action-level Request Source and Category fields.
Conduct the inspection on a PMX-linked property, building, unit, or suite.
Add actions during the inspection.
Complete or close the inspection, depending on your selected trigger.
Review the created service request in PMX.
What To Do Next
Once your action and service request settings are configured, you may also want to review:
MRI PMX: Inspection Sync and Report Updates
Manage inspection imports, report links, and status updates.MRI PMX: Contact Import Settings
Control which PMX contacts import and how they are used in Property Inspect.MRI PMX: Property Sync Settings
Review which PMX property levels and property types should import.
Need Help?
If actions are not syncing to PMX as expected, contact Property Inspect Support and include:
The Property Inspect inspection ID or URL
The PMX property, building, unit, or suite linked to the inspection
The action name or action ID
Your selected Create Service Requests setting
The selected Request Source and Category, if configured
A screenshot of the PMX integration settings
A screenshot of the action settings
Any error message shown in Property Inspect or PMX