Overview
This template finds devices that were bound recently, assigns sequential names from a chosen prefix, and skips devices that already match the pattern. It also summarizes the run and can send Outlook notifications when input, query, or renaming problems occur, making it suitable as a repeatable device naming step.
The Problem This Workflow Solves
Teams responsible for managed devices often need to rename newly bound devices while checking which ones already follow the required naming pattern. They also need to confirm the recent binding window, decide whether any devices should be renamed, and handle failures with a clear result or notification.
- Cleaner naming. The workflow assigns sequential names from one prefix and skips devices that already match the rule.
- Faster follow-up. The run returns success, partial success, empty, or failure results for easier handling.
- Failure detail. When renaming fails, the workflow can generate an Excel report and send Outlook notification.
- Earlier validation. The workflow checks prefix, recent days, and recipient email settings before processing devices.
Who This Is For
- Device management teams. They need to name recently bound devices in a consistent and repeatable way.
- Operations staff. They review run results and handle devices that fail naming or already match the rule.
- Teams using Outlook notifications. They need email alerts when configuration or device processing does not complete cleanly.
What Sets This Workflow Apart
- Pattern-based skip. Devices that already use the prefix plus number format are not renamed again.
- Time-windowed scope. The workflow queries only devices bound within the selected recent-day range.
- Per-device results. Each rename attempt is recorded, and failed items can be summarized in Excel.
How It Works
- Collect naming settings
- The workflow reads the prefix, recent-day window, display time zone, and notification recipients before any device processing begins.
- Validate the request
- It checks the prefix and day count, and it stops early with a configuration result when those values are invalid.
- Query recently bound devices
- The workflow searches accessible devices bound within the selected window and stops if the device query returns an error.
- Plan sequential names
- It skips devices that already match the naming rule, orders the remaining devices by binding time, and assigns the next available numbers.
- Rename devices one by one
- The workflow applies each planned name individually and records whether every device rename succeeded or failed.
- Summarize and notify
- It returns the run status and counts, and it sends Outlook notifications when invalid input, query errors, or rename failures occur.
What You'll Need
- AirDroid Business access
- You need permission to view devices and change device names for the targeted account.
- Connected Microsoft services
- Authorized AirDroid Business, Excel, OneDrive, and Outlook connections are required, and Excel plus OneDrive must use the same account.
- Run settings
- You must enter a name prefix, a positive recent-day value, a display time zone, and recipient email addresses.
How to Use
- Step 1. Prepare the connections
- Step 2. Enter the run values
- Step 3. Run or schedule the template
- Step 4. Review the outcome
Confirm device-name permissions and make sure the Outlook connection can send messages. Set up the required AirDroid Business, Excel, OneDrive, and Outlook credentials.
Provide the prefix, recent-day range, notification time zone, and recipient emails. Keep the prefix within the supported length and avoid unsupported characters.
Use the template for an immediate run, or make the values optional and set defaults for periodic naming. After that, publish a scheduled run if needed.
Check the returned counts and run result. If some devices fail, review the Outlook notification and the Excel details report when one is generated.