Overview
Flight Matrix provides RideSense for autonomous drone inspection of rides. The Flight Matrix page in Mobaro introduces a workflow for bringing inspection evidence into Mobaro and matching rides to Locations.
Use this guide to understand the current setup page and prepare the inspection workflow with your Customer Success Manager and Flight Matrix.
At a glance |
|
Who can do this | Super Users or a Role with Organization › Administrate; the Flight Matrix card must be enabled. |
Where | Configuration › Integrations › Flight Matrix |
Works on | Backend (web) |
Availability | Contact your CSM |
💡 Why this matters: Inspection evidence is most useful when your team knows which ride it belongs to, where to review it and who follows up on any findings.
Understand the integration
The Flight Matrix page describes RideSense flying a planned inspection path and returning labelled findings. The intended Mobaro workflow brings evidence from completed flights into inspection records for the relevant ride.
Confirm the exact evidence, record type and delivery process with Mobaro and Flight Matrix for your organization. The setup preview alone does not confirm that data is being transferred or that a particular report will be created.
Explore the setup page
1. Open Flight Matrix
In the Backend, open Configuration, select Integrations and choose Flight Matrix. Read the Information page. If the card is missing, contact your CSM to confirm access.
2. Read the connection requirements
Select Continue to open Integrate. The page shows an API key field for a RideSense key and a Test connection button. It also states that the key is not stored.
⚠️ Heads-up: The preview’s Test connection action is simulated. A success message here is not proof of a connection to Flight Matrix. Do not enter a production credential merely to try the preview.
3. Confirm the production setup
Ask your CSM and Flight Matrix for the supported connection process before using the integration operationally. Confirm who provides the credentials, which rides are included and how their records reach Mobaro. The preview’s Configure stage illustrates Location mapping; its example rides and selections are not a saved configuration.
Prepare your inspection workflow
Identify each ride’s existing Mobaro Location and agree the matching Flight Matrix reference.
Agree what inspection documentation should arrive and where your team will find it.
Name the person responsible for reviewing the evidence and arranging any follow-up work.
Arrange a representative test inspection and confirm that the expected evidence reaches the correct ride’s record.
Keep your existing inspection and review procedure in place until the agreed workflow has been tested. Receiving documentation is a separate step from deciding what action it requires.
Best practices
Start with one clearly identified ride and a representative inspection.
Check the evidence and its destination, rather than relying only on a connection message.
Record the agreed support contact for missing or unexpected data.
Frequently asked questions
What is a Location in Mobaro?
A Location is something you manage or inspect, such as a ride. It organizes related work and reporting. See the Locations overview before deciding how an inspection should be associated with a ride.
Why do I get a CORS error when calling the Mobaro API?
For a custom API workflow, make requests from your integration’s server rather than exposing an API key in browser code. See API access and limitations. This is separate from the Flight Matrix setup preview.
Why can I edit an Assignment but not its description?
An API-created Assignment can have its description marked read-only. Ask the integration owner whether that setting is intentional. See Assignment API fields. This does not mean Flight Matrix automatically creates Assignments.