Overview
Mobaro has a connector in Microsoft Power Automate (the online version) that lets your flows read and update your Mobaro data — for example, sending yesterday's Checklist Results to Excel or SharePoint, posting new Assignments to Teams, or keeping Users in step with another system. There's nothing to install: search for Mobaro when you add an action to a flow.
The connector is built on the Mobaro API. Each connector action is one API operation and it signs in with a Mobaro API key, so the connector can't do anything the API can't.
At a glance |
|
Who can do this | Anyone with a Premium Power Automate license and a Mobaro API key. Users with Organization › Administrate create API keys. |
Where | Power Automate › add an action › search Mobaro. API keys: Configuration › API › API Keys |
Works on | Public API, through Power Automate |
Availability | API access is enabled per organization by Mobaro — ask your CSM |
🛑 Critical: Microsoft classifies the Mobaro connector as Premium, so everyone who builds or runs a flow with it needs a Premium Power Automate license. Mobaro doesn't control this classification.
What the connector can do
The connector's actions have the same names as the Mobaro API operations, such as List all results, Create an assignment or Update a user. In summary:
Read — Results, Checklists, Schedules and schedule slots, Calendars, Assignments, Assets, Locations and Location Groups, Users, User Groups and Roles, Competencies and Certifications, Timesheet entries, Downtimes, Notes, files and RideOps data.
Create — Assignments, Assets, Users, User Groups, Locations, Location Groups, Competencies, Certifications, Downtimes, Timesheet entries and ad-hoc schedule slots.
Update — most of the records you can create, plus Roles. Results can be approved, disapproved or moved to another Location or Asset; a Checklist's categories and folders can be changed.
Delete — Assignments, Assets, Users, User Groups, Roles, Locations, Location Groups, Competencies, Certifications, Downtimes, Timesheet entries and ad-hoc schedule slots.
The connector can't do what the API can't: it can't create Checklists or edit their questions, complete a Checklist, create or change Notes, create Schedules or delete Results. For every operation and its filters, see the Mobaro API parameter reference.
Get an API key
A User with Organization › Administrate creates the key under Configuration › API › API Keys. Keys are Read-only by default, which is enough for flows that only read data. Actions that create, update or delete fail with a read-only key, so untick Read-only only for flows that must write. If Mobaro has enabled read-only API access for your organization, the box can't be unticked. The key is shown once, so copy it straight away. See Creating and Managing API Keys.
⚠️ Heads-up: An API key has Super User-level access to your organization's data, whoever created it. Treat it like an administrator password: never paste it into a flow step or share it in email or chat. See Understanding API access scopes and limitations.
Build your first flow
1. Sign in to Power Automate
Go to make.powerautomate.com and sign in with your Microsoft account.
2. Create a flow
Click Create and choose the kind of flow you need, for example an Instant cloud flow that you run by hand, or a scheduled flow that runs every morning.
3. Add a Mobaro action
Add a step, search for Mobaro and choose an action, for example List all results.
4. Connect with your API key
The first time you use a Mobaro action, Power Automate asks you to create a connection. Enter your Mobaro API key.
5. Test and refine
Run the flow, check the output, then add filters, conditions and the steps that send the data where you need it — Excel, SharePoint, Teams or email. For a complete worked example, see How to schedule daily exports from Mobaro using Power Automate.
Best practices
Filter large data sets. On List all results, use AnsweredAfter and AnsweredBefore to fetch only the period you need, and page through with Limit (up to 20 per call) and Offset.
Use a Read-only key unless the flow must write, and give each flow or integration its own key so you can delete one without breaking others.
Stay within the API's rate limit of 10 requests per second per key (creating, updating or deleting Users and Location Groups is limited further): add a delay inside loops that call Mobaro for many records.
Test a flow that updates or deletes data on a few records first.
Frequently asked questions
How do I get access, and what credentials do I use?
You connect with a Mobaro API key from Configuration › API › API Keys. If there's no API tab, or no API Keys table on it, API access isn't enabled for your organization yet — ask your CSM. You also need Organization › Administrate to create a key.
Where can I find documentation on the Mobaro connector's actions?
Each action matches a Mobaro API operation of the same name, so the API documentation applies. See the Mobaro API parameter reference and Getting started with the Mobaro API.
Can I fill out a checklist or form through the Power Automate connection?
No. Checklists are completed in the Mobaro app or Backend. The connector can read the Results afterwards, approve or disapprove them, and create Assignments, Downtimes and other records.
Can the connector create checklists or delete results?
No. The Mobaro API has no operations to create Checklists or delete Results, so neither does the connector. It can change a Checklist's categories and folders, and approve or disapprove Results.