Overview

This workflow checks one device group for offline, low battery, low storage, and configuration anomalies, then compiles the results into an online Excel summary. It suits repeatable operational checks where teams need a consistent report, a shareable link, and a clear run result for follow-up.

The Problem This Workflow Solves

Teams responsible for monitored devices often need to review one group, confirm which anomaly types matter, and decide whether any devices need follow-up. They also need a summary they can share quickly, with thresholds, counts, and a clear result that shows whether the query and export completed.

  • Group-level view. The workflow gathers anomaly counts for one selected group instead of forcing separate checks.
  • Clear follow-up link. It sends an online Excel link so recipients can open the summary directly.
  • Consistent thresholds. It applies the same configured limits when checking offline, battery, and storage conditions.
  • Readable outcome. It returns a run result and error message when a step does not complete.

Who This Is For

  • Device operations teams. They check one group for anomalies and share the summary with other stakeholders.
  • Store or regional inspection routines. They use the workflow for recurring group reviews and follow-up reporting.
  • Teams managing alert thresholds. They compare offline, battery, and storage conditions against chosen limits.

What Sets This Workflow Apart

  • Recipient validation. The workflow stops early if no valid email address is provided.
  • Group confirmation. It checks whether the entered group name matches an accessible group before querying devices.
  • Deduplicated anomaly count. It counts anomaly devices once per device ID, even if multiple conditions apply.
  • Query failure return. It preserves query error information and a retryable flag when device search fails.

How It Works

1
  1. Validate input and recipients
  2. The workflow checks the group name, anomaly types, thresholds, and recipient emails before it starts any device query.
2
  1. Resolve the target group
  2. It confirms the group exists and is accessible, then prepares the query state for the selected device group.
3
  1. Query devices in pages
  2. The workflow reads devices page by page, applies the selected anomaly rules, and keeps a running summary.
4
  1. Build and send the report
  2. It formats the summary, writes an online Excel file, creates a read-only link, and emails the link.
5
  1. Return the run result
  2. The workflow returns execution status, counts, workbook details, or an error message when a step fails.

What You'll Need

  • AirDroid Business access and a valid device group
    • You need authorized AirDroid Business credentials, and the group name must exactly match the console entry.
  • Email and file-sharing connections
    • You need Outlook, Microsoft Excel, and Microsoft OneDrive credentials, and Excel and OneDrive must use the same account.
  • Run inputs and display settings
    • You must enter recipient emails, choose at least one anomaly type, set matching thresholds, and select a time zone.

How to Use

  1. Step 1. Prepare the connected services
  2. Connect the required AirDroid Business, Excel, OneDrive, and Outlook accounts before you run the template.

  3. Step 2. Enter the run details
  4. Provide the device group name, recipient addresses, anomaly types, thresholds, and display time zone.

  5. Step 3. Run and review the result
  6. Start the workflow and review the returned status, error message, counts, and workbook link if the run succeeds.

FAQs

What happens if the recipient email list is invalid?
The workflow stops before the device query starts. It returns an invalid recipient result and lists the invalid addresses.
How are configuration anomalies identified?
They are matched against the console statuses Policy & Kiosk not applied, Policy ineffective, and Kiosk ineffective.
What if the selected group cannot be resolved?
The workflow ends with a group not found or group resolution failed result and does not continue to the query stage.
Does the summary count a device more than once?
No. The final anomaly total is deduplicated by device ID, even if one device matches multiple anomaly types.
Was This Page Helpful?

More Workflows for Inspiration

🔧
AirDroid Business Alert and Automation Result Notification to Microsoft Teams
Send AirDroid Business alerts and automation results to Microsoft Teams with clear event details and timestamps.
Learn more >
📊
Offline device query and export
Find devices that have stayed offline beyond a set number of days and export the list to Excel.
Learn more >
📊
Cellular Data Usage Alert Report
Checks cellular data over-limit alerts, reports usage context, and routes the admin's chosen response.
Learn more >