Overview

This workflow queries one AirDroid Business device by IMEI and returns its current Policy & Kiosk effective status through an API response. It is a reusable step for operations that need a consistent status lookup for deployment checks or external integrations.

The Problem This Workflow Solves

Teams that manage AirDroid Business devices sometimes need to confirm whether a single device has the expected Policy & Kiosk configuration. The lookup must be done by IMEI, and the result must show whether the device was found, whether the IMEI is unique, and what status should be returned to the calling system.

  • Direct status check. The workflow returns the device's current Policy & Kiosk status in one response.
  • Clear lookup result. It separates missing, ambiguous, and successful matches for easier follow-up.
  • API-friendly output. External systems receive a consistent status code, message, and status value.

Who This Is For

  • Operations teams. They use this query when they need a current status check for one managed device.
  • Integration owners. They call the API from external systems that need Policy & Kiosk status by IMEI.
  • Deployment verification users. They confirm whether a single device reports the expected configuration effective status.

What Sets This Workflow Apart

  • Single-device scope. The workflow accepts one IMEI and does not support batch, group, or device name queries.
  • Unique-match check. It confirms that the IMEI matches exactly one device before returning the status.
  • Unified response. It returns success and failure results in a consistent format for calling systems.

How It Works

1
  1. Check the IMEI
  2. The workflow first checks that an IMEI is provided. If it is missing, the workflow ends with an invalid input response.
2
  1. Build query context and locate the device
  2. The workflow records the query time, searches AirDroid Business by IMEI, and reads the device snapshot if the lookup succeeds.
3
  1. Validate the match and return the response
  2. The workflow confirms the device lookup, checks that exactly one device matched, and returns the Policy & Kiosk effective status or a failure message.

What You'll Need

  • AirDroid Business credentials
    • An authorized connection is needed so the workflow can search devices by IMEI and read configuration status.
  • Target device IMEI
    • The calling system must provide one required IMEI value for the device you want to query.

How to Use

  1. Step 1. Connect credentials
  2. Bind authorized AirDroid Business credentials so the workflow can search for the device and return its status.

  3. Step 2. Pass the device IMEI
  4. Send the target device IMEI from your external system to start the query.

  5. Step 3. Read the returned fields
  6. Check Success, StatusCode, and PolicyKioskEffectiveStatus when the query succeeds, or ErrorMessage when it fails.

FAQs

What does this workflow query?
It queries the current Policy & Kiosk effective status for one AirDroid Business device.
Can I use device names or groups instead of IMEI?
No. The workflow only supports a single device lookup by IMEI.
What happens if the IMEI is missing or unclear?
The workflow returns a failure response if the IMEI is empty, the device is not found, or multiple devices match.
What output should external systems read?
Read Success, StatusCode, and PolicyKioskEffectiveStatus on success. Read ErrorMessage when the response indicates failure.
Was This Page Helpful?

More Workflows for Inspiration

🔧
Account Activity Log Query and Export
Exports account activity logs from the chosen days, then emails a OneDrive workbook link.
Learn more >
🔧
Device Unenroll and Transfer Log Query
Query recent device unenrollment and group transfer logs, then send an Excel report link by email.
Learn more >
🔧
Auto-add Tags to Alerting Devices
When an alert fires, this workflow tags the target device for faster filtering and follow-up.
Learn more >