Overview
This workflow inspects Android devices for Biz Daemon version and selected permissions, then sends the findings by email. When devices need follow-up, it creates an Excel report and can share a read-only link. It fits recurring device inspection as a repeatable workflow step.
The Problem This Workflow Solves
Teams responsible for managed Android devices need a clear way to confirm whether Biz Daemon is current and required permissions are enabled. They also need to know which devices need follow-up, which names were not found in a custom scope, and whether results should be reviewed through email or Excel.
- Faster follow-up. The email highlights devices that need attention, so the team can act without manual sorting.
- Clearer checks. The workflow separates version, permission, and unreadable-status results for easier review.
- Defined handoff. The Excel report and read-only link give recipients a shared record for next steps.
Who This Is For
- Device management teams. They inspect managed Android devices and identify units that need version or permission follow-up.
- Operations teams. They review device readiness before upgrades, feature use, or new device rollout.
- Support staff. They use the email summary and Excel details to track abnormal or unreadable devices.
What Sets This Workflow Apart
- Scope control. It supports all devices or exact device and group names, then keeps only Android devices.
- Selective inspection. It checks version, permissions, or both, so unused standards do not need to be entered.
- Report gating. It generates Excel only when abnormal devices exist, and it skips the report for all-normal results.
- Readable status handling. It separates disabled, unsupported, and unreadable permission states, which makes follow-up clearer.
How It Works
- Select the inspection scope
- The workflow takes all devices or chosen device and group names, then keeps only Android devices for inspection.
- Validate the inputs
- It checks the scope choice, required version or permission fields, recipient emails, and the report time zone before continuing.
- Inspect versions and permissions
- It resolves the target devices, checks the selected Biz Daemon standards, and marks devices with unreadable statuses separately.
- Create the report when needed
- When abnormal devices exist, it writes them to Sheet1 in Excel and prepares a read-only link.
- Send the results by email
- It emails the summary to the chosen recipients and includes the report link when the workbook and sharing step succeed.
What You'll Need
- AirDroid Business access
- An authorized connection is needed to read device scope, version, and permission data.
- Excel, OneDrive, and Gmail connections
- Authorized connections are needed to write the report, create the read-only link, and send email notifications.
- Inspection settings
- You must choose the device scope, select the inspection mode, and enter any required version or permission values.
- Recipient emails and report time zone
- You must enter at least one recipient address, and you can select a time zone for report display.
How to Use
- Step 1. Prepare the required connections
- Step 2. Choose the inspection scope
- Step 3. Set the inspection standards
- Step 4. Review the email result
Bind usable AirDroid Business, Excel, OneDrive, and Gmail connections, then enter at least one recipient email address.
Select all devices or enter exact device and group names for a custom Android scope.
Choose version only, permissions only, or both, then enter the required minimum version or permission names.
Check the Gmail summary for device counts, abnormal items, and any report link or failure reason.