Overview

This workflow responds to cellular data usage alerts for Android devices and apps managed in AirDroid Business. It gathers today’s usage, app rankings, recent daily trends, and same-group comparison data, then delivers a report and action form for the administrator. It fits a repeatable operating process for reviewing and handling recurring usage anomalies.

The Problem This Workflow Solves

Teams responsible for monitored Android devices need to review cellular data over-limit alerts, confirm which device or app triggered them, and decide whether to take no action, uninstall an app, shut down the device, or send a notification. The workflow collects the report details needed for that decision.

  • Faster context. The report brings device, app, trend, and group data into one review.
  • Clearer handoff. The email includes a form link that lets the administrator choose the next action.
  • Duplicate control. The workflow records repeat alerts and avoids sending another email inside the set interval.
  • Result follow-up. The workflow checks uninstall and shutdown status later and returns the outcome by email.

Who This Is For

  • Device monitoring teams. They review cellular data alerts and decide how to handle unusual usage on managed Android devices.
  • Administrators who receive alert mail. They review the investigation report and submit the next action for the triggered device.
  • Teams managing app usage. They use the app uninstall path when one app appears linked to the data spike.

What Sets This Workflow Apart

  • Device-based deduplication. The workflow stores notification state by device and suppresses repeat emails within the configured window.
  • Context before action. It compares the trigger with same-group devices before the administrator chooses a response.
  • Verified follow-up. It checks uninstall or shutdown status after a five-minute wait and emails the result.

How It Works

1
  1. Receive and screen the alert
  2. The workflow reads the cellular data alert, identifies the device, and checks whether the event is a duplicate.
2
  1. Collect usage context
  2. It refreshes monitoring data, gathers today’s device usage, reviews the last seven complete days, and compares same-group devices.
3
  1. Send the report and wait
  2. The workflow emails the investigation report and action form, then waits for the administrator’s choice for up to 24 hours.
4
  1. Run the selected action
  2. Depending on the form submission, it records no action, opens an app selection form, sends a shutdown, or sends a device notification.
5
  1. Check the result
  2. For app uninstall and shutdown, it waits five minutes, checks the current status once, and emails the result.

What You'll Need

  • Matching cellular data alerts
    • Device and app cellular data usage alerts must be created and linked to this workflow with daily limits.
  • Start parameters
    • Choose a report time zone, enter one administrator email address, and set the duplicate action email interval.
  • Authorized connections
    • Usable AirDroid Business and Gmail credentials are required for the report, notification, uninstall, and shutdown steps.
  • Supported scope and limits
    • Same-group investigation covers Android devices and can analyze up to 6,000 devices in one run.

How to Use

  1. Step 1. Set up the alerts
  2. Create the device and app cellular data usage alerts, choose daily limits, and connect them to this workflow.

  3. Step 2. Enter the run settings
  4. Select the report time zone, provide one administrator email address, and set the duplicate suppression interval.

  5. Step 3. Prepare access for execution
  6. Make sure the AirDroid Business and Gmail connections used by the workflow are authorized and available.

  7. Step 4. Review the report and act
  8. Open the emailed form, choose no action, uninstall app, emergency shutdown, or send notification to device, and submit your choice.

  9. Step 5. Continue for uninstall or shutdown
  10. If you choose uninstall or shutdown, wait for the later email that returns the queried execution status.

FAQs

What happens if the same device triggers another alert soon after the first one?
The workflow records the new event and does not send another action email within the configured interval.
Can the administrator handle the alert without taking device action?
Yes. The form includes a do not handle now choice that ends the workflow without sending a device operation.
What happens after an uninstall or shutdown command is sent?
The workflow waits five minutes, checks the current status once, and emails the result.
Are there limits on the same-group comparison?
Yes. The same-group investigation covers Android devices and analyzes up to 6,000 devices per run.
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 >
⚙️
Biz Daemon Permission Issue Handling
Biz Daemon permission alerts route device issues to administrators and on-site technicians for guided follow-up.
Learn more >