Overview
This template queries the latest historical GPS record for a device by SNID within the last 30 UTC days. It returns the most recent location record, query time, and status data so teams can use the same lookup step in a repeatable operating process.
The Problem This Workflow Solves
Teams responsible for monitored devices often need the last known location of a specific unit after a dispatch update, field check, or inventory review. They must confirm the device by SNID, stay within the supported history window, and decide whether the record exists or the query failed.
- Faster lookup. The workflow returns the latest recorded GPS point without manual console searching.
- Clearer exceptions. The response shows why the lookup failed when SNID, access, or history is missing.
- Consistent range. The query always stays inside the supported 30-day historical window.
Who This Is For
- Dispatch and fleet teams. They can check the last reported location of vehicles or handheld terminals.
- Field operations teams. They can verify recent device location before inspections or retrieval work.
- Asset and inventory teams. They can reference recent location records during device checks.
- System integrators. They can call the API from ERP, WMS, or TMS workflows.
What Sets This Workflow Apart
- SNID-based lookup. The workflow identifies the target device from its serial number instead of a name match.
- Fixed history window. It only reads reports from the past 30 UTC days, matching the supported range.
- Structured result. It returns location data, query time, status code, and error text in one response.
- Historical data only. It uses stored GPS reports and does not request a real-time location refresh.
How It Works
- Receive the device SNID
- The workflow starts when a business system passes the target device serial number.
- Check the query window
- It sets the date range to the past 30 UTC calendar days before querying history.
- Find the device and latest record
- It locates the device by SNID, then reads the newest GPS report in that range.
- Return the result
- The workflow returns the location record and query time on success, or a readable failure reason.
What You'll Need
- AirDroid Business access
- An authorized connection is required, and the device must be visible to the current account.
- Target device SNID
- The calling system must provide the device serial number as the input for the lookup.
How to Use
- Step 1. Prepare the connection and input
- Step 2. Pass the SNID from your system
- Step 3. Read the returned status
Configure the AirDroid Business credential and make sure the target device SNID is ready before calling the template.
Send the device serial number from your business application to invoke the API-style workflow.
Use the status code, location records, query time, and error message to handle the response in your system.