Overview
This template queries a device screen snapshot in AirDroid Business by SNID, then refreshes the image and returns the latest snapshot fields in one response. It supports a repeatable operational step for teams that need current device visibility and a consistent way to retrieve it through a published API.
The Problem This Workflow Solves
Teams responsible for monitored devices often need a current screen image tied to a specific SNID. They also need the device name, group, last online time, and screenshot timing to decide whether the snapshot is current enough or whether the query should be repeated.
- Clear device lookup. The workflow checks whether one device matches the provided SNID before it continues.
- Current snapshot data. It refreshes the device screen image before reading the snapshot fields.
- Simple follow-up. It returns a unified response with success and failure details for the next action.
Who This Is For
- Device monitoring teams. They need a direct way to check a device screen from a known SNID.
- Operations staff. They need current screen information for terminals or field devices at query time.
- External system integrators. They need a unified API response that exposes snapshot status for one device.
What Sets This Workflow Apart
- SNID validation. The workflow stops early when no SNID is provided and returns a clear input error.
- Uniqueness check. It confirms that the SNID matches one device before requesting a screenshot refresh.
- Age calculation. It turns the screenshot update time into a relative age such as hours or minutes ago.
How It Works
- Validate the request
- The workflow checks that an SNID is present and prepares a query timestamp for the response.
- Find the target device
- It looks up the device by SNID, confirms the match is unique, and extracts the device ID.
- Refresh and wait
- The workflow pushes a screenshot refresh to the device and waits 20 seconds before reading the snapshot.
- Return the snapshot data
- It reads device name, group, last online time, screenshot link, update time, and relative screenshot age when available.
What You'll Need
- AirDroid Business access
- An authorized connection is needed so the workflow can search devices and request a screenshot refresh.
- SNID in the request
- You must provide the device serial number so the workflow can identify one target device.
- Refresh wait time
- The workflow uses a 20 second wait before snapshot retrieval, and that value can be adjusted if needed.
How to Use
- Step 1. Prepare the request
- Step 2. Run the template
- Step 3. Read the response
- Step 4. Review failure details
Enter the SNID and make sure the AirDroid Business credentials used by the workflow are available.
Run the workflow or call the published API so it can refresh the device snapshot and return the response.
Use the returned status code, snapshot link, last screenshot time, and screenshot age to judge whether the image is current.
If the run fails, check the error description and result code to see whether the SNID, device lookup, or refresh needs attention.